apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:24:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-135-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-135.us-west-1.compute.internal uid: 0a79f0f2-716b-419f-96ff-6310be5f8751 resourceVersion: "115335" uid: ed0c062a-fd18-4939-b656-00b6043d7728 spec: sourcePod: network-check-source-6f78d59f99-948s6 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T21:31:27Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.10186ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:41:27Z" - latency: 1.029838ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:40:27Z" - latency: 1.052028ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:39:27Z" - latency: 1.180372ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:38:27Z" - latency: 1.22046ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:37:27Z" - latency: 1.095909ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:36:27Z" - latency: 1.36457ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:35:27Z" - latency: 965.225µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:34:27Z" - latency: 1.219263ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:33:27Z" - latency: 3.388652ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:32:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:24:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-135-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-135.us-west-1.compute.internal uid: 0a79f0f2-716b-419f-96ff-6310be5f8751 resourceVersion: "115851" uid: 0e7d17c4-d267-43b2-abd8-1ae4dfee54c0 spec: sourcePod: network-check-source-6f78d59f99-948s6 targetEndpoint: af1d03f21ae4249649589735f9d6a3af-3cfe10bb520c60ba.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T21:30:31Z" message: 'load-balancer-api-external: tcp connection to af1d03f21ae4249649589735f9d6a3af-3cfe10bb520c60ba.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 54.002523ms message: 'load-balancer-api-external: tcp connection to af1d03f21ae4249649589735f9d6a3af-3cfe10bb520c60ba.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:42:27Z" - latency: 6.178839ms message: 'load-balancer-api-external: resolved host name af1d03f21ae4249649589735f9d6a3af-3cfe10bb520c60ba.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:42:27Z" - latency: 53.829947ms message: 'load-balancer-api-external: tcp connection to af1d03f21ae4249649589735f9d6a3af-3cfe10bb520c60ba.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:41:27Z" - latency: 9.331473ms message: 'load-balancer-api-external: resolved host name af1d03f21ae4249649589735f9d6a3af-3cfe10bb520c60ba.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:41:27Z" - latency: 54.193448ms message: 'load-balancer-api-external: tcp connection to af1d03f21ae4249649589735f9d6a3af-3cfe10bb520c60ba.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:40:27Z" - latency: 5.478181ms message: 'load-balancer-api-external: resolved host name af1d03f21ae4249649589735f9d6a3af-3cfe10bb520c60ba.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:40:27Z" - latency: 54.166365ms message: 'load-balancer-api-external: tcp connection to af1d03f21ae4249649589735f9d6a3af-3cfe10bb520c60ba.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:39:27Z" - latency: 5.707073ms message: 'load-balancer-api-external: resolved host name af1d03f21ae4249649589735f9d6a3af-3cfe10bb520c60ba.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:39:27Z" - latency: 53.482972ms message: 'load-balancer-api-external: tcp connection to af1d03f21ae4249649589735f9d6a3af-3cfe10bb520c60ba.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:38:27Z" - latency: 5.954886ms message: 'load-balancer-api-external: resolved host name af1d03f21ae4249649589735f9d6a3af-3cfe10bb520c60ba.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:38:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:24:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-135-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-135.us-west-1.compute.internal uid: 0a79f0f2-716b-419f-96ff-6310be5f8751 resourceVersion: "115852" uid: dd2c6e16-24d7-41d6-8a02-8a94249170ad spec: sourcePod: network-check-source-6f78d59f99-948s6 targetEndpoint: af1d03f21ae4249649589735f9d6a3af-3cfe10bb520c60ba.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T21:30:27Z" message: 'load-balancer-api-internal: tcp connection to af1d03f21ae4249649589735f9d6a3af-3cfe10bb520c60ba.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 56.406194ms message: 'load-balancer-api-internal: tcp connection to af1d03f21ae4249649589735f9d6a3af-3cfe10bb520c60ba.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:42:27Z" - latency: 6.118408ms message: 'load-balancer-api-internal: resolved host name af1d03f21ae4249649589735f9d6a3af-3cfe10bb520c60ba.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:42:27Z" - latency: 53.88149ms message: 'load-balancer-api-internal: tcp connection to af1d03f21ae4249649589735f9d6a3af-3cfe10bb520c60ba.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:41:27Z" - latency: 9.29492ms message: 'load-balancer-api-internal: resolved host name af1d03f21ae4249649589735f9d6a3af-3cfe10bb520c60ba.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:41:27Z" - latency: 59.224066ms message: 'load-balancer-api-internal: tcp connection to af1d03f21ae4249649589735f9d6a3af-3cfe10bb520c60ba.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:40:27Z" - latency: 5.428913ms message: 'load-balancer-api-internal: resolved host name af1d03f21ae4249649589735f9d6a3af-3cfe10bb520c60ba.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:40:27Z" - latency: 54.199673ms message: 'load-balancer-api-internal: tcp connection to af1d03f21ae4249649589735f9d6a3af-3cfe10bb520c60ba.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:39:27Z" - latency: 5.67046ms message: 'load-balancer-api-internal: resolved host name af1d03f21ae4249649589735f9d6a3af-3cfe10bb520c60ba.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:39:27Z" - latency: 54.024457ms message: 'load-balancer-api-internal: tcp connection to af1d03f21ae4249649589735f9d6a3af-3cfe10bb520c60ba.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:38:27Z" - latency: 5.98975ms message: 'load-balancer-api-internal: resolved host name af1d03f21ae4249649589735f9d6a3af-3cfe10bb520c60ba.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:38:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:24:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-135-to-network-check-target-ip-10-0-134-53 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-135.us-west-1.compute.internal uid: 0a79f0f2-716b-419f-96ff-6310be5f8751 resourceVersion: "115341" uid: 9f582687-d209-42a9-b4a0-36cea2455971 spec: sourcePod: network-check-source-6f78d59f99-948s6 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T21:31:28Z" message: 'network-check-target-ip-10-0-134-53: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.856731ms message: 'network-check-target-ip-10-0-134-53: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:41:28Z" - latency: 622.707µs message: 'network-check-target-ip-10-0-134-53: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:40:28Z" - latency: 2.173203ms message: 'network-check-target-ip-10-0-134-53: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:39:28Z" - latency: 1.137686ms message: 'network-check-target-ip-10-0-134-53: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:38:28Z" - latency: 2.482582ms message: 'network-check-target-ip-10-0-134-53: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:37:28Z" - latency: 2.286893ms message: 'network-check-target-ip-10-0-134-53: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:36:28Z" - latency: 728.778µs message: 'network-check-target-ip-10-0-134-53: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:35:28Z" - latency: 1.574709ms message: 'network-check-target-ip-10-0-134-53: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:34:28Z" - latency: 2.399826ms message: 'network-check-target-ip-10-0-134-53: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:33:28Z" - latency: 2.395331ms message: 'network-check-target-ip-10-0-134-53: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:32:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:24:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-135-to-network-check-target-ip-10-0-136-135 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-135.us-west-1.compute.internal uid: 0a79f0f2-716b-419f-96ff-6310be5f8751 resourceVersion: "115339" uid: 80516b5f-587a-4b43-820d-04640ec1cf3e spec: sourcePod: network-check-source-6f78d59f99-948s6 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T21:31:28Z" message: 'network-check-target-ip-10-0-136-135: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.063452ms message: 'network-check-target-ip-10-0-136-135: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:41:28Z" - latency: 997.547µs message: 'network-check-target-ip-10-0-136-135: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:40:28Z" - latency: 540.131µs message: 'network-check-target-ip-10-0-136-135: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:39:28Z" - latency: 841.893µs message: 'network-check-target-ip-10-0-136-135: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:38:28Z" - latency: 1.16114ms message: 'network-check-target-ip-10-0-136-135: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:37:28Z" - latency: 857.572µs message: 'network-check-target-ip-10-0-136-135: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:36:28Z" - latency: 1.206607ms message: 'network-check-target-ip-10-0-136-135: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:35:28Z" - latency: 912.463µs message: 'network-check-target-ip-10-0-136-135: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:34:28Z" - latency: 686.546µs message: 'network-check-target-ip-10-0-136-135: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:33:28Z" - latency: 597.353µs message: 'network-check-target-ip-10-0-136-135: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:32:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:24:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-135-to-network-check-target-ip-10-0-143-61 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-135.us-west-1.compute.internal uid: 0a79f0f2-716b-419f-96ff-6310be5f8751 resourceVersion: "115334" uid: 63e46b51-3cb4-43a8-b85a-c723e53788a3 spec: sourcePod: network-check-source-6f78d59f99-948s6 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T21:31:27Z" message: 'network-check-target-ip-10-0-143-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.887989ms message: 'network-check-target-ip-10-0-143-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:41:27Z" - latency: 1.876742ms message: 'network-check-target-ip-10-0-143-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:40:27Z" - latency: 1.649377ms message: 'network-check-target-ip-10-0-143-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:39:27Z" - latency: 2.036768ms message: 'network-check-target-ip-10-0-143-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:38:27Z" - latency: 2.025659ms message: 'network-check-target-ip-10-0-143-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:37:27Z" - latency: 2.068503ms message: 'network-check-target-ip-10-0-143-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:36:27Z" - latency: 2.341516ms message: 'network-check-target-ip-10-0-143-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:35:27Z" - latency: 2.10176ms message: 'network-check-target-ip-10-0-143-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:34:27Z" - latency: 2.120076ms message: 'network-check-target-ip-10-0-143-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:33:27Z" - latency: 3.134618ms message: 'network-check-target-ip-10-0-143-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:32:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:24:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-135-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-135.us-west-1.compute.internal uid: 0a79f0f2-716b-419f-96ff-6310be5f8751 resourceVersion: "115850" uid: 72a95f4f-a2c8-4c5d-9415-d3a36a88ed6d spec: sourcePod: network-check-source-6f78d59f99-948s6 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T21:30:27Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 956.164µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:42:27Z" - latency: 592.096µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:42:27Z" - latency: 795.384µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:41:27Z" - latency: 575.705µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:41:27Z" - latency: 2.16704ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:40:27Z" - latency: 515.384µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:40:27Z" - latency: 1.012079ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:39:27Z" - latency: 569.187µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:39:27Z" - latency: 2.231193ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:38:27Z" - latency: 519.696µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:38:27Z" kind: List metadata: resourceVersion: ""