apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T12:44:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-39-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-39.ec2.internal uid: 6197eb1a-4eb0-4cb4-8b97-06decd255c8f resourceVersion: "62637" uid: 80802c0b-8af0-4c3b-8fdb-0057b9657513 spec: sourcePod: network-check-source-7bc5b6bf85-kprgx targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-21T12:51:17Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 992.492µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:26:17Z" - latency: 1.258648ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:25:17Z" - latency: 1.41533ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:24:17Z" - latency: 997.317µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:23:17Z" - latency: 1.040083ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:22:17Z" - latency: 1.038527ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:21:17Z" - latency: 1.455639ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:20:17Z" - latency: 2.081161ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:19:17Z" - latency: 1.170532ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:18:17Z" - latency: 897.956µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:17:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T12:44:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-39-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-39.ec2.internal uid: 6197eb1a-4eb0-4cb4-8b97-06decd255c8f resourceVersion: "62638" uid: 90b360dc-57a4-4f8c-b786-fb4d49c04a1a spec: sourcePod: network-check-source-7bc5b6bf85-kprgx targetEndpoint: a979754ffbe0f401d954ce47bcc8f771-f9fe16ecbdc9a5d4.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-21T12:50:17Z" message: 'load-balancer-api-external: tcp connection to a979754ffbe0f401d954ce47bcc8f771-f9fe16ecbdc9a5d4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.84291ms message: 'load-balancer-api-external: tcp connection to a979754ffbe0f401d954ce47bcc8f771-f9fe16ecbdc9a5d4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:26:17Z" - latency: 8.064503ms message: 'load-balancer-api-external: resolved host name a979754ffbe0f401d954ce47bcc8f771-f9fe16ecbdc9a5d4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T13:26:17Z" - latency: 4.814703ms message: 'load-balancer-api-external: tcp connection to a979754ffbe0f401d954ce47bcc8f771-f9fe16ecbdc9a5d4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:25:17Z" - latency: 7.580181ms message: 'load-balancer-api-external: resolved host name a979754ffbe0f401d954ce47bcc8f771-f9fe16ecbdc9a5d4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T13:25:17Z" - latency: 4.453001ms message: 'load-balancer-api-external: tcp connection to a979754ffbe0f401d954ce47bcc8f771-f9fe16ecbdc9a5d4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:24:17Z" - latency: 7.628521ms message: 'load-balancer-api-external: resolved host name a979754ffbe0f401d954ce47bcc8f771-f9fe16ecbdc9a5d4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T13:24:17Z" - latency: 3.849762ms message: 'load-balancer-api-external: tcp connection to a979754ffbe0f401d954ce47bcc8f771-f9fe16ecbdc9a5d4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:23:17Z" - latency: 7.129609ms message: 'load-balancer-api-external: resolved host name a979754ffbe0f401d954ce47bcc8f771-f9fe16ecbdc9a5d4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T13:23:17Z" - latency: 3.14944ms message: 'load-balancer-api-external: tcp connection to a979754ffbe0f401d954ce47bcc8f771-f9fe16ecbdc9a5d4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:22:17Z" - latency: 7.596436ms message: 'load-balancer-api-external: resolved host name a979754ffbe0f401d954ce47bcc8f771-f9fe16ecbdc9a5d4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T13:22:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T12:44:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-39-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-39.ec2.internal uid: 6197eb1a-4eb0-4cb4-8b97-06decd255c8f resourceVersion: "62639" uid: 81687b38-68b1-4f97-8ea4-e65595416c7f spec: sourcePod: network-check-source-7bc5b6bf85-kprgx targetEndpoint: a979754ffbe0f401d954ce47bcc8f771-f9fe16ecbdc9a5d4.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-21T12:50:17Z" message: 'load-balancer-api-internal: tcp connection to a979754ffbe0f401d954ce47bcc8f771-f9fe16ecbdc9a5d4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.850874ms message: 'load-balancer-api-internal: tcp connection to a979754ffbe0f401d954ce47bcc8f771-f9fe16ecbdc9a5d4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:26:17Z" - latency: 7.93245ms message: 'load-balancer-api-internal: resolved host name a979754ffbe0f401d954ce47bcc8f771-f9fe16ecbdc9a5d4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T13:26:17Z" - latency: 4.810757ms message: 'load-balancer-api-internal: tcp connection to a979754ffbe0f401d954ce47bcc8f771-f9fe16ecbdc9a5d4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:25:17Z" - latency: 7.485975ms message: 'load-balancer-api-internal: resolved host name a979754ffbe0f401d954ce47bcc8f771-f9fe16ecbdc9a5d4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T13:25:17Z" - latency: 4.512723ms message: 'load-balancer-api-internal: tcp connection to a979754ffbe0f401d954ce47bcc8f771-f9fe16ecbdc9a5d4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:24:17Z" - latency: 7.561058ms message: 'load-balancer-api-internal: resolved host name a979754ffbe0f401d954ce47bcc8f771-f9fe16ecbdc9a5d4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T13:24:17Z" - latency: 4.151353ms message: 'load-balancer-api-internal: tcp connection to a979754ffbe0f401d954ce47bcc8f771-f9fe16ecbdc9a5d4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:23:17Z" - latency: 6.931119ms message: 'load-balancer-api-internal: resolved host name a979754ffbe0f401d954ce47bcc8f771-f9fe16ecbdc9a5d4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T13:23:17Z" - latency: 3.180076ms message: 'load-balancer-api-internal: tcp connection to a979754ffbe0f401d954ce47bcc8f771-f9fe16ecbdc9a5d4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:22:17Z" - latency: 7.517332ms message: 'load-balancer-api-internal: resolved host name a979754ffbe0f401d954ce47bcc8f771-f9fe16ecbdc9a5d4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T13:22:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T12:44:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-39-to-network-check-target-ip-10-0-130-157 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-39.ec2.internal uid: 6197eb1a-4eb0-4cb4-8b97-06decd255c8f resourceVersion: "62635" uid: 7d258435-a3dc-4255-87f4-04852305a789 spec: sourcePod: network-check-source-7bc5b6bf85-kprgx targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-21T12:51:17Z" message: 'network-check-target-ip-10-0-130-157: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.329343ms message: 'network-check-target-ip-10-0-130-157: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:26:17Z" - latency: 2.921548ms message: 'network-check-target-ip-10-0-130-157: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:25:17Z" - latency: 2.300247ms message: 'network-check-target-ip-10-0-130-157: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:24:17Z" - latency: 2.071059ms message: 'network-check-target-ip-10-0-130-157: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:23:17Z" - latency: 2.233178ms message: 'network-check-target-ip-10-0-130-157: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:22:17Z" - latency: 2.674296ms message: 'network-check-target-ip-10-0-130-157: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:21:17Z" - latency: 2.096743ms message: 'network-check-target-ip-10-0-130-157: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:20:17Z" - latency: 2.453955ms message: 'network-check-target-ip-10-0-130-157: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:19:17Z" - latency: 2.406878ms message: 'network-check-target-ip-10-0-130-157: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:18:17Z" - latency: 1.718556ms message: 'network-check-target-ip-10-0-130-157: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:17:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T12:44:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-39-to-network-check-target-ip-10-0-130-2 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-39.ec2.internal uid: 6197eb1a-4eb0-4cb4-8b97-06decd255c8f resourceVersion: "62634" uid: 862c3d20-8db3-4b56-897d-28e86aa32ef5 spec: sourcePod: network-check-source-7bc5b6bf85-kprgx targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-21T12:51:17Z" message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.319564ms message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:26:17Z" - latency: 2.407291ms message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:25:17Z" - latency: 2.688833ms message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:24:17Z" - latency: 2.327391ms message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:23:17Z" - latency: 2.627458ms message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:22:17Z" - latency: 2.344623ms message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:21:17Z" - latency: 2.504466ms message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:20:17Z" - latency: 2.57254ms message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:19:17Z" - latency: 2.530894ms message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:18:17Z" - latency: 2.593097ms message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:17:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T12:44:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-39-to-network-check-target-ip-10-0-133-39 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-39.ec2.internal uid: 6197eb1a-4eb0-4cb4-8b97-06decd255c8f resourceVersion: "62633" uid: 86bc9233-4b8c-46f9-bf0f-98af245e8981 spec: sourcePod: network-check-source-7bc5b6bf85-kprgx targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-21T12:51:17Z" message: 'network-check-target-ip-10-0-133-39: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 965.582µs message: 'network-check-target-ip-10-0-133-39: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:26:17Z" - latency: 1.143041ms message: 'network-check-target-ip-10-0-133-39: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:25:17Z" - latency: 1.096917ms message: 'network-check-target-ip-10-0-133-39: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:24:17Z" - latency: 1.018971ms message: 'network-check-target-ip-10-0-133-39: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:23:17Z" - latency: 1.02624ms message: 'network-check-target-ip-10-0-133-39: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:22:17Z" - latency: 990.58µs message: 'network-check-target-ip-10-0-133-39: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:21:17Z" - latency: 888.728µs message: 'network-check-target-ip-10-0-133-39: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:20:17Z" - latency: 2.041198ms message: 'network-check-target-ip-10-0-133-39: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:19:17Z" - latency: 1.504622ms message: 'network-check-target-ip-10-0-133-39: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:18:17Z" - latency: 1.080697ms message: 'network-check-target-ip-10-0-133-39: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:17:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T12:44:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-39-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-39.ec2.internal uid: 6197eb1a-4eb0-4cb4-8b97-06decd255c8f resourceVersion: "62636" uid: 36c42f5a-82ab-49ad-a3ac-cf5bb66ebf5c spec: sourcePod: network-check-source-7bc5b6bf85-kprgx targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-21T12:50:17Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.095709ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:26:17Z" - latency: 1.949531ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T13:26:17Z" - latency: 1.215822ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:25:17Z" - latency: 1.897148ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T13:25:17Z" - latency: 935.571µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:24:17Z" - latency: 1.892565ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T13:24:17Z" - latency: 887.135µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:23:17Z" - latency: 1.799261ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T13:23:17Z" - latency: 1.412085ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T13:22:17Z" - latency: 1.814876ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T13:22:17Z" kind: List metadata: resourceVersion: ""