apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T00:06:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-162-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-162.us-west-1.compute.internal uid: 4088fb70-e5b0-4199-a322-307bd76b1b50 resourceVersion: "156926" uid: 69bbf266-e8ed-42f5-a0e1-d75e27c2978b spec: sourcePod: network-check-source-6f78d59f99-dlhnx targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-03T00:13:44Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.172468ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:51:44Z" - latency: 973.006µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:50:44Z" - latency: 6.383319ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:49:44Z" - latency: 1.185445ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:48:44Z" - latency: 1.050297ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:47:44Z" - latency: 1.047652ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:46:44Z" - latency: 1.145972ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:45:44Z" - latency: 882.809µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:44:44Z" - latency: 1.513522ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:43:44Z" - latency: 1.316471ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:42:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T00:06:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-162-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-162.us-west-1.compute.internal uid: 4088fb70-e5b0-4199-a322-307bd76b1b50 resourceVersion: "154329" uid: 0208dcfe-81a2-48d1-93cf-9d49258918f1 spec: sourcePod: network-check-source-6f78d59f99-dlhnx targetEndpoint: a94de1dd7bb8b42158c74d34dda92279-9029fc03a8717821.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T00:12:44Z" message: 'load-balancer-api-external: tcp connection to a94de1dd7bb8b42158c74d34dda92279-9029fc03a8717821.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 54.996488ms message: 'load-balancer-api-external: tcp connection to a94de1dd7bb8b42158c74d34dda92279-9029fc03a8717821.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:48:44Z" - latency: 8.068717ms message: 'load-balancer-api-external: resolved host name a94de1dd7bb8b42158c74d34dda92279-9029fc03a8717821.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T01:48:44Z" - latency: 54.753942ms message: 'load-balancer-api-external: tcp connection to a94de1dd7bb8b42158c74d34dda92279-9029fc03a8717821.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:47:44Z" - latency: 15.363112ms message: 'load-balancer-api-external: resolved host name a94de1dd7bb8b42158c74d34dda92279-9029fc03a8717821.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T01:47:44Z" - latency: 53.599612ms message: 'load-balancer-api-external: tcp connection to a94de1dd7bb8b42158c74d34dda92279-9029fc03a8717821.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:46:44Z" - latency: 7.424005ms message: 'load-balancer-api-external: resolved host name a94de1dd7bb8b42158c74d34dda92279-9029fc03a8717821.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T01:46:44Z" - latency: 53.632749ms message: 'load-balancer-api-external: tcp connection to a94de1dd7bb8b42158c74d34dda92279-9029fc03a8717821.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:45:44Z" - latency: 6.482903ms message: 'load-balancer-api-external: resolved host name a94de1dd7bb8b42158c74d34dda92279-9029fc03a8717821.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T01:45:44Z" - latency: 53.219189ms message: 'load-balancer-api-external: tcp connection to a94de1dd7bb8b42158c74d34dda92279-9029fc03a8717821.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:44:44Z" - latency: 7.83309ms message: 'load-balancer-api-external: resolved host name a94de1dd7bb8b42158c74d34dda92279-9029fc03a8717821.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T01:44:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T00:06:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-162-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-162.us-west-1.compute.internal uid: 4088fb70-e5b0-4199-a322-307bd76b1b50 resourceVersion: "154328" uid: e849048b-4714-45bb-90d7-0c67c09ba2fb spec: sourcePod: network-check-source-6f78d59f99-dlhnx targetEndpoint: a94de1dd7bb8b42158c74d34dda92279-9029fc03a8717821.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T00:12:44Z" message: 'load-balancer-api-internal: tcp connection to a94de1dd7bb8b42158c74d34dda92279-9029fc03a8717821.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 55.03273ms message: 'load-balancer-api-internal: tcp connection to a94de1dd7bb8b42158c74d34dda92279-9029fc03a8717821.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:48:44Z" - latency: 8.168142ms message: 'load-balancer-api-internal: resolved host name a94de1dd7bb8b42158c74d34dda92279-9029fc03a8717821.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T01:48:44Z" - latency: 54.741101ms message: 'load-balancer-api-internal: tcp connection to a94de1dd7bb8b42158c74d34dda92279-9029fc03a8717821.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:47:44Z" - latency: 15.473559ms message: 'load-balancer-api-internal: resolved host name a94de1dd7bb8b42158c74d34dda92279-9029fc03a8717821.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T01:47:44Z" - latency: 53.253117ms message: 'load-balancer-api-internal: tcp connection to a94de1dd7bb8b42158c74d34dda92279-9029fc03a8717821.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:46:44Z" - latency: 7.500056ms message: 'load-balancer-api-internal: resolved host name a94de1dd7bb8b42158c74d34dda92279-9029fc03a8717821.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T01:46:44Z" - latency: 53.566113ms message: 'load-balancer-api-internal: tcp connection to a94de1dd7bb8b42158c74d34dda92279-9029fc03a8717821.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:45:44Z" - latency: 6.55853ms message: 'load-balancer-api-internal: resolved host name a94de1dd7bb8b42158c74d34dda92279-9029fc03a8717821.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T01:45:44Z" - latency: 53.204887ms message: 'load-balancer-api-internal: tcp connection to a94de1dd7bb8b42158c74d34dda92279-9029fc03a8717821.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:44:44Z" - latency: 7.944974ms message: 'load-balancer-api-internal: resolved host name a94de1dd7bb8b42158c74d34dda92279-9029fc03a8717821.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T01:44:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T00:06:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-162-to-network-check-target-ip-10-0-135-199 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-162.us-west-1.compute.internal uid: 4088fb70-e5b0-4199-a322-307bd76b1b50 resourceVersion: "156924" uid: dd7ca4cd-f57a-4dfa-ad6d-9fe7a396cd1c spec: sourcePod: network-check-source-6f78d59f99-dlhnx targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-03T00:13:44Z" message: 'network-check-target-ip-10-0-135-199: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.575251ms message: 'network-check-target-ip-10-0-135-199: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:51:44Z" - latency: 2.287618ms message: 'network-check-target-ip-10-0-135-199: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:50:44Z" - latency: 5.8155ms message: 'network-check-target-ip-10-0-135-199: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:49:44Z" - latency: 2.256391ms message: 'network-check-target-ip-10-0-135-199: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:48:44Z" - latency: 2.041421ms message: 'network-check-target-ip-10-0-135-199: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:47:44Z" - latency: 2.425682ms message: 'network-check-target-ip-10-0-135-199: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:46:44Z" - latency: 2.385399ms message: 'network-check-target-ip-10-0-135-199: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:45:44Z" - latency: 1.951604ms message: 'network-check-target-ip-10-0-135-199: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:44:44Z" - latency: 2.175695ms message: 'network-check-target-ip-10-0-135-199: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:43:44Z" - latency: 2.206794ms message: 'network-check-target-ip-10-0-135-199: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:42:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T00:06:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-162-to-network-check-target-ip-10-0-140-172 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-162.us-west-1.compute.internal uid: 4088fb70-e5b0-4199-a322-307bd76b1b50 resourceVersion: "156923" uid: 60bd61ac-3003-4f62-b9fb-913631e85442 spec: sourcePod: network-check-source-6f78d59f99-dlhnx targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-03T00:13:44Z" message: 'network-check-target-ip-10-0-140-172: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.658667ms message: 'network-check-target-ip-10-0-140-172: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:51:44Z" - latency: 1.833564ms message: 'network-check-target-ip-10-0-140-172: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:50:44Z" - latency: 14.035795ms message: 'network-check-target-ip-10-0-140-172: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:49:44Z" - latency: 2.098641ms message: 'network-check-target-ip-10-0-140-172: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:48:44Z" - latency: 1.953072ms message: 'network-check-target-ip-10-0-140-172: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:47:44Z" - latency: 1.917238ms message: 'network-check-target-ip-10-0-140-172: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:46:44Z" - latency: 1.559004ms message: 'network-check-target-ip-10-0-140-172: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:45:44Z" - latency: 1.749719ms message: 'network-check-target-ip-10-0-140-172: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:44:44Z" - latency: 1.935863ms message: 'network-check-target-ip-10-0-140-172: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:43:44Z" - latency: 1.980624ms message: 'network-check-target-ip-10-0-140-172: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:42:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T00:06:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-162-to-network-check-target-ip-10-0-143-162 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-162.us-west-1.compute.internal uid: 4088fb70-e5b0-4199-a322-307bd76b1b50 resourceVersion: "156922" uid: d777f03e-361f-48be-8913-19de46ecbe60 spec: sourcePod: network-check-source-6f78d59f99-dlhnx targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-03T00:13:44Z" message: 'network-check-target-ip-10-0-143-162: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.736979ms message: 'network-check-target-ip-10-0-143-162: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:51:44Z" - latency: 915.304µs message: 'network-check-target-ip-10-0-143-162: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:50:44Z" - latency: 6.435545ms message: 'network-check-target-ip-10-0-143-162: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:49:44Z" - latency: 1.474212ms message: 'network-check-target-ip-10-0-143-162: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:48:44Z" - latency: 1.547068ms message: 'network-check-target-ip-10-0-143-162: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:47:44Z" - latency: 1.039292ms message: 'network-check-target-ip-10-0-143-162: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:46:44Z" - latency: 1.717176ms message: 'network-check-target-ip-10-0-143-162: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:45:44Z" - latency: 941.524µs message: 'network-check-target-ip-10-0-143-162: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:44:44Z" - latency: 1.250582ms message: 'network-check-target-ip-10-0-143-162: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:43:44Z" - latency: 1.6803ms message: 'network-check-target-ip-10-0-143-162: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:42:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T00:06:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-162-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-162.us-west-1.compute.internal uid: 4088fb70-e5b0-4199-a322-307bd76b1b50 resourceVersion: "154323" uid: ea1986b9-e022-41ff-b3e0-ca79760d6443 spec: sourcePod: network-check-source-6f78d59f99-dlhnx targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-03T00:12:44Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 938.487µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:48:44Z" - latency: 2.408342ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T01:48:44Z" - latency: 1.120719ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:47:44Z" - latency: 1.918458ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T01:47:44Z" - latency: 857.661µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:46:44Z" - latency: 1.97302ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T01:46:44Z" - latency: 882.998µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:45:44Z" - latency: 2.212131ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T01:45:44Z" - latency: 865.768µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:44:44Z" - latency: 2.491595ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T01:44:44Z" kind: List metadata: resourceVersion: ""