apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T17:41:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-237-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-237.ec2.internal uid: 971ff768-5740-4b94-8212-59f0f7856669 resourceVersion: "67256" uid: 9d1fcf78-57db-44c4-bd7a-0c2c4f9a1983 spec: sourcePod: network-check-source-6f8b768455-2hq8s targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-11T17:48:41Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.161423ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:16:41Z" - latency: 846.455µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:15:41Z" - latency: 1.252458ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:14:41Z" - latency: 1.001681ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:13:41Z" - latency: 1.310529ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:12:41Z" - latency: 940.206µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:11:41Z" - latency: 1.196023ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:10:41Z" - latency: 1.345575ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:09:41Z" - latency: 1.507578ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:08:41Z" - latency: 1.200588ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:07:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T17:41:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-237-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-237.ec2.internal uid: 971ff768-5740-4b94-8212-59f0f7856669 resourceVersion: "68239" uid: 7c4238cd-f5f2-48ed-8793-da774415722d spec: sourcePod: network-check-source-6f8b768455-2hq8s targetEndpoint: a2acf860bed554802b857e331ca23c6d-c9bb0c3b9fa30017.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-11T17:47:41Z" message: 'load-balancer-api-external: tcp connection to a2acf860bed554802b857e331ca23c6d-c9bb0c3b9fa30017.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.02354ms message: 'load-balancer-api-external: tcp connection to a2acf860bed554802b857e331ca23c6d-c9bb0c3b9fa30017.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:17:41Z" - latency: 9.135491ms message: 'load-balancer-api-external: resolved host name a2acf860bed554802b857e331ca23c6d-c9bb0c3b9fa30017.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T18:17:41Z" - latency: 4.05064ms message: 'load-balancer-api-external: tcp connection to a2acf860bed554802b857e331ca23c6d-c9bb0c3b9fa30017.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:16:41Z" - latency: 9.033265ms message: 'load-balancer-api-external: resolved host name a2acf860bed554802b857e331ca23c6d-c9bb0c3b9fa30017.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T18:16:41Z" - latency: 4.239504ms message: 'load-balancer-api-external: tcp connection to a2acf860bed554802b857e331ca23c6d-c9bb0c3b9fa30017.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:15:41Z" - latency: 8.96187ms message: 'load-balancer-api-external: resolved host name a2acf860bed554802b857e331ca23c6d-c9bb0c3b9fa30017.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T18:15:41Z" - latency: 3.950628ms message: 'load-balancer-api-external: tcp connection to a2acf860bed554802b857e331ca23c6d-c9bb0c3b9fa30017.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:14:41Z" - latency: 9.429694ms message: 'load-balancer-api-external: resolved host name a2acf860bed554802b857e331ca23c6d-c9bb0c3b9fa30017.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T18:14:41Z" - latency: 4.119217ms message: 'load-balancer-api-external: tcp connection to a2acf860bed554802b857e331ca23c6d-c9bb0c3b9fa30017.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:13:41Z" - latency: 9.931913ms message: 'load-balancer-api-external: resolved host name a2acf860bed554802b857e331ca23c6d-c9bb0c3b9fa30017.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T18:13:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T17:41:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-237-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-237.ec2.internal uid: 971ff768-5740-4b94-8212-59f0f7856669 resourceVersion: "68238" uid: 5df02a21-f356-48b5-8250-5f63e1d9ca48 spec: sourcePod: network-check-source-6f8b768455-2hq8s targetEndpoint: a2acf860bed554802b857e331ca23c6d-c9bb0c3b9fa30017.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-11T17:47:41Z" message: 'load-balancer-api-internal: tcp connection to a2acf860bed554802b857e331ca23c6d-c9bb0c3b9fa30017.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.036275ms message: 'load-balancer-api-internal: tcp connection to a2acf860bed554802b857e331ca23c6d-c9bb0c3b9fa30017.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:17:41Z" - latency: 9.105837ms message: 'load-balancer-api-internal: resolved host name a2acf860bed554802b857e331ca23c6d-c9bb0c3b9fa30017.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T18:17:41Z" - latency: 4.021463ms message: 'load-balancer-api-internal: tcp connection to a2acf860bed554802b857e331ca23c6d-c9bb0c3b9fa30017.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:16:41Z" - latency: 9.066731ms message: 'load-balancer-api-internal: resolved host name a2acf860bed554802b857e331ca23c6d-c9bb0c3b9fa30017.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T18:16:41Z" - latency: 4.777444ms message: 'load-balancer-api-internal: tcp connection to a2acf860bed554802b857e331ca23c6d-c9bb0c3b9fa30017.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:15:41Z" - latency: 9.024334ms message: 'load-balancer-api-internal: resolved host name a2acf860bed554802b857e331ca23c6d-c9bb0c3b9fa30017.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T18:15:41Z" - latency: 4.191927ms message: 'load-balancer-api-internal: tcp connection to a2acf860bed554802b857e331ca23c6d-c9bb0c3b9fa30017.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:14:41Z" - latency: 9.455263ms message: 'load-balancer-api-internal: resolved host name a2acf860bed554802b857e331ca23c6d-c9bb0c3b9fa30017.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T18:14:41Z" - latency: 3.133211ms message: 'load-balancer-api-internal: tcp connection to a2acf860bed554802b857e331ca23c6d-c9bb0c3b9fa30017.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:13:41Z" - latency: 9.991209ms message: 'load-balancer-api-internal: resolved host name a2acf860bed554802b857e331ca23c6d-c9bb0c3b9fa30017.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T18:13:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T17:41:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-237-to-network-check-target-ip-10-0-128-237 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-237.ec2.internal uid: 971ff768-5740-4b94-8212-59f0f7856669 resourceVersion: "67254" uid: a29f354d-d5a2-4875-bf2e-3e448f27eba1 spec: sourcePod: network-check-source-6f8b768455-2hq8s targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-11T17:48:41Z" message: 'network-check-target-ip-10-0-128-237: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.334314ms message: 'network-check-target-ip-10-0-128-237: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:16:41Z" - latency: 859.186µs message: 'network-check-target-ip-10-0-128-237: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:15:41Z" - latency: 886.427µs message: 'network-check-target-ip-10-0-128-237: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:14:41Z" - latency: 1.075698ms message: 'network-check-target-ip-10-0-128-237: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:13:41Z" - latency: 1.4421ms message: 'network-check-target-ip-10-0-128-237: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:12:41Z" - latency: 953.396µs message: 'network-check-target-ip-10-0-128-237: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:11:41Z" - latency: 1.00278ms message: 'network-check-target-ip-10-0-128-237: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:10:41Z" - latency: 1.549198ms message: 'network-check-target-ip-10-0-128-237: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:09:41Z" - latency: 1.104195ms message: 'network-check-target-ip-10-0-128-237: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:08:41Z" - latency: 920.055µs message: 'network-check-target-ip-10-0-128-237: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:07:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T17:41:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-237-to-network-check-target-ip-10-0-135-167 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-237.ec2.internal uid: 971ff768-5740-4b94-8212-59f0f7856669 resourceVersion: "67258" uid: 31a061e1-08e2-4f16-9cbf-844bbdce9a72 spec: sourcePod: network-check-source-6f8b768455-2hq8s targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-11T17:48:41Z" message: 'network-check-target-ip-10-0-135-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.608172ms message: 'network-check-target-ip-10-0-135-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:16:41Z" - latency: 2.074759ms message: 'network-check-target-ip-10-0-135-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:15:41Z" - latency: 2.386923ms message: 'network-check-target-ip-10-0-135-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:14:41Z" - latency: 2.341613ms message: 'network-check-target-ip-10-0-135-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:13:41Z" - latency: 2.285965ms message: 'network-check-target-ip-10-0-135-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:12:41Z" - latency: 2.495975ms message: 'network-check-target-ip-10-0-135-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:11:41Z" - latency: 2.537564ms message: 'network-check-target-ip-10-0-135-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:10:41Z" - latency: 2.506833ms message: 'network-check-target-ip-10-0-135-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:09:41Z" - latency: 2.740645ms message: 'network-check-target-ip-10-0-135-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:08:41Z" - latency: 2.340753ms message: 'network-check-target-ip-10-0-135-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:07:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T17:41:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-237-to-network-check-target-ip-10-0-140-215 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-237.ec2.internal uid: 971ff768-5740-4b94-8212-59f0f7856669 resourceVersion: "67255" uid: 73f09d3f-9132-494e-bcb1-66e0e2259855 spec: sourcePod: network-check-source-6f8b768455-2hq8s targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-11T17:48:41Z" message: 'network-check-target-ip-10-0-140-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.4281ms message: 'network-check-target-ip-10-0-140-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:16:41Z" - latency: 2.051653ms message: 'network-check-target-ip-10-0-140-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:15:41Z" - latency: 2.208688ms message: 'network-check-target-ip-10-0-140-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:14:41Z" - latency: 2.216397ms message: 'network-check-target-ip-10-0-140-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:13:41Z" - latency: 2.327338ms message: 'network-check-target-ip-10-0-140-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:12:41Z" - latency: 2.124276ms message: 'network-check-target-ip-10-0-140-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:11:41Z" - latency: 2.499998ms message: 'network-check-target-ip-10-0-140-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:10:41Z" - latency: 2.447123ms message: 'network-check-target-ip-10-0-140-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:09:41Z" - latency: 2.455414ms message: 'network-check-target-ip-10-0-140-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:08:41Z" - latency: 2.435675ms message: 'network-check-target-ip-10-0-140-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:07:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T17:41:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-237-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-237.ec2.internal uid: 971ff768-5740-4b94-8212-59f0f7856669 resourceVersion: "68237" uid: 958bfc45-9f68-4600-b877-ae8798675079 spec: sourcePod: network-check-source-6f8b768455-2hq8s targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-11T17:47:41Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 981.442µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:17:41Z" - latency: 1.59756ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T18:17:41Z" - latency: 1.155423ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:16:41Z" - latency: 1.809213ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T18:16:41Z" - latency: 937.027µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:15:41Z" - latency: 2.538996ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T18:15:41Z" - latency: 903.466µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:14:41Z" - latency: 2.390524ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T18:14:41Z" - latency: 1.052567ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:13:41Z" - latency: 2.452232ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T18:13:41Z" kind: List metadata: resourceVersion: ""