apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:40:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-122-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-122.us-west-1.compute.internal uid: e49029e3-706b-4efb-b25c-f969c926a801 resourceVersion: "93679" uid: b2f6b2d2-7449-43d6-a8ed-d31476a8393d spec: sourcePod: network-check-source-6f78d59f99-jwxvn targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T18:47:07Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.477924ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:36:07Z" - latency: 1.221678ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:35:07Z" - latency: 1.130602ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:34:07Z" - latency: 1.627906ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:33:07Z" - latency: 963.781µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:32:07Z" - latency: 1.21832ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:31:07Z" - latency: 995.467µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:30:07Z" - latency: 996.154µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:29:07Z" - latency: 1.255931ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:28:07Z" - latency: 6.657443ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:27:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:40:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-122-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-122.us-west-1.compute.internal uid: e49029e3-706b-4efb-b25c-f969c926a801 resourceVersion: "96435" uid: 3c1a212b-9a8c-424a-a833-e30e38d3b692 spec: sourcePod: network-check-source-6f78d59f99-jwxvn targetEndpoint: aec3e5e704cd849e78ca3402ce7e1bb4-9d227f372467f59d.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T18:46:07Z" message: 'load-balancer-api-external: tcp connection to aec3e5e704cd849e78ca3402ce7e1bb4-9d227f372467f59d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 53.824125ms message: 'load-balancer-api-external: tcp connection to aec3e5e704cd849e78ca3402ce7e1bb4-9d227f372467f59d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:40:07Z" - latency: 6.951433ms message: 'load-balancer-api-external: resolved host name aec3e5e704cd849e78ca3402ce7e1bb4-9d227f372467f59d.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:40:07Z" - latency: 52.480226ms message: 'load-balancer-api-external: tcp connection to aec3e5e704cd849e78ca3402ce7e1bb4-9d227f372467f59d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:39:07Z" - latency: 8.600756ms message: 'load-balancer-api-external: resolved host name aec3e5e704cd849e78ca3402ce7e1bb4-9d227f372467f59d.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:39:07Z" - latency: 53.558493ms message: 'load-balancer-api-external: tcp connection to aec3e5e704cd849e78ca3402ce7e1bb4-9d227f372467f59d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:38:07Z" - latency: 6.408472ms message: 'load-balancer-api-external: resolved host name aec3e5e704cd849e78ca3402ce7e1bb4-9d227f372467f59d.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:38:07Z" - latency: 52.151936ms message: 'load-balancer-api-external: tcp connection to aec3e5e704cd849e78ca3402ce7e1bb4-9d227f372467f59d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:37:07Z" - latency: 6.76721ms message: 'load-balancer-api-external: resolved host name aec3e5e704cd849e78ca3402ce7e1bb4-9d227f372467f59d.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:37:07Z" - latency: 54.518026ms message: 'load-balancer-api-external: tcp connection to aec3e5e704cd849e78ca3402ce7e1bb4-9d227f372467f59d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:36:07Z" - latency: 10.221156ms message: 'load-balancer-api-external: resolved host name aec3e5e704cd849e78ca3402ce7e1bb4-9d227f372467f59d.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:36:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:40:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-122-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-122.us-west-1.compute.internal uid: e49029e3-706b-4efb-b25c-f969c926a801 resourceVersion: "96434" uid: 1c35de13-6b53-4ea1-a3e8-ff445542cde0 spec: sourcePod: network-check-source-6f78d59f99-jwxvn targetEndpoint: aec3e5e704cd849e78ca3402ce7e1bb4-9d227f372467f59d.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T18:46:07Z" message: 'load-balancer-api-internal: tcp connection to aec3e5e704cd849e78ca3402ce7e1bb4-9d227f372467f59d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 54.270133ms message: 'load-balancer-api-internal: tcp connection to aec3e5e704cd849e78ca3402ce7e1bb4-9d227f372467f59d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:40:07Z" - latency: 6.900734ms message: 'load-balancer-api-internal: resolved host name aec3e5e704cd849e78ca3402ce7e1bb4-9d227f372467f59d.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:40:07Z" - latency: 52.464148ms message: 'load-balancer-api-internal: tcp connection to aec3e5e704cd849e78ca3402ce7e1bb4-9d227f372467f59d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:39:07Z" - latency: 8.647242ms message: 'load-balancer-api-internal: resolved host name aec3e5e704cd849e78ca3402ce7e1bb4-9d227f372467f59d.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:39:07Z" - latency: 53.544305ms message: 'load-balancer-api-internal: tcp connection to aec3e5e704cd849e78ca3402ce7e1bb4-9d227f372467f59d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:38:07Z" - latency: 6.344194ms message: 'load-balancer-api-internal: resolved host name aec3e5e704cd849e78ca3402ce7e1bb4-9d227f372467f59d.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:38:07Z" - latency: 52.096634ms message: 'load-balancer-api-internal: tcp connection to aec3e5e704cd849e78ca3402ce7e1bb4-9d227f372467f59d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:37:07Z" - latency: 6.802084ms message: 'load-balancer-api-internal: resolved host name aec3e5e704cd849e78ca3402ce7e1bb4-9d227f372467f59d.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:37:07Z" - latency: 54.040994ms message: 'load-balancer-api-internal: tcp connection to aec3e5e704cd849e78ca3402ce7e1bb4-9d227f372467f59d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:36:07Z" - latency: 10.24989ms message: 'load-balancer-api-internal: resolved host name aec3e5e704cd849e78ca3402ce7e1bb4-9d227f372467f59d.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:36:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:40:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-122-to-network-check-target-ip-10-0-131-68 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-122.us-west-1.compute.internal uid: e49029e3-706b-4efb-b25c-f969c926a801 resourceVersion: "93678" uid: 5603771f-07b1-4b58-b0eb-41469494f989 spec: sourcePod: network-check-source-6f78d59f99-jwxvn targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T18:47:07Z" message: 'network-check-target-ip-10-0-131-68: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.43801ms message: 'network-check-target-ip-10-0-131-68: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:36:07Z" - latency: 2.310365ms message: 'network-check-target-ip-10-0-131-68: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:35:07Z" - latency: 2.266453ms message: 'network-check-target-ip-10-0-131-68: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:34:07Z" - latency: 2.306066ms message: 'network-check-target-ip-10-0-131-68: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:33:07Z" - latency: 2.095417ms message: 'network-check-target-ip-10-0-131-68: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:32:07Z" - latency: 1.820947ms message: 'network-check-target-ip-10-0-131-68: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:31:07Z" - latency: 2.477639ms message: 'network-check-target-ip-10-0-131-68: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:30:07Z" - latency: 2.462604ms message: 'network-check-target-ip-10-0-131-68: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:29:07Z" - latency: 2.202984ms message: 'network-check-target-ip-10-0-131-68: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:28:07Z" - latency: 15.999069ms message: 'network-check-target-ip-10-0-131-68: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:27:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:40:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-122-to-network-check-target-ip-10-0-132-122 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-122.us-west-1.compute.internal uid: e49029e3-706b-4efb-b25c-f969c926a801 resourceVersion: "93676" uid: 97365c0a-057b-4b6a-b5b9-6b4bd92a6a0f spec: sourcePod: network-check-source-6f78d59f99-jwxvn targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T18:47:07Z" message: 'network-check-target-ip-10-0-132-122: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 980.24µs message: 'network-check-target-ip-10-0-132-122: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:36:07Z" - latency: 807.113µs message: 'network-check-target-ip-10-0-132-122: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:35:07Z" - latency: 1.387354ms message: 'network-check-target-ip-10-0-132-122: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:34:07Z" - latency: 786.305µs message: 'network-check-target-ip-10-0-132-122: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:33:07Z" - latency: 916.503µs message: 'network-check-target-ip-10-0-132-122: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:32:07Z" - latency: 822.278µs message: 'network-check-target-ip-10-0-132-122: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:31:07Z" - latency: 1.181058ms message: 'network-check-target-ip-10-0-132-122: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:30:07Z" - latency: 1.156996ms message: 'network-check-target-ip-10-0-132-122: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:29:07Z" - latency: 942.235µs message: 'network-check-target-ip-10-0-132-122: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:28:07Z" - latency: 6.019974ms message: 'network-check-target-ip-10-0-132-122: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:27:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:40:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-122-to-network-check-target-ip-10-0-143-97 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-122.us-west-1.compute.internal uid: e49029e3-706b-4efb-b25c-f969c926a801 resourceVersion: "93677" uid: 2e0034c8-5f4f-47ff-9344-916569ae5322 spec: sourcePod: network-check-source-6f78d59f99-jwxvn targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T18:47:07Z" message: 'network-check-target-ip-10-0-143-97: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.879586ms message: 'network-check-target-ip-10-0-143-97: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:36:07Z" - latency: 1.994652ms message: 'network-check-target-ip-10-0-143-97: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:35:07Z" - latency: 2.255391ms message: 'network-check-target-ip-10-0-143-97: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:34:07Z" - latency: 1.984147ms message: 'network-check-target-ip-10-0-143-97: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:33:07Z" - latency: 1.862682ms message: 'network-check-target-ip-10-0-143-97: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:32:07Z" - latency: 2.232208ms message: 'network-check-target-ip-10-0-143-97: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:31:07Z" - latency: 1.985735ms message: 'network-check-target-ip-10-0-143-97: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:30:07Z" - latency: 2.227022ms message: 'network-check-target-ip-10-0-143-97: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:29:07Z" - latency: 2.1305ms message: 'network-check-target-ip-10-0-143-97: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:28:07Z" - latency: 15.463758ms message: 'network-check-target-ip-10-0-143-97: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:27:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:40:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-122-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-122.us-west-1.compute.internal uid: e49029e3-706b-4efb-b25c-f969c926a801 resourceVersion: "96433" uid: bc2958e1-d972-44fb-abbd-13f8a50dae8b spec: sourcePod: network-check-source-6f78d59f99-jwxvn targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T18:46:07Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.294424ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:40:07Z" - latency: 1.992658ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T19:40:07Z" - latency: 1.083283ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:39:07Z" - latency: 2.303859ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T19:39:07Z" - latency: 1.062423ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:38:07Z" - latency: 1.68937ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T19:38:07Z" - latency: 893.666µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:37:07Z" - latency: 1.890446ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T19:37:07Z" - latency: 1.171488ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:36:07Z" - latency: 1.879884ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T19:36:07Z" kind: List metadata: resourceVersion: ""