apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T12:42:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-88-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-88.ec2.internal uid: 7fe0adb3-00e2-476b-b823-df2c958eea53 resourceVersion: "22079" uid: bd79d28b-275f-4afd-be2e-072d2e6853d7 spec: sourcePod: network-check-source-56499946bc-9fqqb targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-02T12:50:00Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.172091ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:04:00Z" - latency: 1.292712ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:03:00Z" - latency: 1.705945ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:02:00Z" - latency: 1.253047ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:01:00Z" - latency: 1.083552ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:00:00Z" - latency: 1.440945ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:59:00Z" - latency: 1.08209ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:58:00Z" - latency: 898.385µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:57:00Z" - latency: 1.065745ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:56:00Z" - latency: 1.21194ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:55:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T12:42:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-88-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-88.ec2.internal uid: 7fe0adb3-00e2-476b-b823-df2c958eea53 resourceVersion: "20458" uid: 42eff083-f218-4fca-9e32-7a5d3be028a2 spec: sourcePod: network-check-source-56499946bc-9fqqb targetEndpoint: a27e46730322d4ae68398230f9cb59be-2f3115ca7daefb02.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T12:49:00Z" message: 'load-balancer-api-external: tcp connection to a27e46730322d4ae68398230f9cb59be-2f3115ca7daefb02.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.74815ms message: 'load-balancer-api-external: tcp connection to a27e46730322d4ae68398230f9cb59be-2f3115ca7daefb02.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:01:00Z" - latency: 8.860228ms message: 'load-balancer-api-external: resolved host name a27e46730322d4ae68398230f9cb59be-2f3115ca7daefb02.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T13:01:00Z" - latency: 5.228162ms message: 'load-balancer-api-external: tcp connection to a27e46730322d4ae68398230f9cb59be-2f3115ca7daefb02.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:00:00Z" - latency: 10.605904ms message: 'load-balancer-api-external: resolved host name a27e46730322d4ae68398230f9cb59be-2f3115ca7daefb02.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T13:00:00Z" - latency: 4.699629ms message: 'load-balancer-api-external: tcp connection to a27e46730322d4ae68398230f9cb59be-2f3115ca7daefb02.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:59:00Z" - latency: 8.449183ms message: 'load-balancer-api-external: resolved host name a27e46730322d4ae68398230f9cb59be-2f3115ca7daefb02.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T12:59:00Z" - latency: 4.966246ms message: 'load-balancer-api-external: tcp connection to a27e46730322d4ae68398230f9cb59be-2f3115ca7daefb02.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:58:00Z" - latency: 9.425897ms message: 'load-balancer-api-external: resolved host name a27e46730322d4ae68398230f9cb59be-2f3115ca7daefb02.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T12:58:00Z" - latency: 5.26278ms message: 'load-balancer-api-external: tcp connection to a27e46730322d4ae68398230f9cb59be-2f3115ca7daefb02.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:57:00Z" - latency: 9.650528ms message: 'load-balancer-api-external: resolved host name a27e46730322d4ae68398230f9cb59be-2f3115ca7daefb02.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T12:57:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T12:42:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-88-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-88.ec2.internal uid: 7fe0adb3-00e2-476b-b823-df2c958eea53 resourceVersion: "20460" uid: 17369e36-f551-4256-9aac-f12faaacaceb spec: sourcePod: network-check-source-56499946bc-9fqqb targetEndpoint: a27e46730322d4ae68398230f9cb59be-2f3115ca7daefb02.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T12:49:00Z" message: 'load-balancer-api-internal: tcp connection to a27e46730322d4ae68398230f9cb59be-2f3115ca7daefb02.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.744586ms message: 'load-balancer-api-internal: tcp connection to a27e46730322d4ae68398230f9cb59be-2f3115ca7daefb02.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:01:00Z" - latency: 8.802952ms message: 'load-balancer-api-internal: resolved host name a27e46730322d4ae68398230f9cb59be-2f3115ca7daefb02.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T13:01:00Z" - latency: 5.256378ms message: 'load-balancer-api-internal: tcp connection to a27e46730322d4ae68398230f9cb59be-2f3115ca7daefb02.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:00:00Z" - latency: 10.595578ms message: 'load-balancer-api-internal: resolved host name a27e46730322d4ae68398230f9cb59be-2f3115ca7daefb02.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T13:00:00Z" - latency: 4.693355ms message: 'load-balancer-api-internal: tcp connection to a27e46730322d4ae68398230f9cb59be-2f3115ca7daefb02.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:59:00Z" - latency: 8.374359ms message: 'load-balancer-api-internal: resolved host name a27e46730322d4ae68398230f9cb59be-2f3115ca7daefb02.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T12:59:00Z" - latency: 3.818965ms message: 'load-balancer-api-internal: tcp connection to a27e46730322d4ae68398230f9cb59be-2f3115ca7daefb02.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:58:00Z" - latency: 9.358606ms message: 'load-balancer-api-internal: resolved host name a27e46730322d4ae68398230f9cb59be-2f3115ca7daefb02.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T12:58:00Z" - latency: 5.34654ms message: 'load-balancer-api-internal: tcp connection to a27e46730322d4ae68398230f9cb59be-2f3115ca7daefb02.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:57:00Z" - latency: 9.573658ms message: 'load-balancer-api-internal: resolved host name a27e46730322d4ae68398230f9cb59be-2f3115ca7daefb02.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T12:57:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T12:42:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-88-to-network-check-target-ip-10-0-138-24 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-88.ec2.internal uid: 7fe0adb3-00e2-476b-b823-df2c958eea53 resourceVersion: "22078" uid: a5440efb-cca7-49ca-a867-89224ea6befe spec: sourcePod: network-check-source-56499946bc-9fqqb targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-02T12:50:00Z" message: 'network-check-target-ip-10-0-138-24: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.19817ms message: 'network-check-target-ip-10-0-138-24: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:04:00Z" - latency: 2.348439ms message: 'network-check-target-ip-10-0-138-24: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:03:00Z" - latency: 2.714124ms message: 'network-check-target-ip-10-0-138-24: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:02:00Z" - latency: 2.302624ms message: 'network-check-target-ip-10-0-138-24: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:01:00Z" - latency: 2.321717ms message: 'network-check-target-ip-10-0-138-24: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:00:00Z" - latency: 2.220342ms message: 'network-check-target-ip-10-0-138-24: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:59:00Z" - latency: 2.232901ms message: 'network-check-target-ip-10-0-138-24: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:58:00Z" - latency: 2.367213ms message: 'network-check-target-ip-10-0-138-24: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:57:00Z" - latency: 2.230454ms message: 'network-check-target-ip-10-0-138-24: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:56:00Z" - latency: 2.258484ms message: 'network-check-target-ip-10-0-138-24: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:55:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T12:42:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-88-to-network-check-target-ip-10-0-142-167 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-88.ec2.internal uid: 7fe0adb3-00e2-476b-b823-df2c958eea53 resourceVersion: "22077" uid: 61ae00f3-e744-4e01-bea8-759fb5cf912f spec: sourcePod: network-check-source-56499946bc-9fqqb targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-02T12:50:00Z" message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.28211ms message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:04:00Z" - latency: 2.553912ms message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:03:00Z" - latency: 2.025339ms message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:02:00Z" - latency: 2.133679ms message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:01:00Z" - latency: 2.319867ms message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:00:00Z" - latency: 2.293421ms message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:59:00Z" - latency: 2.328459ms message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:58:00Z" - latency: 2.520293ms message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:57:00Z" - latency: 2.342547ms message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:56:00Z" - latency: 2.339111ms message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:55:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T12:42:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-88-to-network-check-target-ip-10-0-143-88 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-88.ec2.internal uid: 7fe0adb3-00e2-476b-b823-df2c958eea53 resourceVersion: "22076" uid: bb9dc4c1-6062-479f-9047-3fb599638de1 spec: sourcePod: network-check-source-56499946bc-9fqqb targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-02T12:50:00Z" message: 'network-check-target-ip-10-0-143-88: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 972.663µs message: 'network-check-target-ip-10-0-143-88: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:04:00Z" - latency: 998.502µs message: 'network-check-target-ip-10-0-143-88: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:03:00Z" - latency: 1.082634ms message: 'network-check-target-ip-10-0-143-88: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:02:00Z" - latency: 1.380811ms message: 'network-check-target-ip-10-0-143-88: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:01:00Z" - latency: 1.320627ms message: 'network-check-target-ip-10-0-143-88: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:00:00Z" - latency: 946.831µs message: 'network-check-target-ip-10-0-143-88: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:59:00Z" - latency: 1.406975ms message: 'network-check-target-ip-10-0-143-88: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:58:00Z" - latency: 1.105257ms message: 'network-check-target-ip-10-0-143-88: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:57:00Z" - latency: 1.036345ms message: 'network-check-target-ip-10-0-143-88: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:56:00Z" - latency: 1.390359ms message: 'network-check-target-ip-10-0-143-88: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:55:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T12:42:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-88-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-88.ec2.internal uid: 7fe0adb3-00e2-476b-b823-df2c958eea53 resourceVersion: "20457" uid: 42299e64-c6d4-4d08-a604-953e19ae7b14 spec: sourcePod: network-check-source-56499946bc-9fqqb targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-02T12:49:00Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 868.869µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:01:00Z" - latency: 2.110834ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T13:01:00Z" - latency: 1.161709ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:00:00Z" - latency: 2.043014ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T13:00:00Z" - latency: 1.414708ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:59:00Z" - latency: 1.740483ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T12:59:00Z" - latency: 844.485µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:58:00Z" - latency: 2.520601ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T12:58:00Z" - latency: 1.81124ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:57:00Z" - latency: 1.924749ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T12:57:00Z" kind: List metadata: resourceVersion: ""