apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T22:09:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-84-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-84.us-west-2.compute.internal uid: cb7fcf21-9b5a-40cf-b069-2488a4b08190 resourceVersion: "107238" uid: d0be9f8a-22b5-4b2b-b227-d1184184b337 spec: sourcePod: network-check-source-6f78d59f99-q4b9r targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-03T22:16:12Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.028601ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:12:11Z" - latency: 1.202981ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:11:11Z" - latency: 1.303946ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:10:11Z" - latency: 980.605µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:09:11Z" - latency: 1.303466ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:08:11Z" - latency: 1.169262ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:07:11Z" - latency: 1.430341ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:06:11Z" - latency: 1.159397ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:05:11Z" - latency: 1.025144ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:04:11Z" - latency: 1.322377ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:03:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T22:09:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-84-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-84.us-west-2.compute.internal uid: cb7fcf21-9b5a-40cf-b069-2488a4b08190 resourceVersion: "110162" uid: 736faa07-8ba7-40ed-9518-e6e818ff3356 spec: sourcePod: network-check-source-6f78d59f99-q4b9r targetEndpoint: a3890ba9e34074c9bb3a6df7076aca19-87013095a60c6b5c.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T22:15:12Z" message: 'load-balancer-api-external: tcp connection to a3890ba9e34074c9bb3a6df7076aca19-87013095a60c6b5c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 51.320567ms message: 'load-balancer-api-external: tcp connection to a3890ba9e34074c9bb3a6df7076aca19-87013095a60c6b5c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:16:12Z" - latency: 6.401359ms message: 'load-balancer-api-external: resolved host name a3890ba9e34074c9bb3a6df7076aca19-87013095a60c6b5c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T23:16:11Z" - latency: 55.702441ms message: 'load-balancer-api-external: tcp connection to a3890ba9e34074c9bb3a6df7076aca19-87013095a60c6b5c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:15:12Z" - latency: 6.784435ms message: 'load-balancer-api-external: resolved host name a3890ba9e34074c9bb3a6df7076aca19-87013095a60c6b5c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T23:15:11Z" - latency: 52.03654ms message: 'load-balancer-api-external: tcp connection to a3890ba9e34074c9bb3a6df7076aca19-87013095a60c6b5c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:14:12Z" - latency: 6.179584ms message: 'load-balancer-api-external: resolved host name a3890ba9e34074c9bb3a6df7076aca19-87013095a60c6b5c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T23:14:11Z" - latency: 51.67615ms message: 'load-balancer-api-external: tcp connection to a3890ba9e34074c9bb3a6df7076aca19-87013095a60c6b5c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:13:12Z" - latency: 7.872552ms message: 'load-balancer-api-external: resolved host name a3890ba9e34074c9bb3a6df7076aca19-87013095a60c6b5c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T23:13:11Z" - latency: 54.855175ms message: 'load-balancer-api-external: tcp connection to a3890ba9e34074c9bb3a6df7076aca19-87013095a60c6b5c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:12:12Z" - latency: 7.019972ms message: 'load-balancer-api-external: resolved host name a3890ba9e34074c9bb3a6df7076aca19-87013095a60c6b5c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T23:12:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T22:09:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-84-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-84.us-west-2.compute.internal uid: cb7fcf21-9b5a-40cf-b069-2488a4b08190 resourceVersion: "110163" uid: fc47396d-8673-437d-bc69-8a4925519fd1 spec: sourcePod: network-check-source-6f78d59f99-q4b9r targetEndpoint: a3890ba9e34074c9bb3a6df7076aca19-87013095a60c6b5c.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T22:15:12Z" message: 'load-balancer-api-internal: tcp connection to a3890ba9e34074c9bb3a6df7076aca19-87013095a60c6b5c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 54.751144ms message: 'load-balancer-api-internal: tcp connection to a3890ba9e34074c9bb3a6df7076aca19-87013095a60c6b5c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:16:12Z" - latency: 6.440329ms message: 'load-balancer-api-internal: resolved host name a3890ba9e34074c9bb3a6df7076aca19-87013095a60c6b5c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T23:16:11Z" - latency: 55.897701ms message: 'load-balancer-api-internal: tcp connection to a3890ba9e34074c9bb3a6df7076aca19-87013095a60c6b5c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:15:12Z" - latency: 6.718906ms message: 'load-balancer-api-internal: resolved host name a3890ba9e34074c9bb3a6df7076aca19-87013095a60c6b5c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T23:15:11Z" - latency: 55.572388ms message: 'load-balancer-api-internal: tcp connection to a3890ba9e34074c9bb3a6df7076aca19-87013095a60c6b5c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:14:12Z" - latency: 6.215276ms message: 'load-balancer-api-internal: resolved host name a3890ba9e34074c9bb3a6df7076aca19-87013095a60c6b5c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T23:14:11Z" - latency: 54.947886ms message: 'load-balancer-api-internal: tcp connection to a3890ba9e34074c9bb3a6df7076aca19-87013095a60c6b5c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:13:12Z" - latency: 7.79049ms message: 'load-balancer-api-internal: resolved host name a3890ba9e34074c9bb3a6df7076aca19-87013095a60c6b5c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T23:13:11Z" - latency: 51.427563ms message: 'load-balancer-api-internal: tcp connection to a3890ba9e34074c9bb3a6df7076aca19-87013095a60c6b5c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:12:12Z" - latency: 6.965951ms message: 'load-balancer-api-internal: resolved host name a3890ba9e34074c9bb3a6df7076aca19-87013095a60c6b5c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T23:12:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T22:09:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-84-to-network-check-target-ip-10-0-134-57 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-84.us-west-2.compute.internal uid: cb7fcf21-9b5a-40cf-b069-2488a4b08190 resourceVersion: "107236" uid: 30c90e01-ae0b-43ea-be12-52b18ddb7e4f spec: sourcePod: network-check-source-6f78d59f99-q4b9r targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-03T22:16:11Z" message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.535417ms message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:12:11Z" - latency: 2.174892ms message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:11:11Z" - latency: 2.628854ms message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:10:11Z" - latency: 2.581135ms message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:09:11Z" - latency: 2.22692ms message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:08:11Z" - latency: 2.249597ms message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:07:11Z" - latency: 2.223676ms message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:06:11Z" - latency: 2.100047ms message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:05:11Z" - latency: 2.316835ms message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:04:11Z" - latency: 2.464768ms message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:03:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T22:09:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-84-to-network-check-target-ip-10-0-139-254 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-84.us-west-2.compute.internal uid: cb7fcf21-9b5a-40cf-b069-2488a4b08190 resourceVersion: "107220" uid: f76fa411-2664-4a06-a9b2-99f0b0cd39f1 spec: sourcePod: network-check-source-6f78d59f99-q4b9r targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-03T22:16:11Z" message: 'network-check-target-ip-10-0-139-254: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.475534ms message: 'network-check-target-ip-10-0-139-254: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:12:11Z" - latency: 2.093139ms message: 'network-check-target-ip-10-0-139-254: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:11:11Z" - latency: 2.180488ms message: 'network-check-target-ip-10-0-139-254: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:10:11Z" - latency: 2.910384ms message: 'network-check-target-ip-10-0-139-254: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:09:11Z" - latency: 2.322058ms message: 'network-check-target-ip-10-0-139-254: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:08:11Z" - latency: 1.754854ms message: 'network-check-target-ip-10-0-139-254: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:07:11Z" - latency: 2.153263ms message: 'network-check-target-ip-10-0-139-254: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:06:11Z" - latency: 1.959141ms message: 'network-check-target-ip-10-0-139-254: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:05:11Z" - latency: 2.130632ms message: 'network-check-target-ip-10-0-139-254: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:04:11Z" - latency: 2.02833ms message: 'network-check-target-ip-10-0-139-254: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:03:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T22:09:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-84-to-network-check-target-ip-10-0-141-84 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-84.us-west-2.compute.internal uid: cb7fcf21-9b5a-40cf-b069-2488a4b08190 resourceVersion: "107218" uid: 98862b44-f81b-4d92-86ad-091b1ed067fe spec: sourcePod: network-check-source-6f78d59f99-q4b9r targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-03T22:16:11Z" message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.191891ms message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:12:11Z" - latency: 1.231216ms message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:11:11Z" - latency: 1.085238ms message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:10:11Z" - latency: 2.33662ms message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:09:11Z" - latency: 911.668µs message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:08:11Z" - latency: 1.176082ms message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:07:11Z" - latency: 1.355533ms message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:06:11Z" - latency: 1.03384ms message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:05:11Z" - latency: 983.596µs message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:04:11Z" - latency: 1.12776ms message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:03:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T22:09:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-84-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-84.us-west-2.compute.internal uid: cb7fcf21-9b5a-40cf-b069-2488a4b08190 resourceVersion: "110161" uid: c3b90aff-c364-4028-b491-c75a9268f032 spec: sourcePod: network-check-source-6f78d59f99-q4b9r targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-03T22:15:12Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.033823ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:16:12Z" - latency: 840.323µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T23:16:12Z" - latency: 1.055576ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:15:12Z" - latency: 781.469µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T23:15:12Z" - latency: 1.190462ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:14:12Z" - latency: 645.597µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T23:14:12Z" - latency: 1.143051ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:13:12Z" - latency: 735.641µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T23:13:12Z" - latency: 1.235023ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T23:12:12Z" - latency: 859.207µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T23:12:12Z" kind: List metadata: resourceVersion: ""