apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T13:13:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-249-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-249.ec2.internal uid: 7df75408-3a40-4964-b2d4-fa46b14008f2 resourceVersion: "54410" uid: 4cf57f11-fdef-4a34-ad28-48c60a43bd9e spec: sourcePod: network-check-source-869dcfcdcd-7pj2h targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-10T13:20:30Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.289944ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:48:30Z" - latency: 1.231922ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:47:30Z" - latency: 899.34µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:46:30Z" - latency: 879.949µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:45:30Z" - latency: 1.142528ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:44:30Z" - latency: 903.348µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:43:30Z" - latency: 1.045378ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:42:30Z" - latency: 1.101671ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:41:30Z" - latency: 809.658µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:40:30Z" - latency: 1.460247ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:39:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T13:13:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-249-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-249.ec2.internal uid: 7df75408-3a40-4964-b2d4-fa46b14008f2 resourceVersion: "55430" uid: 1a46f759-406d-4acb-a6da-77566afb2df6 spec: sourcePod: network-check-source-869dcfcdcd-7pj2h targetEndpoint: a02fe35e0225c4d3f8ddd66ae1da6a64-ae844fcc0c9eab59.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T13:19:30Z" message: 'load-balancer-api-external: tcp connection to a02fe35e0225c4d3f8ddd66ae1da6a64-ae844fcc0c9eab59.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.141589ms message: 'load-balancer-api-external: tcp connection to a02fe35e0225c4d3f8ddd66ae1da6a64-ae844fcc0c9eab59.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:49:30Z" - latency: 6.478072ms message: 'load-balancer-api-external: resolved host name a02fe35e0225c4d3f8ddd66ae1da6a64-ae844fcc0c9eab59.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T13:49:30Z" - latency: 4.752383ms message: 'load-balancer-api-external: tcp connection to a02fe35e0225c4d3f8ddd66ae1da6a64-ae844fcc0c9eab59.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:48:30Z" - latency: 7.253257ms message: 'load-balancer-api-external: resolved host name a02fe35e0225c4d3f8ddd66ae1da6a64-ae844fcc0c9eab59.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T13:48:30Z" - latency: 3.643968ms message: 'load-balancer-api-external: tcp connection to a02fe35e0225c4d3f8ddd66ae1da6a64-ae844fcc0c9eab59.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:47:30Z" - latency: 9.966506ms message: 'load-balancer-api-external: resolved host name a02fe35e0225c4d3f8ddd66ae1da6a64-ae844fcc0c9eab59.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T13:47:30Z" - latency: 4.678274ms message: 'load-balancer-api-external: tcp connection to a02fe35e0225c4d3f8ddd66ae1da6a64-ae844fcc0c9eab59.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:46:30Z" - latency: 7.339179ms message: 'load-balancer-api-external: resolved host name a02fe35e0225c4d3f8ddd66ae1da6a64-ae844fcc0c9eab59.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T13:46:30Z" - latency: 3.541569ms message: 'load-balancer-api-external: tcp connection to a02fe35e0225c4d3f8ddd66ae1da6a64-ae844fcc0c9eab59.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:45:30Z" - latency: 6.814983ms message: 'load-balancer-api-external: resolved host name a02fe35e0225c4d3f8ddd66ae1da6a64-ae844fcc0c9eab59.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T13:45:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T13:13:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-249-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-249.ec2.internal uid: 7df75408-3a40-4964-b2d4-fa46b14008f2 resourceVersion: "55429" uid: de918646-e2be-4058-8be7-620a7e97a86d spec: sourcePod: network-check-source-869dcfcdcd-7pj2h targetEndpoint: a02fe35e0225c4d3f8ddd66ae1da6a64-ae844fcc0c9eab59.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T13:19:30Z" message: 'load-balancer-api-internal: tcp connection to a02fe35e0225c4d3f8ddd66ae1da6a64-ae844fcc0c9eab59.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.789361ms message: 'load-balancer-api-internal: tcp connection to a02fe35e0225c4d3f8ddd66ae1da6a64-ae844fcc0c9eab59.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:49:30Z" - latency: 6.417399ms message: 'load-balancer-api-internal: resolved host name a02fe35e0225c4d3f8ddd66ae1da6a64-ae844fcc0c9eab59.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T13:49:30Z" - latency: 4.776241ms message: 'load-balancer-api-internal: tcp connection to a02fe35e0225c4d3f8ddd66ae1da6a64-ae844fcc0c9eab59.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:48:30Z" - latency: 7.180315ms message: 'load-balancer-api-internal: resolved host name a02fe35e0225c4d3f8ddd66ae1da6a64-ae844fcc0c9eab59.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T13:48:30Z" - latency: 3.659741ms message: 'load-balancer-api-internal: tcp connection to a02fe35e0225c4d3f8ddd66ae1da6a64-ae844fcc0c9eab59.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:47:30Z" - latency: 9.933138ms message: 'load-balancer-api-internal: resolved host name a02fe35e0225c4d3f8ddd66ae1da6a64-ae844fcc0c9eab59.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T13:47:30Z" - latency: 4.741031ms message: 'load-balancer-api-internal: tcp connection to a02fe35e0225c4d3f8ddd66ae1da6a64-ae844fcc0c9eab59.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:46:30Z" - latency: 7.253905ms message: 'load-balancer-api-internal: resolved host name a02fe35e0225c4d3f8ddd66ae1da6a64-ae844fcc0c9eab59.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T13:46:30Z" - latency: 5.602638ms message: 'load-balancer-api-internal: tcp connection to a02fe35e0225c4d3f8ddd66ae1da6a64-ae844fcc0c9eab59.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:45:30Z" - latency: 6.767479ms message: 'load-balancer-api-internal: resolved host name a02fe35e0225c4d3f8ddd66ae1da6a64-ae844fcc0c9eab59.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T13:45:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T13:13:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-249-to-network-check-target-ip-10-0-128-249 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-249.ec2.internal uid: 7df75408-3a40-4964-b2d4-fa46b14008f2 resourceVersion: "54407" uid: 519bfea4-a674-4d28-ac93-4a37fa7273c4 spec: sourcePod: network-check-source-869dcfcdcd-7pj2h targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-10T13:20:30Z" message: 'network-check-target-ip-10-0-128-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.36332ms message: 'network-check-target-ip-10-0-128-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:48:30Z" - latency: 1.514343ms message: 'network-check-target-ip-10-0-128-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:47:30Z" - latency: 1.020192ms message: 'network-check-target-ip-10-0-128-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:46:30Z" - latency: 867.929µs message: 'network-check-target-ip-10-0-128-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:45:30Z" - latency: 810.877µs message: 'network-check-target-ip-10-0-128-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:44:30Z" - latency: 1.128023ms message: 'network-check-target-ip-10-0-128-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:43:30Z" - latency: 907.943µs message: 'network-check-target-ip-10-0-128-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:42:30Z" - latency: 895.168µs message: 'network-check-target-ip-10-0-128-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:41:30Z" - latency: 779.753µs message: 'network-check-target-ip-10-0-128-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:40:30Z" - latency: 1.518912ms message: 'network-check-target-ip-10-0-128-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:39:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T13:13:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-249-to-network-check-target-ip-10-0-133-196 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-249.ec2.internal uid: 7df75408-3a40-4964-b2d4-fa46b14008f2 resourceVersion: "54408" uid: 698cf263-b725-4abe-84cd-d6e52b8a894e spec: sourcePod: network-check-source-869dcfcdcd-7pj2h targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-10T13:20:30Z" message: 'network-check-target-ip-10-0-133-196: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.951476ms message: 'network-check-target-ip-10-0-133-196: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:48:30Z" - latency: 1.751197ms message: 'network-check-target-ip-10-0-133-196: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:47:30Z" - latency: 1.931272ms message: 'network-check-target-ip-10-0-133-196: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:46:30Z" - latency: 1.697126ms message: 'network-check-target-ip-10-0-133-196: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:45:30Z" - latency: 1.972415ms message: 'network-check-target-ip-10-0-133-196: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:44:30Z" - latency: 1.98188ms message: 'network-check-target-ip-10-0-133-196: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:43:30Z" - latency: 1.917167ms message: 'network-check-target-ip-10-0-133-196: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:42:30Z" - latency: 1.936739ms message: 'network-check-target-ip-10-0-133-196: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:41:30Z" - latency: 1.823688ms message: 'network-check-target-ip-10-0-133-196: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:40:30Z" - latency: 2.084335ms message: 'network-check-target-ip-10-0-133-196: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:39:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T13:13:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-249-to-network-check-target-ip-10-0-140-11 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-249.ec2.internal uid: 7df75408-3a40-4964-b2d4-fa46b14008f2 resourceVersion: "54409" uid: 2a765694-0f1b-4ba9-831d-44bdfaa74c84 spec: sourcePod: network-check-source-869dcfcdcd-7pj2h targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-10T13:20:30Z" message: 'network-check-target-ip-10-0-140-11: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.260724ms message: 'network-check-target-ip-10-0-140-11: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:48:30Z" - latency: 2.074964ms message: 'network-check-target-ip-10-0-140-11: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:47:30Z" - latency: 2.272022ms message: 'network-check-target-ip-10-0-140-11: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:46:30Z" - latency: 2.011945ms message: 'network-check-target-ip-10-0-140-11: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:45:30Z" - latency: 2.253318ms message: 'network-check-target-ip-10-0-140-11: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:44:30Z" - latency: 2.122277ms message: 'network-check-target-ip-10-0-140-11: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:43:30Z" - latency: 2.137984ms message: 'network-check-target-ip-10-0-140-11: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:42:30Z" - latency: 2.299815ms message: 'network-check-target-ip-10-0-140-11: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:41:30Z" - latency: 2.09973ms message: 'network-check-target-ip-10-0-140-11: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:40:30Z" - latency: 2.493448ms message: 'network-check-target-ip-10-0-140-11: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:39:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T13:13:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-249-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-249.ec2.internal uid: 7df75408-3a40-4964-b2d4-fa46b14008f2 resourceVersion: "55428" uid: 2a7be1f1-c3df-4dd9-91d0-ecb1ea4bd8e7 spec: sourcePod: network-check-source-869dcfcdcd-7pj2h targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-10T13:19:30Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 931.851µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:49:30Z" - latency: 1.899587ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T13:49:30Z" - latency: 925.608µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:48:30Z" - latency: 1.787291ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T13:48:30Z" - latency: 839.221µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:47:30Z" - latency: 2.332325ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T13:47:30Z" - latency: 886.716µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:46:30Z" - latency: 2.29205ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T13:46:30Z" - latency: 952.553µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:45:30Z" - latency: 1.660222ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T13:45:30Z" kind: List metadata: resourceVersion: ""