apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:43:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-158-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-158.ec2.internal uid: 4bf6ff8c-b1c8-4169-b8d9-4538d715e471 resourceVersion: "60350" uid: e05db440-4942-4db6-8dbe-d402a1c882b7 spec: sourcePod: network-check-source-685456655f-gwqc5 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-09T20:50:58Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 943.181µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:18:58Z" - latency: 1.330443ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:17:58Z" - latency: 845.836µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:16:58Z" - latency: 934.85µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:15:58Z" - latency: 990.8µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:14:58Z" - latency: 826.629µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:13:58Z" - latency: 1.277888ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:12:58Z" - latency: 1.244227ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:11:58Z" - latency: 1.182124ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:10:58Z" - latency: 1.132721ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:09:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:43:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-158-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-158.ec2.internal uid: 4bf6ff8c-b1c8-4169-b8d9-4538d715e471 resourceVersion: "61155" uid: 9bb28a8f-abec-401b-96f6-dde068dd50f0 spec: sourcePod: network-check-source-685456655f-gwqc5 targetEndpoint: aad04e0a00c7240158723cd9ce356fdd-15faac1b766244fb.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-09T20:49:58Z" message: 'load-balancer-api-external: tcp connection to aad04e0a00c7240158723cd9ce356fdd-15faac1b766244fb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.790004ms message: 'load-balancer-api-external: tcp connection to aad04e0a00c7240158723cd9ce356fdd-15faac1b766244fb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:19:58Z" - latency: 8.186267ms message: 'load-balancer-api-external: resolved host name aad04e0a00c7240158723cd9ce356fdd-15faac1b766244fb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:19:58Z" - latency: 3.840387ms message: 'load-balancer-api-external: tcp connection to aad04e0a00c7240158723cd9ce356fdd-15faac1b766244fb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:18:58Z" - latency: 8.653414ms message: 'load-balancer-api-external: resolved host name aad04e0a00c7240158723cd9ce356fdd-15faac1b766244fb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:18:58Z" - latency: 5.033472ms message: 'load-balancer-api-external: tcp connection to aad04e0a00c7240158723cd9ce356fdd-15faac1b766244fb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:17:58Z" - latency: 8.077857ms message: 'load-balancer-api-external: resolved host name aad04e0a00c7240158723cd9ce356fdd-15faac1b766244fb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:17:58Z" - latency: 4.663816ms message: 'load-balancer-api-external: tcp connection to aad04e0a00c7240158723cd9ce356fdd-15faac1b766244fb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:16:58Z" - latency: 8.98132ms message: 'load-balancer-api-external: resolved host name aad04e0a00c7240158723cd9ce356fdd-15faac1b766244fb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:16:58Z" - latency: 5.319975ms message: 'load-balancer-api-external: tcp connection to aad04e0a00c7240158723cd9ce356fdd-15faac1b766244fb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:15:58Z" - latency: 9.499572ms message: 'load-balancer-api-external: resolved host name aad04e0a00c7240158723cd9ce356fdd-15faac1b766244fb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:15:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:43:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-158-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-158.ec2.internal uid: 4bf6ff8c-b1c8-4169-b8d9-4538d715e471 resourceVersion: "61154" uid: 152fe03f-cd42-43f5-80a1-40cfd37b0794 spec: sourcePod: network-check-source-685456655f-gwqc5 targetEndpoint: aad04e0a00c7240158723cd9ce356fdd-15faac1b766244fb.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-09T20:49:58Z" message: 'load-balancer-api-internal: tcp connection to aad04e0a00c7240158723cd9ce356fdd-15faac1b766244fb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.565631ms message: 'load-balancer-api-internal: tcp connection to aad04e0a00c7240158723cd9ce356fdd-15faac1b766244fb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:19:58Z" - latency: 8.108719ms message: 'load-balancer-api-internal: resolved host name aad04e0a00c7240158723cd9ce356fdd-15faac1b766244fb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:19:58Z" - latency: 6.12785ms message: 'load-balancer-api-internal: tcp connection to aad04e0a00c7240158723cd9ce356fdd-15faac1b766244fb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:18:58Z" - latency: 8.609175ms message: 'load-balancer-api-internal: resolved host name aad04e0a00c7240158723cd9ce356fdd-15faac1b766244fb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:18:58Z" - latency: 4.973924ms message: 'load-balancer-api-internal: tcp connection to aad04e0a00c7240158723cd9ce356fdd-15faac1b766244fb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:17:58Z" - latency: 8.03696ms message: 'load-balancer-api-internal: resolved host name aad04e0a00c7240158723cd9ce356fdd-15faac1b766244fb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:17:58Z" - latency: 3.922517ms message: 'load-balancer-api-internal: tcp connection to aad04e0a00c7240158723cd9ce356fdd-15faac1b766244fb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:16:58Z" - latency: 8.896755ms message: 'load-balancer-api-internal: resolved host name aad04e0a00c7240158723cd9ce356fdd-15faac1b766244fb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:16:58Z" - latency: 4.250962ms message: 'load-balancer-api-internal: tcp connection to aad04e0a00c7240158723cd9ce356fdd-15faac1b766244fb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:15:58Z" - latency: 9.420789ms message: 'load-balancer-api-internal: resolved host name aad04e0a00c7240158723cd9ce356fdd-15faac1b766244fb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:15:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:43:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-158-to-network-check-target-ip-10-0-129-99 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-158.ec2.internal uid: 4bf6ff8c-b1c8-4169-b8d9-4538d715e471 resourceVersion: "60347" uid: 5e2efdd9-9e78-4450-a0c3-c09ce369d8e7 spec: sourcePod: network-check-source-685456655f-gwqc5 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-09T20:50:58Z" message: 'network-check-target-ip-10-0-129-99: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.208678ms message: 'network-check-target-ip-10-0-129-99: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:18:58Z" - latency: 2.024818ms message: 'network-check-target-ip-10-0-129-99: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:17:58Z" - latency: 1.891505ms message: 'network-check-target-ip-10-0-129-99: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:16:58Z" - latency: 1.808525ms message: 'network-check-target-ip-10-0-129-99: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:15:58Z" - latency: 2.353293ms message: 'network-check-target-ip-10-0-129-99: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:14:58Z" - latency: 1.801143ms message: 'network-check-target-ip-10-0-129-99: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:13:58Z" - latency: 2.011501ms message: 'network-check-target-ip-10-0-129-99: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:12:58Z" - latency: 1.635741ms message: 'network-check-target-ip-10-0-129-99: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:11:58Z" - latency: 1.662228ms message: 'network-check-target-ip-10-0-129-99: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:10:58Z" - latency: 2.026163ms message: 'network-check-target-ip-10-0-129-99: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:09:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:43:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-158-to-network-check-target-ip-10-0-135-158 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-158.ec2.internal uid: 4bf6ff8c-b1c8-4169-b8d9-4538d715e471 resourceVersion: "60346" uid: 64c66591-77e2-4418-b9b3-6ed77f6d7930 spec: sourcePod: network-check-source-685456655f-gwqc5 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-09T20:50:58Z" message: 'network-check-target-ip-10-0-135-158: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.285688ms message: 'network-check-target-ip-10-0-135-158: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:18:58Z" - latency: 1.695753ms message: 'network-check-target-ip-10-0-135-158: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:17:58Z" - latency: 837.001µs message: 'network-check-target-ip-10-0-135-158: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:16:58Z" - latency: 1.134122ms message: 'network-check-target-ip-10-0-135-158: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:15:58Z" - latency: 999.833µs message: 'network-check-target-ip-10-0-135-158: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:14:58Z" - latency: 825.84µs message: 'network-check-target-ip-10-0-135-158: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:13:58Z" - latency: 845.509µs message: 'network-check-target-ip-10-0-135-158: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:12:58Z" - latency: 901.047µs message: 'network-check-target-ip-10-0-135-158: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:11:58Z" - latency: 829.546µs message: 'network-check-target-ip-10-0-135-158: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:10:58Z" - latency: 902.68µs message: 'network-check-target-ip-10-0-135-158: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:09:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:43:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-158-to-network-check-target-ip-10-0-137-187 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-158.ec2.internal uid: 4bf6ff8c-b1c8-4169-b8d9-4538d715e471 resourceVersion: "60349" uid: bc35ea50-a66d-4032-b25c-b0e526111d90 spec: sourcePod: network-check-source-685456655f-gwqc5 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-09T20:50:58Z" message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.447997ms message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:18:58Z" - latency: 2.393764ms message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:17:58Z" - latency: 1.852324ms message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:16:58Z" - latency: 1.976052ms message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:15:58Z" - latency: 2.103116ms message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:14:58Z" - latency: 2.216832ms message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:13:58Z" - latency: 2.084624ms message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:12:58Z" - latency: 2.104914ms message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:11:58Z" - latency: 1.951159ms message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:10:58Z" - latency: 2.038112ms message: 'network-check-target-ip-10-0-137-187: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:09:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:43:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-158-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-158.ec2.internal uid: 4bf6ff8c-b1c8-4169-b8d9-4538d715e471 resourceVersion: "61153" uid: f8b93b95-f2e8-48ff-a3c7-0f3aa609f9a5 spec: sourcePod: network-check-source-685456655f-gwqc5 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-09T20:49:58Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.09322ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:19:58Z" - latency: 1.738189ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T21:19:58Z" - latency: 1.085642ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:18:58Z" - latency: 2.202177ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T21:18:58Z" - latency: 887.597µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:17:58Z" - latency: 2.681063ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T21:17:58Z" - latency: 831.483µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:16:58Z" - latency: 1.922732ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T21:16:58Z" - latency: 971.829µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:15:58Z" - latency: 1.792689ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T21:15:58Z" kind: List metadata: resourceVersion: ""