apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T21:45:27Z" 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: c8154f15-0baa-4f10-bdf3-3b67ca687cde resourceVersion: "45775" uid: c5d9292b-2c5c-4f1c-addd-bec29be2047c spec: sourcePod: network-check-source-56d84b9f44-96vsd targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-02T21:52:28Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 964.67µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:13:28Z" - latency: 875.512µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:12:28Z" - latency: 892.265µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:11:28Z" - latency: 1.205986ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:10:28Z" - latency: 1.370694ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:09:28Z" - latency: 1.038438ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:08:28Z" - latency: 873.621µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:07:28Z" - latency: 1.236567ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:06:28Z" - latency: 1.014188ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:05:28Z" - latency: 985.386µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:04:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T21:45:27Z" 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: c8154f15-0baa-4f10-bdf3-3b67ca687cde resourceVersion: "48233" uid: 110f1e30-bd42-4a08-8714-e8b830224b36 spec: sourcePod: network-check-source-56d84b9f44-96vsd targetEndpoint: a2e0495e3452f471297eead49b3c4137-a0db639dfc90dfa8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-02T21:51:28Z" message: 'load-balancer-api-external: tcp connection to a2e0495e3452f471297eead49b3c4137-a0db639dfc90dfa8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.931145ms message: 'load-balancer-api-external: tcp connection to a2e0495e3452f471297eead49b3c4137-a0db639dfc90dfa8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:15:28Z" - latency: 6.391092ms message: 'load-balancer-api-external: resolved host name a2e0495e3452f471297eead49b3c4137-a0db639dfc90dfa8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T22:15:28Z" - latency: 4.649938ms message: 'load-balancer-api-external: tcp connection to a2e0495e3452f471297eead49b3c4137-a0db639dfc90dfa8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:14:28Z" - latency: 6.84105ms message: 'load-balancer-api-external: resolved host name a2e0495e3452f471297eead49b3c4137-a0db639dfc90dfa8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T22:14:28Z" - latency: 3.876317ms message: 'load-balancer-api-external: tcp connection to a2e0495e3452f471297eead49b3c4137-a0db639dfc90dfa8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:13:28Z" - latency: 6.105289ms message: 'load-balancer-api-external: resolved host name a2e0495e3452f471297eead49b3c4137-a0db639dfc90dfa8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T22:13:28Z" - latency: 5.20227ms message: 'load-balancer-api-external: tcp connection to a2e0495e3452f471297eead49b3c4137-a0db639dfc90dfa8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:12:28Z" - latency: 6.506005ms message: 'load-balancer-api-external: resolved host name a2e0495e3452f471297eead49b3c4137-a0db639dfc90dfa8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T22:12:28Z" - latency: 4.197822ms message: 'load-balancer-api-external: tcp connection to a2e0495e3452f471297eead49b3c4137-a0db639dfc90dfa8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:11:28Z" - latency: 6.056239ms message: 'load-balancer-api-external: resolved host name a2e0495e3452f471297eead49b3c4137-a0db639dfc90dfa8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T22:11:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T21:45:27Z" 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: c8154f15-0baa-4f10-bdf3-3b67ca687cde resourceVersion: "48234" uid: 4e2f83c9-6221-499b-80bf-dbbd69a17354 spec: sourcePod: network-check-source-56d84b9f44-96vsd targetEndpoint: a2e0495e3452f471297eead49b3c4137-a0db639dfc90dfa8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-02T21:51:28Z" message: 'load-balancer-api-internal: tcp connection to a2e0495e3452f471297eead49b3c4137-a0db639dfc90dfa8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.7711ms message: 'load-balancer-api-internal: tcp connection to a2e0495e3452f471297eead49b3c4137-a0db639dfc90dfa8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:15:28Z" - latency: 6.426064ms message: 'load-balancer-api-internal: resolved host name a2e0495e3452f471297eead49b3c4137-a0db639dfc90dfa8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T22:15:28Z" - latency: 4.707567ms message: 'load-balancer-api-internal: tcp connection to a2e0495e3452f471297eead49b3c4137-a0db639dfc90dfa8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:14:28Z" - latency: 6.851953ms message: 'load-balancer-api-internal: resolved host name a2e0495e3452f471297eead49b3c4137-a0db639dfc90dfa8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T22:14:28Z" - latency: 4.504672ms message: 'load-balancer-api-internal: tcp connection to a2e0495e3452f471297eead49b3c4137-a0db639dfc90dfa8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:13:28Z" - latency: 6.052182ms message: 'load-balancer-api-internal: resolved host name a2e0495e3452f471297eead49b3c4137-a0db639dfc90dfa8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T22:13:28Z" - latency: 5.049059ms message: 'load-balancer-api-internal: tcp connection to a2e0495e3452f471297eead49b3c4137-a0db639dfc90dfa8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:12:28Z" - latency: 6.839141ms message: 'load-balancer-api-internal: resolved host name a2e0495e3452f471297eead49b3c4137-a0db639dfc90dfa8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T22:12:28Z" - latency: 4.10224ms message: 'load-balancer-api-internal: tcp connection to a2e0495e3452f471297eead49b3c4137-a0db639dfc90dfa8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:11:28Z" - latency: 6.10402ms message: 'load-balancer-api-internal: resolved host name a2e0495e3452f471297eead49b3c4137-a0db639dfc90dfa8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T22:11:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T21:45:27Z" 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-133-201 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-67.ec2.internal uid: c8154f15-0baa-4f10-bdf3-3b67ca687cde resourceVersion: "45772" uid: de5fbc07-b865-493a-9efd-27315ef24b08 spec: sourcePod: network-check-source-56d84b9f44-96vsd targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-02T21:52:28Z" message: 'network-check-target-ip-10-0-133-201: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.140022ms message: 'network-check-target-ip-10-0-133-201: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:13:28Z" - latency: 2.507221ms message: 'network-check-target-ip-10-0-133-201: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:12:28Z" - latency: 2.107468ms message: 'network-check-target-ip-10-0-133-201: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:11:28Z" - latency: 2.272188ms message: 'network-check-target-ip-10-0-133-201: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:10:28Z" - latency: 2.061954ms message: 'network-check-target-ip-10-0-133-201: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:09:28Z" - latency: 2.02815ms message: 'network-check-target-ip-10-0-133-201: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:08:28Z" - latency: 1.926295ms message: 'network-check-target-ip-10-0-133-201: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:07:28Z" - latency: 1.809005ms message: 'network-check-target-ip-10-0-133-201: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:06:28Z" - latency: 2.113482ms message: 'network-check-target-ip-10-0-133-201: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:05:28Z" - latency: 2.180101ms message: 'network-check-target-ip-10-0-133-201: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:04:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T21:45:27Z" 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: c8154f15-0baa-4f10-bdf3-3b67ca687cde resourceVersion: "45771" uid: d594e688-ea4d-4218-b14c-a81ac0e47eed spec: sourcePod: network-check-source-56d84b9f44-96vsd targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-02T21:52:28Z" message: 'network-check-target-ip-10-0-139-67: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 797.496µs message: 'network-check-target-ip-10-0-139-67: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:13:28Z" - latency: 844.932µs message: 'network-check-target-ip-10-0-139-67: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:12:28Z" - latency: 836.131µs message: 'network-check-target-ip-10-0-139-67: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:11:28Z" - latency: 1.470073ms message: 'network-check-target-ip-10-0-139-67: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:10:28Z" - latency: 1.660948ms message: 'network-check-target-ip-10-0-139-67: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:09:28Z" - latency: 894.501µs message: 'network-check-target-ip-10-0-139-67: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:08:28Z" - latency: 789.087µs message: 'network-check-target-ip-10-0-139-67: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:07:28Z" - latency: 1.519766ms message: 'network-check-target-ip-10-0-139-67: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:06:28Z" - latency: 1.172318ms message: 'network-check-target-ip-10-0-139-67: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:05:28Z" - latency: 1.354038ms message: 'network-check-target-ip-10-0-139-67: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:04:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T21:45:27Z" 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-141-177 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-67.ec2.internal uid: c8154f15-0baa-4f10-bdf3-3b67ca687cde resourceVersion: "45773" uid: 8da72da9-29d7-499e-991a-2c62d57e3ce2 spec: sourcePod: network-check-source-56d84b9f44-96vsd targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-02T21:52:28Z" message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.286464ms message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:13:28Z" - latency: 2.453744ms message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:12:28Z" - latency: 2.130828ms message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:11:28Z" - latency: 2.719925ms message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:10:28Z" - latency: 2.313781ms message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:09:28Z" - latency: 2.275173ms message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:08:28Z" - latency: 2.502453ms message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:07:28Z" - latency: 2.217045ms message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:06:28Z" - latency: 2.408764ms message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:05:28Z" - latency: 2.268075ms message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:04:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T21:45:27Z" 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: c8154f15-0baa-4f10-bdf3-3b67ca687cde resourceVersion: "48232" uid: b6c03eca-f30c-412e-a259-6f3d58df775f spec: sourcePod: network-check-source-56d84b9f44-96vsd targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-02T21:51:28Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 855.249µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:15:28Z" - latency: 1.711044ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T22:15:28Z" - latency: 1.140338ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:14:28Z" - latency: 1.809175ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T22:14:28Z" - latency: 818.395µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:13:28Z" - latency: 1.758083ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T22:13:28Z" - latency: 1.127883ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:12:28Z" - latency: 1.54295ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T22:12:28Z" - latency: 735.456µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T22:11:28Z" - latency: 1.518736ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T22:11:28Z" kind: List metadata: resourceVersion: ""