apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T07:17:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-91-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-91.us-east-2.compute.internal uid: 2f5d72a5-91e2-4d05-8a72-12f2d88f997a resourceVersion: "41148" uid: c76440dc-0c5e-4476-8e5e-6625d3df663f spec: sourcePod: network-check-source-6f78d59f99-9slp7 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-04T07:24: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.040686ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:38:28Z" - latency: 1.229282ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:37:28Z" - latency: 918.349µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:36:28Z" - latency: 1.421625ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:35:28Z" - latency: 907.116µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:34:28Z" - latency: 1.146774ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:33:28Z" - latency: 1.1576ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:32:28Z" - latency: 801.482µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:31:28Z" - latency: 940.669µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:30:28Z" - latency: 932.723µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:29:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T07:17:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-91-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-91.us-east-2.compute.internal uid: 2f5d72a5-91e2-4d05-8a72-12f2d88f997a resourceVersion: "51336" uid: 51852499-3190-4278-a342-0e1f8944a705 spec: sourcePod: network-check-source-6f78d59f99-9slp7 targetEndpoint: a1bad623bfc634150a5504d541cd82b3-cce9b240aa801263.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-04T07:23:28Z" message: 'load-balancer-api-external: tcp connection to a1bad623bfc634150a5504d541cd82b3-cce9b240aa801263.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.304843ms message: 'load-balancer-api-external: tcp connection to a1bad623bfc634150a5504d541cd82b3-cce9b240aa801263.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:41:28Z" - latency: 27.441278ms message: 'load-balancer-api-external: resolved host name a1bad623bfc634150a5504d541cd82b3-cce9b240aa801263.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T07:41:28Z" - latency: 5.460459ms message: 'load-balancer-api-external: tcp connection to a1bad623bfc634150a5504d541cd82b3-cce9b240aa801263.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:40:28Z" - latency: 10.046864ms message: 'load-balancer-api-external: resolved host name a1bad623bfc634150a5504d541cd82b3-cce9b240aa801263.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T07:40:28Z" - latency: 5.188413ms message: 'load-balancer-api-external: tcp connection to a1bad623bfc634150a5504d541cd82b3-cce9b240aa801263.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:39:28Z" - latency: 7.131471ms message: 'load-balancer-api-external: resolved host name a1bad623bfc634150a5504d541cd82b3-cce9b240aa801263.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T07:39:28Z" - latency: 5.787891ms message: 'load-balancer-api-external: tcp connection to a1bad623bfc634150a5504d541cd82b3-cce9b240aa801263.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:38:28Z" - latency: 7.673684ms message: 'load-balancer-api-external: resolved host name a1bad623bfc634150a5504d541cd82b3-cce9b240aa801263.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T07:38:28Z" - latency: 5.702804ms message: 'load-balancer-api-external: tcp connection to a1bad623bfc634150a5504d541cd82b3-cce9b240aa801263.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:37:28Z" - latency: 8.535427ms message: 'load-balancer-api-external: resolved host name a1bad623bfc634150a5504d541cd82b3-cce9b240aa801263.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T07:37:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T07:17:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-91-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-91.us-east-2.compute.internal uid: 2f5d72a5-91e2-4d05-8a72-12f2d88f997a resourceVersion: "51335" uid: bc9b015c-f889-46d0-84e2-b9a23ceb92ae spec: sourcePod: network-check-source-6f78d59f99-9slp7 targetEndpoint: a1bad623bfc634150a5504d541cd82b3-cce9b240aa801263.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-04T07:23:28Z" message: 'load-balancer-api-internal: tcp connection to a1bad623bfc634150a5504d541cd82b3-cce9b240aa801263.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.997552ms message: 'load-balancer-api-internal: tcp connection to a1bad623bfc634150a5504d541cd82b3-cce9b240aa801263.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:41:28Z" - latency: 25.529923ms message: 'load-balancer-api-internal: resolved host name a1bad623bfc634150a5504d541cd82b3-cce9b240aa801263.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T07:41:28Z" - latency: 5.602986ms message: 'load-balancer-api-internal: tcp connection to a1bad623bfc634150a5504d541cd82b3-cce9b240aa801263.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:40:28Z" - latency: 9.858675ms message: 'load-balancer-api-internal: resolved host name a1bad623bfc634150a5504d541cd82b3-cce9b240aa801263.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T07:40:28Z" - latency: 6.450246ms message: 'load-balancer-api-internal: tcp connection to a1bad623bfc634150a5504d541cd82b3-cce9b240aa801263.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:39:28Z" - latency: 7.214579ms message: 'load-balancer-api-internal: resolved host name a1bad623bfc634150a5504d541cd82b3-cce9b240aa801263.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T07:39:28Z" - latency: 5.796966ms message: 'load-balancer-api-internal: tcp connection to a1bad623bfc634150a5504d541cd82b3-cce9b240aa801263.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:38:28Z" - latency: 7.620704ms message: 'load-balancer-api-internal: resolved host name a1bad623bfc634150a5504d541cd82b3-cce9b240aa801263.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T07:38:28Z" - latency: 5.662081ms message: 'load-balancer-api-internal: tcp connection to a1bad623bfc634150a5504d541cd82b3-cce9b240aa801263.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:37:28Z" - latency: 8.564712ms message: 'load-balancer-api-internal: resolved host name a1bad623bfc634150a5504d541cd82b3-cce9b240aa801263.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T07:37:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T07:17:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-91-to-network-check-target-ip-10-0-130-91 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-91.us-east-2.compute.internal uid: 2f5d72a5-91e2-4d05-8a72-12f2d88f997a resourceVersion: "41144" uid: f7eccfe6-633d-45ab-964e-c1bedcacf6ac spec: sourcePod: network-check-source-6f78d59f99-9slp7 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-04T07:24:28Z" message: 'network-check-target-ip-10-0-130-91: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.447716ms message: 'network-check-target-ip-10-0-130-91: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:38:28Z" - latency: 1.32001ms message: 'network-check-target-ip-10-0-130-91: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:37:28Z" - latency: 989.189µs message: 'network-check-target-ip-10-0-130-91: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:36:28Z" - latency: 2.07058ms message: 'network-check-target-ip-10-0-130-91: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:35:28Z" - latency: 858.106µs message: 'network-check-target-ip-10-0-130-91: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:34:28Z" - latency: 1.610036ms message: 'network-check-target-ip-10-0-130-91: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:33:28Z" - latency: 965.318µs message: 'network-check-target-ip-10-0-130-91: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:32:28Z" - latency: 834.778µs message: 'network-check-target-ip-10-0-130-91: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:31:28Z" - latency: 879.489µs message: 'network-check-target-ip-10-0-130-91: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:30:28Z" - latency: 1.041422ms message: 'network-check-target-ip-10-0-130-91: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:29:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T07:17:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-91-to-network-check-target-ip-10-0-131-6 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-91.us-east-2.compute.internal uid: 2f5d72a5-91e2-4d05-8a72-12f2d88f997a resourceVersion: "41146" uid: 10cf557d-39ef-4cd4-a877-1956dbe6c8f9 spec: sourcePod: network-check-source-6f78d59f99-9slp7 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-04T07:24:28Z" message: 'network-check-target-ip-10-0-131-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.324631ms message: 'network-check-target-ip-10-0-131-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:38:28Z" - latency: 2.152946ms message: 'network-check-target-ip-10-0-131-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:37:28Z" - latency: 2.207646ms message: 'network-check-target-ip-10-0-131-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:36:28Z" - latency: 2.691411ms message: 'network-check-target-ip-10-0-131-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:35:28Z" - latency: 2.0051ms message: 'network-check-target-ip-10-0-131-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:34:28Z" - latency: 2.773916ms message: 'network-check-target-ip-10-0-131-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:33:28Z" - latency: 2.339099ms message: 'network-check-target-ip-10-0-131-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:32:28Z" - latency: 2.336143ms message: 'network-check-target-ip-10-0-131-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:31:28Z" - latency: 2.497066ms message: 'network-check-target-ip-10-0-131-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:30:28Z" - latency: 2.249727ms message: 'network-check-target-ip-10-0-131-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:29:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T07:17:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-91-to-network-check-target-ip-10-0-142-197 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-91.us-east-2.compute.internal uid: 2f5d72a5-91e2-4d05-8a72-12f2d88f997a resourceVersion: "41145" uid: 08bbdb8d-0a6d-4a8f-a755-c0325a801cbe spec: sourcePod: network-check-source-6f78d59f99-9slp7 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-04T07:24:28Z" message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.307987ms message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:38:28Z" - latency: 2.750509ms message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:37:28Z" - latency: 2.540406ms message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:36:28Z" - latency: 2.820115ms message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:35:28Z" - latency: 2.164704ms message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:34:28Z" - latency: 3.227768ms message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:33:28Z" - latency: 2.370313ms message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:32:28Z" - latency: 2.368138ms message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:31:28Z" - latency: 1.973178ms message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:30:28Z" - latency: 2.305511ms message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:29:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T07:17:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-91-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-91.us-east-2.compute.internal uid: 2f5d72a5-91e2-4d05-8a72-12f2d88f997a resourceVersion: "51329" uid: b9eb1f2b-7894-4db4-84d6-05d66bb0679f spec: sourcePod: network-check-source-6f78d59f99-9slp7 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-04T07:23:28Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.888271ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:41:28Z" - latency: 10.491472ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T07:41:28Z" - latency: 905.634µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:40:28Z" - latency: 3.143191ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T07:40:28Z" - latency: 1.168844ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:39:28Z" - latency: 2.082141ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T07:39:28Z" - latency: 1.312882ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:38:28Z" - latency: 1.923147ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T07:38:28Z" - latency: 1.081045ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T07:37:28Z" - latency: 3.1047ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T07:37:28Z" kind: List metadata: resourceVersion: ""