apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T07:29:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-67-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-67.ec2.internal uid: 1d6e9139-9e04-4958-9d25-2fed10e13618 resourceVersion: "22488" uid: b9810bdd-6bf8-44e9-8d87-5602d142106e spec: sourcePod: network-check-source-6f8b768455-kjq4x targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-15T07:36:19Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.011114ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:57:19Z" - latency: 1.006402ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:56:19Z" - latency: 2.218341ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:55:19Z" - latency: 1.418613ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:54:19Z" - latency: 1.029764ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:53:19Z" - latency: 990.538µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:52:19Z" - latency: 1.069462ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:51:19Z" - latency: 824.791µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:50:19Z" - latency: 2.369842ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:49:19Z" - latency: 963.997µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:48:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T07:29:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-67-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-67.ec2.internal uid: 1d6e9139-9e04-4958-9d25-2fed10e13618 resourceVersion: "23192" uid: 6364aae8-524d-4235-b3d5-a45a50674873 spec: sourcePod: network-check-source-6f8b768455-kjq4x targetEndpoint: af5be3d25cea049e5b2ca1030a3d1410-379bade06549da3b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-15T07:35:19Z" message: 'load-balancer-api-external: tcp connection to af5be3d25cea049e5b2ca1030a3d1410-379bade06549da3b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.02153ms message: 'load-balancer-api-external: tcp connection to af5be3d25cea049e5b2ca1030a3d1410-379bade06549da3b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:59:19Z" - latency: 6.551112ms message: 'load-balancer-api-external: resolved host name af5be3d25cea049e5b2ca1030a3d1410-379bade06549da3b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T07:59:19Z" - latency: 4.614804ms message: 'load-balancer-api-external: tcp connection to af5be3d25cea049e5b2ca1030a3d1410-379bade06549da3b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:58:19Z" - latency: 8.683594ms message: 'load-balancer-api-external: resolved host name af5be3d25cea049e5b2ca1030a3d1410-379bade06549da3b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T07:58:19Z" - latency: 4.546196ms message: 'load-balancer-api-external: tcp connection to af5be3d25cea049e5b2ca1030a3d1410-379bade06549da3b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:57:19Z" - latency: 6.875924ms message: 'load-balancer-api-external: resolved host name af5be3d25cea049e5b2ca1030a3d1410-379bade06549da3b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T07:57:19Z" - latency: 4.366572ms message: 'load-balancer-api-external: tcp connection to af5be3d25cea049e5b2ca1030a3d1410-379bade06549da3b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:56:19Z" - latency: 8.523634ms message: 'load-balancer-api-external: resolved host name af5be3d25cea049e5b2ca1030a3d1410-379bade06549da3b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T07:56:19Z" - latency: 5.54654ms message: 'load-balancer-api-external: tcp connection to af5be3d25cea049e5b2ca1030a3d1410-379bade06549da3b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:55:19Z" - latency: 8.731038ms message: 'load-balancer-api-external: resolved host name af5be3d25cea049e5b2ca1030a3d1410-379bade06549da3b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T07:55:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T07:29:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-67-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-67.ec2.internal uid: 1d6e9139-9e04-4958-9d25-2fed10e13618 resourceVersion: "23193" uid: ee6f3c66-61ad-4b5a-a1d0-637a1fbdfe34 spec: sourcePod: network-check-source-6f8b768455-kjq4x targetEndpoint: af5be3d25cea049e5b2ca1030a3d1410-379bade06549da3b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-15T07:35:19Z" message: 'load-balancer-api-internal: tcp connection to af5be3d25cea049e5b2ca1030a3d1410-379bade06549da3b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.984455ms message: 'load-balancer-api-internal: tcp connection to af5be3d25cea049e5b2ca1030a3d1410-379bade06549da3b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:59:19Z" - latency: 6.642641ms message: 'load-balancer-api-internal: resolved host name af5be3d25cea049e5b2ca1030a3d1410-379bade06549da3b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T07:59:19Z" - latency: 4.621298ms message: 'load-balancer-api-internal: tcp connection to af5be3d25cea049e5b2ca1030a3d1410-379bade06549da3b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:58:19Z" - latency: 8.74054ms message: 'load-balancer-api-internal: resolved host name af5be3d25cea049e5b2ca1030a3d1410-379bade06549da3b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T07:58:19Z" - latency: 4.47832ms message: 'load-balancer-api-internal: tcp connection to af5be3d25cea049e5b2ca1030a3d1410-379bade06549da3b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:57:19Z" - latency: 6.973911ms message: 'load-balancer-api-internal: resolved host name af5be3d25cea049e5b2ca1030a3d1410-379bade06549da3b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T07:57:19Z" - latency: 3.817229ms message: 'load-balancer-api-internal: tcp connection to af5be3d25cea049e5b2ca1030a3d1410-379bade06549da3b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:56:19Z" - latency: 8.62103ms message: 'load-balancer-api-internal: resolved host name af5be3d25cea049e5b2ca1030a3d1410-379bade06549da3b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T07:56:19Z" - latency: 5.538452ms message: 'load-balancer-api-internal: tcp connection to af5be3d25cea049e5b2ca1030a3d1410-379bade06549da3b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:55:19Z" - latency: 8.554592ms message: 'load-balancer-api-internal: resolved host name af5be3d25cea049e5b2ca1030a3d1410-379bade06549da3b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T07:55:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T07:29:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-67-to-network-check-target-ip-10-0-135-38 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-67.ec2.internal uid: 1d6e9139-9e04-4958-9d25-2fed10e13618 resourceVersion: "22487" uid: 6233d7e0-f52b-4b18-b77b-6e13394b11e0 spec: sourcePod: network-check-source-6f8b768455-kjq4x targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-15T07:36:19Z" message: 'network-check-target-ip-10-0-135-38: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.367674ms message: 'network-check-target-ip-10-0-135-38: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:57:19Z" - latency: 2.155047ms message: 'network-check-target-ip-10-0-135-38: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:56:19Z" - latency: 2.267386ms message: 'network-check-target-ip-10-0-135-38: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:55:19Z" - latency: 2.432229ms message: 'network-check-target-ip-10-0-135-38: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:54:19Z" - latency: 2.26972ms message: 'network-check-target-ip-10-0-135-38: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:53:19Z" - latency: 2.036999ms message: 'network-check-target-ip-10-0-135-38: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:52:19Z" - latency: 2.235749ms message: 'network-check-target-ip-10-0-135-38: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:51:19Z" - latency: 1.845493ms message: 'network-check-target-ip-10-0-135-38: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:50:19Z" - latency: 2.28176ms message: 'network-check-target-ip-10-0-135-38: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:49:19Z" - latency: 2.268916ms message: 'network-check-target-ip-10-0-135-38: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:48:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T07:29:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-67-to-network-check-target-ip-10-0-137-104 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-67.ec2.internal uid: 1d6e9139-9e04-4958-9d25-2fed10e13618 resourceVersion: "22486" uid: 1f8ee2ad-d2ea-49e9-9e77-b76e3cc88c84 spec: sourcePod: network-check-source-6f8b768455-kjq4x targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-15T07:36:19Z" message: 'network-check-target-ip-10-0-137-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.228291ms message: 'network-check-target-ip-10-0-137-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:57:19Z" - latency: 2.009886ms message: 'network-check-target-ip-10-0-137-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:56:19Z" - latency: 2.6352ms message: 'network-check-target-ip-10-0-137-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:55:19Z" - latency: 2.16452ms message: 'network-check-target-ip-10-0-137-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:54:19Z" - latency: 2.253039ms message: 'network-check-target-ip-10-0-137-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:53:19Z" - latency: 2.205905ms message: 'network-check-target-ip-10-0-137-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:52:19Z" - latency: 2.646727ms message: 'network-check-target-ip-10-0-137-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:51:19Z" - latency: 2.356942ms message: 'network-check-target-ip-10-0-137-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:50:19Z" - latency: 2.458482ms message: 'network-check-target-ip-10-0-137-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:49:19Z" - latency: 2.779625ms message: 'network-check-target-ip-10-0-137-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:48:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T07:29:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-67-to-network-check-target-ip-10-0-139-67 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-67.ec2.internal uid: 1d6e9139-9e04-4958-9d25-2fed10e13618 resourceVersion: "22485" uid: ea24153b-a80b-4fca-9305-987eaf4b5303 spec: sourcePod: network-check-source-6f8b768455-kjq4x targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-15T07:36:19Z" message: 'network-check-target-ip-10-0-139-67: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 906.685µs message: 'network-check-target-ip-10-0-139-67: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:57:19Z" - latency: 903.508µs message: 'network-check-target-ip-10-0-139-67: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:56:19Z" - latency: 1.364185ms message: 'network-check-target-ip-10-0-139-67: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:55:19Z" - latency: 1.162604ms message: 'network-check-target-ip-10-0-139-67: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:54:19Z" - latency: 1.013731ms message: 'network-check-target-ip-10-0-139-67: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:53:19Z" - latency: 1.106149ms message: 'network-check-target-ip-10-0-139-67: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:52:19Z" - latency: 1.668453ms message: 'network-check-target-ip-10-0-139-67: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:51:19Z" - latency: 1.42878ms message: 'network-check-target-ip-10-0-139-67: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:50:19Z" - latency: 1.082392ms message: 'network-check-target-ip-10-0-139-67: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:49:19Z" - latency: 1.735808ms message: 'network-check-target-ip-10-0-139-67: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:48:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T07:29:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-67-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-67.ec2.internal uid: 1d6e9139-9e04-4958-9d25-2fed10e13618 resourceVersion: "23191" uid: 9440f1e3-ea0b-4166-9296-f511730fb669 spec: sourcePod: network-check-source-6f8b768455-kjq4x targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-15T07:35:19Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 813.238µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:59:19Z" - latency: 1.620853ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T07:59:19Z" - latency: 946.956µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:58:19Z" - latency: 1.63896ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T07:58:19Z" - latency: 840.17µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:57:19Z" - latency: 1.678761ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T07:57:19Z" - latency: 834.286µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:56:19Z" - latency: 1.872632ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T07:56:19Z" - latency: 853.504µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T07:55:19Z" - latency: 3.423349ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T07:55:19Z" kind: List metadata: resourceVersion: ""