apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T15:15:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-180-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-180.ec2.internal uid: 2bda4d0c-5365-49ed-b74a-186dbb79c0f4 resourceVersion: "54188" uid: 50e79e79-c445-4466-b324-f8665644b4fe spec: sourcePod: network-check-source-685456655f-nxwbl targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-08T15:22:55Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 926.322µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:43:55Z" - latency: 1.301001ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:42:55Z" - latency: 1.229831ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:41:55Z" - latency: 1.132727ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:40:55Z" - latency: 1.184114ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:39:55Z" - latency: 938.8µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:38:55Z" - latency: 1.127305ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:37:55Z" - latency: 1.071785ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:36:55Z" - latency: 861.915µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:35:55Z" - latency: 1.039594ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:34:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T15:15:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-180-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-180.ec2.internal uid: 2bda4d0c-5365-49ed-b74a-186dbb79c0f4 resourceVersion: "55944" uid: 329082e2-0434-4d58-85ea-1e776ee30596 spec: sourcePod: network-check-source-685456655f-nxwbl targetEndpoint: aeedefe238a404e80ad4941acf7a0704-6e1d589035763a62.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-08T15:21:55Z" message: 'load-balancer-api-external: tcp connection to aeedefe238a404e80ad4941acf7a0704-6e1d589035763a62.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.593229ms message: 'load-balancer-api-external: tcp connection to aeedefe238a404e80ad4941acf7a0704-6e1d589035763a62.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:45:55Z" - latency: 14.686511ms message: 'load-balancer-api-external: resolved host name aeedefe238a404e80ad4941acf7a0704-6e1d589035763a62.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T15:45:55Z" - latency: 5.530412ms message: 'load-balancer-api-external: tcp connection to aeedefe238a404e80ad4941acf7a0704-6e1d589035763a62.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:44:55Z" - latency: 8.692187ms message: 'load-balancer-api-external: resolved host name aeedefe238a404e80ad4941acf7a0704-6e1d589035763a62.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T15:44:55Z" - latency: 3.628228ms message: 'load-balancer-api-external: tcp connection to aeedefe238a404e80ad4941acf7a0704-6e1d589035763a62.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:43:55Z" - latency: 11.961764ms message: 'load-balancer-api-external: resolved host name aeedefe238a404e80ad4941acf7a0704-6e1d589035763a62.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T15:43:55Z" - latency: 3.746568ms message: 'load-balancer-api-external: tcp connection to aeedefe238a404e80ad4941acf7a0704-6e1d589035763a62.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:42:55Z" - latency: 11.228443ms message: 'load-balancer-api-external: resolved host name aeedefe238a404e80ad4941acf7a0704-6e1d589035763a62.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T15:42:55Z" - latency: 5.811262ms message: 'load-balancer-api-external: tcp connection to aeedefe238a404e80ad4941acf7a0704-6e1d589035763a62.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:41:55Z" - latency: 8.783038ms message: 'load-balancer-api-external: resolved host name aeedefe238a404e80ad4941acf7a0704-6e1d589035763a62.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T15:41:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T15:15:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-180-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-180.ec2.internal uid: 2bda4d0c-5365-49ed-b74a-186dbb79c0f4 resourceVersion: "55945" uid: 12ffa191-d8a8-473c-b86c-b9bd95d81491 spec: sourcePod: network-check-source-685456655f-nxwbl targetEndpoint: aeedefe238a404e80ad4941acf7a0704-6e1d589035763a62.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-08T15:21:55Z" message: 'load-balancer-api-internal: tcp connection to aeedefe238a404e80ad4941acf7a0704-6e1d589035763a62.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.772011ms message: 'load-balancer-api-internal: tcp connection to aeedefe238a404e80ad4941acf7a0704-6e1d589035763a62.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:45:55Z" - latency: 14.650587ms message: 'load-balancer-api-internal: resolved host name aeedefe238a404e80ad4941acf7a0704-6e1d589035763a62.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T15:45:55Z" - latency: 5.484843ms message: 'load-balancer-api-internal: tcp connection to aeedefe238a404e80ad4941acf7a0704-6e1d589035763a62.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:44:55Z" - latency: 8.644018ms message: 'load-balancer-api-internal: resolved host name aeedefe238a404e80ad4941acf7a0704-6e1d589035763a62.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T15:44:55Z" - latency: 3.629895ms message: 'load-balancer-api-internal: tcp connection to aeedefe238a404e80ad4941acf7a0704-6e1d589035763a62.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:43:55Z" - latency: 11.894334ms message: 'load-balancer-api-internal: resolved host name aeedefe238a404e80ad4941acf7a0704-6e1d589035763a62.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T15:43:55Z" - latency: 4.247318ms message: 'load-balancer-api-internal: tcp connection to aeedefe238a404e80ad4941acf7a0704-6e1d589035763a62.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:42:55Z" - latency: 11.28104ms message: 'load-balancer-api-internal: resolved host name aeedefe238a404e80ad4941acf7a0704-6e1d589035763a62.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T15:42:55Z" - latency: 4.439231ms message: 'load-balancer-api-internal: tcp connection to aeedefe238a404e80ad4941acf7a0704-6e1d589035763a62.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:41:55Z" - latency: 8.815453ms message: 'load-balancer-api-internal: resolved host name aeedefe238a404e80ad4941acf7a0704-6e1d589035763a62.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T15:41:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T15:15:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-180-to-network-check-target-ip-10-0-128-19 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-180.ec2.internal uid: 2bda4d0c-5365-49ed-b74a-186dbb79c0f4 resourceVersion: "54187" uid: 1b079efe-9c5c-4f86-b931-fbd8f348c633 spec: sourcePod: network-check-source-685456655f-nxwbl targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-08T15:22:55Z" message: 'network-check-target-ip-10-0-128-19: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.305442ms message: 'network-check-target-ip-10-0-128-19: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:43:55Z" - latency: 2.290063ms message: 'network-check-target-ip-10-0-128-19: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:42:55Z" - latency: 2.380703ms message: 'network-check-target-ip-10-0-128-19: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:41:55Z" - latency: 2.386359ms message: 'network-check-target-ip-10-0-128-19: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:40:55Z" - latency: 2.663342ms message: 'network-check-target-ip-10-0-128-19: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:39:55Z" - latency: 2.431183ms message: 'network-check-target-ip-10-0-128-19: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:38:55Z" - latency: 1.95724ms message: 'network-check-target-ip-10-0-128-19: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:37:55Z" - latency: 2.679963ms message: 'network-check-target-ip-10-0-128-19: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:36:55Z" - latency: 2.571527ms message: 'network-check-target-ip-10-0-128-19: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:35:55Z" - latency: 2.33052ms message: 'network-check-target-ip-10-0-128-19: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:34:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T15:15:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-180-to-network-check-target-ip-10-0-129-54 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-180.ec2.internal uid: 2bda4d0c-5365-49ed-b74a-186dbb79c0f4 resourceVersion: "54186" uid: 053ccd3c-f815-4dc0-aecf-1066b18f32d8 spec: sourcePod: network-check-source-685456655f-nxwbl targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-08T15:22:55Z" message: 'network-check-target-ip-10-0-129-54: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.915446ms message: 'network-check-target-ip-10-0-129-54: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:43:55Z" - latency: 1.607491ms message: 'network-check-target-ip-10-0-129-54: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:42:55Z" - latency: 2.11567ms message: 'network-check-target-ip-10-0-129-54: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:41:55Z" - latency: 2.387653ms message: 'network-check-target-ip-10-0-129-54: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:40:55Z" - latency: 2.207698ms message: 'network-check-target-ip-10-0-129-54: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:39:55Z" - latency: 1.925332ms message: 'network-check-target-ip-10-0-129-54: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:38:55Z" - latency: 1.808543ms message: 'network-check-target-ip-10-0-129-54: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:37:55Z" - latency: 2.412534ms message: 'network-check-target-ip-10-0-129-54: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:36:55Z" - latency: 2.185781ms message: 'network-check-target-ip-10-0-129-54: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:35:55Z" - latency: 2.165862ms message: 'network-check-target-ip-10-0-129-54: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:34:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T15:15:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-180-to-network-check-target-ip-10-0-134-180 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-180.ec2.internal uid: 2bda4d0c-5365-49ed-b74a-186dbb79c0f4 resourceVersion: "54185" uid: 1c243141-4b51-4520-bd1b-65e98410e03c spec: sourcePod: network-check-source-685456655f-nxwbl targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-08T15:22:55Z" message: 'network-check-target-ip-10-0-134-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.442713ms message: 'network-check-target-ip-10-0-134-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:43:55Z" - latency: 909.326µs message: 'network-check-target-ip-10-0-134-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:42:55Z" - latency: 987.308µs message: 'network-check-target-ip-10-0-134-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:41:55Z" - latency: 820.201µs message: 'network-check-target-ip-10-0-134-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:40:55Z" - latency: 980.177µs message: 'network-check-target-ip-10-0-134-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:39:55Z" - latency: 1.101728ms message: 'network-check-target-ip-10-0-134-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:38:55Z" - latency: 977.562µs message: 'network-check-target-ip-10-0-134-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:37:55Z" - latency: 939.053µs message: 'network-check-target-ip-10-0-134-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:36:55Z" - latency: 1.103488ms message: 'network-check-target-ip-10-0-134-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:35:55Z" - latency: 1.079623ms message: 'network-check-target-ip-10-0-134-180: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:34:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T15:15:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-180-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-180.ec2.internal uid: 2bda4d0c-5365-49ed-b74a-186dbb79c0f4 resourceVersion: "55942" uid: e37f090b-ff7d-47f0-98b6-a147060d29e4 spec: sourcePod: network-check-source-685456655f-nxwbl targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-08T15:21:55Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 944.877µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:45:55Z" - latency: 1.765636ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T15:45:55Z" - latency: 847.703µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:44:55Z" - latency: 2.155509ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T15:44:55Z" - latency: 1.158894ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:43:55Z" - latency: 2.429736ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T15:43:55Z" - latency: 955.964µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:42:55Z" - latency: 1.649173ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T15:42:55Z" - latency: 1.095241ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:41:55Z" - latency: 1.967715ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T15:41:55Z" kind: List metadata: resourceVersion: ""