apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-04T22:51:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-117-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-117.ec2.internal uid: cb196d18-ff2e-47ac-a8da-ecc3541d9b44 resourceVersion: "54945" uid: 4c2bdaab-f226-4e98-b3d6-7393e73252cf spec: sourcePod: network-check-source-685456655f-f5vkr targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-04T22:58:18Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.35696ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:19:18Z" - latency: 973.747µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:18:18Z" - latency: 954.92µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:17:18Z" - latency: 845.82µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:16:18Z" - latency: 1.048394ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:15:18Z" - latency: 958.989µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:14:18Z" - latency: 1.102042ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:13:18Z" - latency: 1.081109ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:12:18Z" - latency: 918.27µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:11:18Z" - latency: 833.916µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:10:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-04T22:51:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-117-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-117.ec2.internal uid: cb196d18-ff2e-47ac-a8da-ecc3541d9b44 resourceVersion: "56769" uid: b91a1193-69b0-41c0-9274-0377ee3e0b94 spec: sourcePod: network-check-source-685456655f-f5vkr targetEndpoint: ae1b4ba493f7843eeb7173e040647aa4-40286e33d34d52d1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-04T22:57:18Z" message: 'load-balancer-api-external: tcp connection to ae1b4ba493f7843eeb7173e040647aa4-40286e33d34d52d1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.573788ms message: 'load-balancer-api-external: tcp connection to ae1b4ba493f7843eeb7173e040647aa4-40286e33d34d52d1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:21:18Z" - latency: 7.567114ms message: 'load-balancer-api-external: resolved host name ae1b4ba493f7843eeb7173e040647aa4-40286e33d34d52d1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-04T23:21:18Z" - latency: 4.461222ms message: 'load-balancer-api-external: tcp connection to ae1b4ba493f7843eeb7173e040647aa4-40286e33d34d52d1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:20:18Z" - latency: 11.806852ms message: 'load-balancer-api-external: resolved host name ae1b4ba493f7843eeb7173e040647aa4-40286e33d34d52d1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-04T23:20:18Z" - latency: 4.800036ms message: 'load-balancer-api-external: tcp connection to ae1b4ba493f7843eeb7173e040647aa4-40286e33d34d52d1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:19:18Z" - latency: 12.504067ms message: 'load-balancer-api-external: resolved host name ae1b4ba493f7843eeb7173e040647aa4-40286e33d34d52d1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-04T23:19:18Z" - latency: 4.127296ms message: 'load-balancer-api-external: tcp connection to ae1b4ba493f7843eeb7173e040647aa4-40286e33d34d52d1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:18:18Z" - latency: 10.087816ms message: 'load-balancer-api-external: resolved host name ae1b4ba493f7843eeb7173e040647aa4-40286e33d34d52d1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-04T23:18:18Z" - latency: 4.60386ms message: 'load-balancer-api-external: tcp connection to ae1b4ba493f7843eeb7173e040647aa4-40286e33d34d52d1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:17:18Z" - latency: 13.446287ms message: 'load-balancer-api-external: resolved host name ae1b4ba493f7843eeb7173e040647aa4-40286e33d34d52d1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-04T23:17:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-04T22:51:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-117-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-117.ec2.internal uid: cb196d18-ff2e-47ac-a8da-ecc3541d9b44 resourceVersion: "56768" uid: fc6309ed-a2bd-42e3-a0c7-4dc082671d36 spec: sourcePod: network-check-source-685456655f-f5vkr targetEndpoint: ae1b4ba493f7843eeb7173e040647aa4-40286e33d34d52d1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-04T22:57:18Z" message: 'load-balancer-api-internal: tcp connection to ae1b4ba493f7843eeb7173e040647aa4-40286e33d34d52d1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.625524ms message: 'load-balancer-api-internal: tcp connection to ae1b4ba493f7843eeb7173e040647aa4-40286e33d34d52d1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:21:18Z" - latency: 7.542003ms message: 'load-balancer-api-internal: resolved host name ae1b4ba493f7843eeb7173e040647aa4-40286e33d34d52d1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-04T23:21:18Z" - latency: 4.74643ms message: 'load-balancer-api-internal: tcp connection to ae1b4ba493f7843eeb7173e040647aa4-40286e33d34d52d1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:20:18Z" - latency: 11.763643ms message: 'load-balancer-api-internal: resolved host name ae1b4ba493f7843eeb7173e040647aa4-40286e33d34d52d1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-04T23:20:18Z" - latency: 4.213417ms message: 'load-balancer-api-internal: tcp connection to ae1b4ba493f7843eeb7173e040647aa4-40286e33d34d52d1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:19:18Z" - latency: 12.479207ms message: 'load-balancer-api-internal: resolved host name ae1b4ba493f7843eeb7173e040647aa4-40286e33d34d52d1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-04T23:19:18Z" - latency: 4.666864ms message: 'load-balancer-api-internal: tcp connection to ae1b4ba493f7843eeb7173e040647aa4-40286e33d34d52d1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:18:18Z" - latency: 10.059924ms message: 'load-balancer-api-internal: resolved host name ae1b4ba493f7843eeb7173e040647aa4-40286e33d34d52d1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-04T23:18:18Z" - latency: 4.754224ms message: 'load-balancer-api-internal: tcp connection to ae1b4ba493f7843eeb7173e040647aa4-40286e33d34d52d1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:17:18Z" - latency: 13.414084ms message: 'load-balancer-api-internal: resolved host name ae1b4ba493f7843eeb7173e040647aa4-40286e33d34d52d1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-04T23:17:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-04T22:51:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-117-to-network-check-target-ip-10-0-128-32 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-117.ec2.internal uid: cb196d18-ff2e-47ac-a8da-ecc3541d9b44 resourceVersion: "54944" uid: 43f91c99-d133-4f25-ac0c-9545af6605af spec: sourcePod: network-check-source-685456655f-f5vkr targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-04T22:58:18Z" message: 'network-check-target-ip-10-0-128-32: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.653113ms message: 'network-check-target-ip-10-0-128-32: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:19:18Z" - latency: 2.640904ms message: 'network-check-target-ip-10-0-128-32: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:18:18Z" - latency: 2.507995ms message: 'network-check-target-ip-10-0-128-32: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:17:18Z" - latency: 2.413701ms message: 'network-check-target-ip-10-0-128-32: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:16:18Z" - latency: 2.907648ms message: 'network-check-target-ip-10-0-128-32: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:15:18Z" - latency: 2.827897ms message: 'network-check-target-ip-10-0-128-32: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:14:18Z" - latency: 2.76195ms message: 'network-check-target-ip-10-0-128-32: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:13:18Z" - latency: 2.920017ms message: 'network-check-target-ip-10-0-128-32: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:12:18Z" - latency: 2.440635ms message: 'network-check-target-ip-10-0-128-32: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:11:18Z" - latency: 2.452694ms message: 'network-check-target-ip-10-0-128-32: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:10:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-04T22:51:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-117-to-network-check-target-ip-10-0-134-172 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-117.ec2.internal uid: cb196d18-ff2e-47ac-a8da-ecc3541d9b44 resourceVersion: "54943" uid: 5580fff9-9392-4f47-90ed-f344e762b6dd spec: sourcePod: network-check-source-685456655f-f5vkr targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-04T22:58:18Z" message: 'network-check-target-ip-10-0-134-172: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.376006ms message: 'network-check-target-ip-10-0-134-172: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:19:18Z" - latency: 2.841404ms message: 'network-check-target-ip-10-0-134-172: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:18:18Z" - latency: 2.49215ms message: 'network-check-target-ip-10-0-134-172: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:17:18Z" - latency: 2.488356ms message: 'network-check-target-ip-10-0-134-172: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:16:18Z" - latency: 2.262763ms message: 'network-check-target-ip-10-0-134-172: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:15:18Z" - latency: 2.169528ms message: 'network-check-target-ip-10-0-134-172: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:14:18Z" - latency: 2.197753ms message: 'network-check-target-ip-10-0-134-172: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:13:18Z" - latency: 2.542169ms message: 'network-check-target-ip-10-0-134-172: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:12:18Z" - latency: 2.391658ms message: 'network-check-target-ip-10-0-134-172: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:11:18Z" - latency: 2.282254ms message: 'network-check-target-ip-10-0-134-172: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:10:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-04T22:51:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-117-to-network-check-target-ip-10-0-141-117 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-117.ec2.internal uid: cb196d18-ff2e-47ac-a8da-ecc3541d9b44 resourceVersion: "54942" uid: 0fa5a11d-a50a-4aca-8858-495c656a325f spec: sourcePod: network-check-source-685456655f-f5vkr targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-04T22:58:18Z" message: 'network-check-target-ip-10-0-141-117: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.43564ms message: 'network-check-target-ip-10-0-141-117: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:19:18Z" - latency: 878.641µs message: 'network-check-target-ip-10-0-141-117: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:18:18Z" - latency: 805.177µs message: 'network-check-target-ip-10-0-141-117: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:17:18Z" - latency: 888.926µs message: 'network-check-target-ip-10-0-141-117: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:16:18Z" - latency: 1.145152ms message: 'network-check-target-ip-10-0-141-117: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:15:18Z" - latency: 846.016µs message: 'network-check-target-ip-10-0-141-117: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:14:18Z" - latency: 829.877µs message: 'network-check-target-ip-10-0-141-117: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:13:18Z" - latency: 861.671µs message: 'network-check-target-ip-10-0-141-117: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:12:18Z" - latency: 1.058466ms message: 'network-check-target-ip-10-0-141-117: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:11:18Z" - latency: 1.052125ms message: 'network-check-target-ip-10-0-141-117: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:10:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-04T22:51:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-117-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-117.ec2.internal uid: cb196d18-ff2e-47ac-a8da-ecc3541d9b44 resourceVersion: "56767" uid: 026be864-587e-4596-a54e-89cc80f03da6 spec: sourcePod: network-check-source-685456655f-f5vkr targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-04T22:57:18Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.286261ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:21:18Z" - latency: 1.82641ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-04T23:21:18Z" - latency: 1.056593ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:20:18Z" - latency: 1.947836ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-04T23:20:18Z" - latency: 948.233µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:19:18Z" - latency: 1.710052ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-04T23:19:18Z" - latency: 1.055997ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:18:18Z" - latency: 1.870502ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-04T23:18:18Z" - latency: 779.384µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-04T23:17:18Z" - latency: 1.615845ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-04T23:17:18Z" kind: List metadata: resourceVersion: ""