apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T21:33:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-53-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-53.ec2.internal uid: 7eba11b5-c838-4d5b-8788-b70f4e656638 resourceVersion: "28058" uid: 016f00de-8ae5-4bfc-ac10-2ae8119979df spec: sourcePod: network-check-source-6947749cfc-ltg49 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-12T21:40:35Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.093606ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:47:35Z" - latency: 930.853µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:46:35Z" - latency: 991.893µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:45:35Z" - latency: 823.635µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:44:35Z" - latency: 1.098408ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:43:35Z" - latency: 1.397726ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:42:35Z" - latency: 1.123533ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:41:35Z" - latency: 839.006µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:40:35Z" - latency: 992.563µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:39:35Z" - latency: 985.466µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:38:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T21:33:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-53-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-53.ec2.internal uid: 7eba11b5-c838-4d5b-8788-b70f4e656638 resourceVersion: "26793" uid: 9d725fb6-2e29-4fe6-b9e3-b97c6c35262c spec: sourcePod: network-check-source-6947749cfc-ltg49 targetEndpoint: a39f2857a8d544be09e1421e98febf16-1e30a6d33100f75c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-12T21:39:35Z" message: 'load-balancer-api-external: tcp connection to a39f2857a8d544be09e1421e98febf16-1e30a6d33100f75c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.252482ms message: 'load-balancer-api-external: tcp connection to a39f2857a8d544be09e1421e98febf16-1e30a6d33100f75c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:45:35Z" - latency: 12.145792ms message: 'load-balancer-api-external: resolved host name a39f2857a8d544be09e1421e98febf16-1e30a6d33100f75c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T21:45:35Z" - latency: 4.621265ms message: 'load-balancer-api-external: tcp connection to a39f2857a8d544be09e1421e98febf16-1e30a6d33100f75c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:44:35Z" - latency: 7.998097ms message: 'load-balancer-api-external: resolved host name a39f2857a8d544be09e1421e98febf16-1e30a6d33100f75c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T21:44:35Z" - latency: 5.617067ms message: 'load-balancer-api-external: tcp connection to a39f2857a8d544be09e1421e98febf16-1e30a6d33100f75c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:43:35Z" - latency: 8.268776ms message: 'load-balancer-api-external: resolved host name a39f2857a8d544be09e1421e98febf16-1e30a6d33100f75c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T21:43:35Z" - latency: 5.452174ms message: 'load-balancer-api-external: tcp connection to a39f2857a8d544be09e1421e98febf16-1e30a6d33100f75c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:42:35Z" - latency: 8.67831ms message: 'load-balancer-api-external: resolved host name a39f2857a8d544be09e1421e98febf16-1e30a6d33100f75c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T21:42:35Z" - latency: 4.808924ms message: 'load-balancer-api-external: tcp connection to a39f2857a8d544be09e1421e98febf16-1e30a6d33100f75c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:41:35Z" - latency: 8.405255ms message: 'load-balancer-api-external: resolved host name a39f2857a8d544be09e1421e98febf16-1e30a6d33100f75c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T21:41:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T21:33:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-53-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-53.ec2.internal uid: 7eba11b5-c838-4d5b-8788-b70f4e656638 resourceVersion: "26794" uid: 48a9b4bd-ae50-428c-85ad-d2725b1f2f89 spec: sourcePod: network-check-source-6947749cfc-ltg49 targetEndpoint: a39f2857a8d544be09e1421e98febf16-1e30a6d33100f75c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-12T21:39:35Z" message: 'load-balancer-api-internal: tcp connection to a39f2857a8d544be09e1421e98febf16-1e30a6d33100f75c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.316663ms message: 'load-balancer-api-internal: tcp connection to a39f2857a8d544be09e1421e98febf16-1e30a6d33100f75c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:45:35Z" - latency: 12.044112ms message: 'load-balancer-api-internal: resolved host name a39f2857a8d544be09e1421e98febf16-1e30a6d33100f75c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T21:45:35Z" - latency: 4.529666ms message: 'load-balancer-api-internal: tcp connection to a39f2857a8d544be09e1421e98febf16-1e30a6d33100f75c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:44:35Z" - latency: 8.017281ms message: 'load-balancer-api-internal: resolved host name a39f2857a8d544be09e1421e98febf16-1e30a6d33100f75c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T21:44:35Z" - latency: 5.637138ms message: 'load-balancer-api-internal: tcp connection to a39f2857a8d544be09e1421e98febf16-1e30a6d33100f75c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:43:35Z" - latency: 8.177561ms message: 'load-balancer-api-internal: resolved host name a39f2857a8d544be09e1421e98febf16-1e30a6d33100f75c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T21:43:35Z" - latency: 5.468214ms message: 'load-balancer-api-internal: tcp connection to a39f2857a8d544be09e1421e98febf16-1e30a6d33100f75c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:42:35Z" - latency: 8.642201ms message: 'load-balancer-api-internal: resolved host name a39f2857a8d544be09e1421e98febf16-1e30a6d33100f75c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T21:42:35Z" - latency: 4.895117ms message: 'load-balancer-api-internal: tcp connection to a39f2857a8d544be09e1421e98febf16-1e30a6d33100f75c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:41:35Z" - latency: 8.34362ms message: 'load-balancer-api-internal: resolved host name a39f2857a8d544be09e1421e98febf16-1e30a6d33100f75c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T21:41:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T21:33:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-53-to-network-check-target-ip-10-0-131-198 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-53.ec2.internal uid: 7eba11b5-c838-4d5b-8788-b70f4e656638 resourceVersion: "28056" uid: 23306b6e-1a68-41cb-873d-a8f386e37082 spec: sourcePod: network-check-source-6947749cfc-ltg49 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-12T21:40:35Z" message: 'network-check-target-ip-10-0-131-198: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.835845ms message: 'network-check-target-ip-10-0-131-198: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:47:35Z" - latency: 1.98727ms message: 'network-check-target-ip-10-0-131-198: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:46:35Z" - latency: 1.973934ms message: 'network-check-target-ip-10-0-131-198: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:45:35Z" - latency: 2.009564ms message: 'network-check-target-ip-10-0-131-198: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:44:35Z" - latency: 1.865416ms message: 'network-check-target-ip-10-0-131-198: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:43:35Z" - latency: 1.890502ms message: 'network-check-target-ip-10-0-131-198: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:42:35Z" - latency: 1.965541ms message: 'network-check-target-ip-10-0-131-198: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:41:35Z" - latency: 2.018191ms message: 'network-check-target-ip-10-0-131-198: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:40:35Z" - latency: 1.825841ms message: 'network-check-target-ip-10-0-131-198: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:39:35Z" - latency: 1.723174ms message: 'network-check-target-ip-10-0-131-198: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:38:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T21:33:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-53-to-network-check-target-ip-10-0-135-53 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-53.ec2.internal uid: 7eba11b5-c838-4d5b-8788-b70f4e656638 resourceVersion: "28055" uid: 4670d42e-35b8-4859-8dd4-776a4e16a1dc spec: sourcePod: network-check-source-6947749cfc-ltg49 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-12T21:40:35Z" message: 'network-check-target-ip-10-0-135-53: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 932.733µs message: 'network-check-target-ip-10-0-135-53: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:47:35Z" - latency: 778.41µs message: 'network-check-target-ip-10-0-135-53: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:46:35Z" - latency: 1.333495ms message: 'network-check-target-ip-10-0-135-53: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:45:35Z" - latency: 1.06778ms message: 'network-check-target-ip-10-0-135-53: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:44:35Z" - latency: 977.737µs message: 'network-check-target-ip-10-0-135-53: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:43:35Z" - latency: 775.434µs message: 'network-check-target-ip-10-0-135-53: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:42:35Z" - latency: 898.497µs message: 'network-check-target-ip-10-0-135-53: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:41:35Z" - latency: 942.39µs message: 'network-check-target-ip-10-0-135-53: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:40:35Z" - latency: 1.491071ms message: 'network-check-target-ip-10-0-135-53: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:39:35Z" - latency: 1.264985ms message: 'network-check-target-ip-10-0-135-53: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:38:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T21:33:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-53-to-network-check-target-ip-10-0-136-163 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-53.ec2.internal uid: 7eba11b5-c838-4d5b-8788-b70f4e656638 resourceVersion: "28057" uid: 5c40baa9-111d-4e36-82e5-9edd8b2dd0cd spec: sourcePod: network-check-source-6947749cfc-ltg49 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-12T21:40:35Z" message: 'network-check-target-ip-10-0-136-163: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.38383ms message: 'network-check-target-ip-10-0-136-163: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:47:35Z" - latency: 2.039934ms message: 'network-check-target-ip-10-0-136-163: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:46:35Z" - latency: 2.320838ms message: 'network-check-target-ip-10-0-136-163: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:45:35Z" - latency: 2.317454ms message: 'network-check-target-ip-10-0-136-163: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:44:35Z" - latency: 2.433458ms message: 'network-check-target-ip-10-0-136-163: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:43:35Z" - latency: 2.295834ms message: 'network-check-target-ip-10-0-136-163: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:42:35Z" - latency: 2.409411ms message: 'network-check-target-ip-10-0-136-163: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:41:35Z" - latency: 2.214522ms message: 'network-check-target-ip-10-0-136-163: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:40:35Z" - latency: 2.346508ms message: 'network-check-target-ip-10-0-136-163: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:39:35Z" - latency: 2.385981ms message: 'network-check-target-ip-10-0-136-163: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:38:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T21:33:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-53-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-53.ec2.internal uid: 7eba11b5-c838-4d5b-8788-b70f4e656638 resourceVersion: "26792" uid: c3b551bd-9c37-4cdb-9f59-b98da59b63c3 spec: sourcePod: network-check-source-6947749cfc-ltg49 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-12T21:39:35Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.030151ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:45:35Z" - latency: 2.169016ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T21:45:35Z" - latency: 1.073645ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:44:35Z" - latency: 1.818029ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T21:44:35Z" - latency: 1.205005ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:43:35Z" - latency: 1.84163ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T21:43:35Z" - latency: 994.722µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:42:35Z" - latency: 1.641227ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T21:42:35Z" - latency: 905.436µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T21:41:35Z" - latency: 1.904191ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T21:41:35Z" kind: List metadata: resourceVersion: ""