apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T16:47:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-45-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-45.ec2.internal uid: 1f483a5e-5d4e-4090-a891-b14b5fcd9d31 resourceVersion: "30789" uid: 8fcb0968-3f6f-4c88-950d-7740443b9025 spec: sourcePod: network-check-source-56d84b9f44-w82gl targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-02T16:54:28Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.054682ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T17:01:28Z" - latency: 1.162657ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T17:00:28Z" - latency: 926.333µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:59:28Z" - latency: 916.106µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:58:28Z" - latency: 915.329µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:57:28Z" - latency: 1.040226ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:56:28Z" - latency: 1.135151ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:55:28Z" - latency: 1.959557ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:54:28Z" - latency: 932.098µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:53:28Z" - latency: 1.189411ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:52:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T16:47:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-45-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-45.ec2.internal uid: 1f483a5e-5d4e-4090-a891-b14b5fcd9d31 resourceVersion: "29216" uid: 7b25d9b4-5165-4021-95ec-d6da6b8bde56 spec: sourcePod: network-check-source-56d84b9f44-w82gl targetEndpoint: a9ddc4a367999432faae98e6239782c6-d4f5108e69c4c160.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-02T16:53:28Z" message: 'load-balancer-api-external: tcp connection to a9ddc4a367999432faae98e6239782c6-d4f5108e69c4c160.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 9.227452ms message: 'load-balancer-api-external: tcp connection to a9ddc4a367999432faae98e6239782c6-d4f5108e69c4c160.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:59:28Z" - latency: 8.01668ms message: 'load-balancer-api-external: resolved host name a9ddc4a367999432faae98e6239782c6-d4f5108e69c4c160.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T16:59:28Z" - latency: 4.600858ms message: 'load-balancer-api-external: tcp connection to a9ddc4a367999432faae98e6239782c6-d4f5108e69c4c160.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:58:28Z" - latency: 7.895476ms message: 'load-balancer-api-external: resolved host name a9ddc4a367999432faae98e6239782c6-d4f5108e69c4c160.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T16:58:28Z" - latency: 4.121012ms message: 'load-balancer-api-external: tcp connection to a9ddc4a367999432faae98e6239782c6-d4f5108e69c4c160.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:57:28Z" - latency: 8.109186ms message: 'load-balancer-api-external: resolved host name a9ddc4a367999432faae98e6239782c6-d4f5108e69c4c160.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T16:57:28Z" - latency: 4.320612ms message: 'load-balancer-api-external: tcp connection to a9ddc4a367999432faae98e6239782c6-d4f5108e69c4c160.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:56:28Z" - latency: 9.319077ms message: 'load-balancer-api-external: resolved host name a9ddc4a367999432faae98e6239782c6-d4f5108e69c4c160.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T16:56:28Z" - latency: 5.567745ms message: 'load-balancer-api-external: tcp connection to a9ddc4a367999432faae98e6239782c6-d4f5108e69c4c160.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:55:28Z" - latency: 9.389923ms message: 'load-balancer-api-external: resolved host name a9ddc4a367999432faae98e6239782c6-d4f5108e69c4c160.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T16:55:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T16:47:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-45-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-45.ec2.internal uid: 1f483a5e-5d4e-4090-a891-b14b5fcd9d31 resourceVersion: "29215" uid: 7ca2207e-acf7-4add-800c-c0bc5923d76a spec: sourcePod: network-check-source-56d84b9f44-w82gl targetEndpoint: a9ddc4a367999432faae98e6239782c6-d4f5108e69c4c160.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-02T16:53:28Z" message: 'load-balancer-api-internal: tcp connection to a9ddc4a367999432faae98e6239782c6-d4f5108e69c4c160.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.815653ms message: 'load-balancer-api-internal: tcp connection to a9ddc4a367999432faae98e6239782c6-d4f5108e69c4c160.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:59:28Z" - latency: 8.05957ms message: 'load-balancer-api-internal: resolved host name a9ddc4a367999432faae98e6239782c6-d4f5108e69c4c160.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T16:59:28Z" - latency: 5.039324ms message: 'load-balancer-api-internal: tcp connection to a9ddc4a367999432faae98e6239782c6-d4f5108e69c4c160.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:58:28Z" - latency: 7.84696ms message: 'load-balancer-api-internal: resolved host name a9ddc4a367999432faae98e6239782c6-d4f5108e69c4c160.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T16:58:28Z" - latency: 8.207373ms message: 'load-balancer-api-internal: tcp connection to a9ddc4a367999432faae98e6239782c6-d4f5108e69c4c160.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:57:28Z" - latency: 8.077281ms message: 'load-balancer-api-internal: resolved host name a9ddc4a367999432faae98e6239782c6-d4f5108e69c4c160.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T16:57:28Z" - latency: 3.442341ms message: 'load-balancer-api-internal: tcp connection to a9ddc4a367999432faae98e6239782c6-d4f5108e69c4c160.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:56:28Z" - latency: 9.250344ms message: 'load-balancer-api-internal: resolved host name a9ddc4a367999432faae98e6239782c6-d4f5108e69c4c160.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T16:56:28Z" - latency: 5.550012ms message: 'load-balancer-api-internal: tcp connection to a9ddc4a367999432faae98e6239782c6-d4f5108e69c4c160.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:55:28Z" - latency: 9.435198ms message: 'load-balancer-api-internal: resolved host name a9ddc4a367999432faae98e6239782c6-d4f5108e69c4c160.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T16:55:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T16:47:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-45-to-network-check-target-ip-10-0-130-253 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-45.ec2.internal uid: 1f483a5e-5d4e-4090-a891-b14b5fcd9d31 resourceVersion: "30787" uid: b40d97a2-8086-4f2d-82bb-361c45d6026c spec: sourcePod: network-check-source-56d84b9f44-w82gl targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-02T16:54:28Z" message: 'network-check-target-ip-10-0-130-253: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.232557ms message: 'network-check-target-ip-10-0-130-253: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T17:01:28Z" - latency: 2.377008ms message: 'network-check-target-ip-10-0-130-253: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T17:00:28Z" - latency: 2.488057ms message: 'network-check-target-ip-10-0-130-253: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:59:28Z" - latency: 2.566798ms message: 'network-check-target-ip-10-0-130-253: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:58:28Z" - latency: 1.89214ms message: 'network-check-target-ip-10-0-130-253: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:57:28Z" - latency: 2.383549ms message: 'network-check-target-ip-10-0-130-253: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:56:28Z" - latency: 1.914476ms message: 'network-check-target-ip-10-0-130-253: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:55:28Z" - latency: 1.957918ms message: 'network-check-target-ip-10-0-130-253: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:54:28Z" - latency: 2.629771ms message: 'network-check-target-ip-10-0-130-253: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:53:28Z" - latency: 2.679744ms message: 'network-check-target-ip-10-0-130-253: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:52:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T16:47:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-45-to-network-check-target-ip-10-0-131-40 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-45.ec2.internal uid: 1f483a5e-5d4e-4090-a891-b14b5fcd9d31 resourceVersion: "30788" uid: 48dd9fdd-1ade-4c7e-9aac-b5f20bfb0fa3 spec: sourcePod: network-check-source-56d84b9f44-w82gl targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-02T16:54:28Z" message: 'network-check-target-ip-10-0-131-40: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.334327ms message: 'network-check-target-ip-10-0-131-40: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T17:01:28Z" - latency: 2.222393ms message: 'network-check-target-ip-10-0-131-40: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T17:00:28Z" - latency: 2.117199ms message: 'network-check-target-ip-10-0-131-40: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:59:28Z" - latency: 2.316505ms message: 'network-check-target-ip-10-0-131-40: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:58:28Z" - latency: 2.495802ms message: 'network-check-target-ip-10-0-131-40: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:57:28Z" - latency: 2.742179ms message: 'network-check-target-ip-10-0-131-40: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:56:28Z" - latency: 2.687031ms message: 'network-check-target-ip-10-0-131-40: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:55:28Z" - latency: 2.491998ms message: 'network-check-target-ip-10-0-131-40: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:54:28Z" - latency: 2.447215ms message: 'network-check-target-ip-10-0-131-40: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:53:28Z" - latency: 2.783365ms message: 'network-check-target-ip-10-0-131-40: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:52:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T16:47:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-45-to-network-check-target-ip-10-0-132-45 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-45.ec2.internal uid: 1f483a5e-5d4e-4090-a891-b14b5fcd9d31 resourceVersion: "30786" uid: 242062db-66df-4f8c-aa66-3b551bcd6f72 spec: sourcePod: network-check-source-56d84b9f44-w82gl targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-02T16:54:28Z" message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 881.492µs message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T17:01:28Z" - latency: 1.19384ms message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T17:00:28Z" - latency: 899.35µs message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:59:28Z" - latency: 780.098µs message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:58:28Z" - latency: 955.837µs message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:57:28Z" - latency: 1.062286ms message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:56:28Z" - latency: 1.371678ms message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:55:28Z" - latency: 946.041µs message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:54:28Z" - latency: 819.808µs message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:53:28Z" - latency: 1.165071ms message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:52:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T16:47:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-45-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-45.ec2.internal uid: 1f483a5e-5d4e-4090-a891-b14b5fcd9d31 resourceVersion: "29213" uid: e949a045-76fc-4dc9-98a1-7257305be3ed spec: sourcePod: network-check-source-56d84b9f44-w82gl targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-02T16:53:28Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 775.014µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:59:28Z" - latency: 1.791977ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T16:59:28Z" - latency: 1.058284ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:58:28Z" - latency: 1.547874ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T16:58:28Z" - latency: 728.274µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:57:28Z" - latency: 1.703085ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T16:57:28Z" - latency: 918.624µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:56:28Z" - latency: 1.987596ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T16:56:28Z" - latency: 1.184606ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:55:28Z" - latency: 2.033772ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T16:55:28Z" kind: List metadata: resourceVersion: ""