apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T22:00:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-57-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-57.us-east-2.compute.internal uid: 0d5195bc-2fbc-40c0-8c10-c2e3c200a88f resourceVersion: "120838" uid: 94c74376-a59e-4a97-9fad-3943688ffa7b spec: sourcePod: network-check-source-6f78d59f99-cw95x targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-02T22:07:45Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 917.141µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:42:45Z" - latency: 1.070071ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:41:45Z" - latency: 1.075178ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:40:45Z" - latency: 1.955398ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:39:45Z" - latency: 984.231µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:38:45Z" - latency: 2.074016ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:37:45Z" - latency: 1.345136ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:36:45Z" - latency: 5.566213ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:35:45Z" - latency: 1.419383ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:34:45Z" - latency: 986.879µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:33:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T22:00:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-57-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-57.us-east-2.compute.internal uid: 0d5195bc-2fbc-40c0-8c10-c2e3c200a88f resourceVersion: "120839" uid: 3f24a7a2-95ba-43b0-9ce7-d5070ac153c5 spec: sourcePod: network-check-source-6f78d59f99-cw95x targetEndpoint: a23a7fce0ce7143d38b69e38506023ff-71cc8589742a996d.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T22:06:45Z" message: 'load-balancer-api-external: tcp connection to a23a7fce0ce7143d38b69e38506023ff-71cc8589742a996d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.103568ms message: 'load-balancer-api-external: tcp connection to a23a7fce0ce7143d38b69e38506023ff-71cc8589742a996d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:42:45Z" - latency: 6.805123ms message: 'load-balancer-api-external: resolved host name a23a7fce0ce7143d38b69e38506023ff-71cc8589742a996d.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:42:45Z" - latency: 5.123512ms message: 'load-balancer-api-external: tcp connection to a23a7fce0ce7143d38b69e38506023ff-71cc8589742a996d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:41:45Z" - latency: 7.757968ms message: 'load-balancer-api-external: resolved host name a23a7fce0ce7143d38b69e38506023ff-71cc8589742a996d.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:41:45Z" - latency: 4.907515ms message: 'load-balancer-api-external: tcp connection to a23a7fce0ce7143d38b69e38506023ff-71cc8589742a996d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:40:45Z" - latency: 7.030863ms message: 'load-balancer-api-external: resolved host name a23a7fce0ce7143d38b69e38506023ff-71cc8589742a996d.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:40:45Z" - latency: 5.131051ms message: 'load-balancer-api-external: tcp connection to a23a7fce0ce7143d38b69e38506023ff-71cc8589742a996d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:39:45Z" - latency: 8.322586ms message: 'load-balancer-api-external: resolved host name a23a7fce0ce7143d38b69e38506023ff-71cc8589742a996d.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:39:45Z" - latency: 5.366122ms message: 'load-balancer-api-external: tcp connection to a23a7fce0ce7143d38b69e38506023ff-71cc8589742a996d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:38:45Z" - latency: 7.885208ms message: 'load-balancer-api-external: resolved host name a23a7fce0ce7143d38b69e38506023ff-71cc8589742a996d.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:38:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T22:00:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-57-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-57.us-east-2.compute.internal uid: 0d5195bc-2fbc-40c0-8c10-c2e3c200a88f resourceVersion: "120840" uid: c66138a0-ca49-4504-9599-755abbb3450c spec: sourcePod: network-check-source-6f78d59f99-cw95x targetEndpoint: a23a7fce0ce7143d38b69e38506023ff-71cc8589742a996d.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T22:06:45Z" message: 'load-balancer-api-internal: tcp connection to a23a7fce0ce7143d38b69e38506023ff-71cc8589742a996d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.139933ms message: 'load-balancer-api-internal: tcp connection to a23a7fce0ce7143d38b69e38506023ff-71cc8589742a996d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:42:45Z" - latency: 6.757874ms message: 'load-balancer-api-internal: resolved host name a23a7fce0ce7143d38b69e38506023ff-71cc8589742a996d.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:42:45Z" - latency: 5.154389ms message: 'load-balancer-api-internal: tcp connection to a23a7fce0ce7143d38b69e38506023ff-71cc8589742a996d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:41:45Z" - latency: 7.72819ms message: 'load-balancer-api-internal: resolved host name a23a7fce0ce7143d38b69e38506023ff-71cc8589742a996d.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:41:45Z" - latency: 5.001632ms message: 'load-balancer-api-internal: tcp connection to a23a7fce0ce7143d38b69e38506023ff-71cc8589742a996d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:40:45Z" - latency: 6.968868ms message: 'load-balancer-api-internal: resolved host name a23a7fce0ce7143d38b69e38506023ff-71cc8589742a996d.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:40:45Z" - latency: 5.20477ms message: 'load-balancer-api-internal: tcp connection to a23a7fce0ce7143d38b69e38506023ff-71cc8589742a996d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:39:45Z" - latency: 8.272635ms message: 'load-balancer-api-internal: resolved host name a23a7fce0ce7143d38b69e38506023ff-71cc8589742a996d.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:39:45Z" - latency: 6.453519ms message: 'load-balancer-api-internal: tcp connection to a23a7fce0ce7143d38b69e38506023ff-71cc8589742a996d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:38:45Z" - latency: 7.84361ms message: 'load-balancer-api-internal: resolved host name a23a7fce0ce7143d38b69e38506023ff-71cc8589742a996d.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:38:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T22:00:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-57-to-network-check-target-ip-10-0-131-57 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-57.us-east-2.compute.internal uid: 0d5195bc-2fbc-40c0-8c10-c2e3c200a88f resourceVersion: "120834" uid: 3e0df764-f600-4d93-af47-d3db80560c30 spec: sourcePod: network-check-source-6f78d59f99-cw95x targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-02T22:07:45Z" message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.430675ms message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:42:45Z" - latency: 968.768µs message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:41:45Z" - latency: 1.387301ms message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:40:45Z" - latency: 1.004434ms message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:39:45Z" - latency: 881.933µs message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:38:45Z" - latency: 2.558432ms message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:37:45Z" - latency: 1.074684ms message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:36:45Z" - latency: 16.073721ms message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:35:45Z" - latency: 1.545134ms message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:34:45Z" - latency: 1.192181ms message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:33:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T22:00:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-57-to-network-check-target-ip-10-0-136-9 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-57.us-east-2.compute.internal uid: 0d5195bc-2fbc-40c0-8c10-c2e3c200a88f resourceVersion: "120835" uid: 79d79de5-6a9d-4a7c-93ac-ec261b26bf82 spec: sourcePod: network-check-source-6f78d59f99-cw95x targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-02T22:07:45Z" message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.891506ms message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:42:45Z" - latency: 1.970544ms message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:41:45Z" - latency: 2.225929ms message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:40:45Z" - latency: 2.171504ms message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:39:45Z" - latency: 1.904604ms message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:38:45Z" - latency: 3.369114ms message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:37:45Z" - latency: 2.172427ms message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:36:45Z" - latency: 8.476935ms message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:35:45Z" - latency: 1.712197ms message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:34:45Z" - latency: 2.112223ms message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:33:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T22:00:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-57-to-network-check-target-ip-10-0-142-132 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-57.us-east-2.compute.internal uid: 0d5195bc-2fbc-40c0-8c10-c2e3c200a88f resourceVersion: "120836" uid: d7869587-32e3-43e1-bb1e-aae4d8343f02 spec: sourcePod: network-check-source-6f78d59f99-cw95x targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-02T22:07:45Z" message: 'network-check-target-ip-10-0-142-132: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.02605ms message: 'network-check-target-ip-10-0-142-132: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:42:45Z" - latency: 1.98679ms message: 'network-check-target-ip-10-0-142-132: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:41:45Z" - latency: 2.18926ms message: 'network-check-target-ip-10-0-142-132: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:40:45Z" - latency: 3.061269ms message: 'network-check-target-ip-10-0-142-132: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:39:45Z" - latency: 1.977418ms message: 'network-check-target-ip-10-0-142-132: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:38:45Z" - latency: 3.382707ms message: 'network-check-target-ip-10-0-142-132: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:37:45Z" - latency: 1.927517ms message: 'network-check-target-ip-10-0-142-132: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:36:45Z" - latency: 6.275254ms message: 'network-check-target-ip-10-0-142-132: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:35:45Z" - latency: 2.316588ms message: 'network-check-target-ip-10-0-142-132: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:34:45Z" - latency: 1.858755ms message: 'network-check-target-ip-10-0-142-132: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:33:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T22:00:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-57-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-57.us-east-2.compute.internal uid: 0d5195bc-2fbc-40c0-8c10-c2e3c200a88f resourceVersion: "120837" uid: 15a53728-c28e-42e2-8a82-cd5d5ea1ee10 spec: sourcePod: network-check-source-6f78d59f99-cw95x targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-02T22:06:45Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.006343ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:42:45Z" - latency: 2.185301ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T22:42:45Z" - latency: 1.015197ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:41:45Z" - latency: 1.83052ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T22:41:45Z" - latency: 901.898µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:40:45Z" - latency: 2.033567ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T22:40:45Z" - latency: 844.218µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:39:45Z" - latency: 2.88939ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T22:39:45Z" - latency: 864.136µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:38:45Z" - latency: 2.942947ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T22:38:45Z" kind: List metadata: resourceVersion: ""