apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T17:12:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-12-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-12.ec2.internal uid: e5ec48e3-cdca-4372-9f4b-54807020147f resourceVersion: "61459" uid: 106dd1d3-a1af-4d25-86dd-c59480e26703 spec: sourcePod: network-check-source-7bc5b6bf85-nq8l4 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-21T17:19:36Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 946.559µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:54:36Z" - latency: 1.349138ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:53:36Z" - latency: 1.141608ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:52:36Z" - latency: 911.189µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:51:36Z" - latency: 898.286µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:50:36Z" - latency: 1.387099ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:49:36Z" - latency: 1.233922ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:48:36Z" - latency: 1.36225ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:47:36Z" - latency: 1.474028ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:46:36Z" - latency: 1.534696ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:45:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T17:12:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-12-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-12.ec2.internal uid: e5ec48e3-cdca-4372-9f4b-54807020147f resourceVersion: "61461" uid: 20a2bf80-aa82-4b4d-84a5-77480f7f4ee1 spec: sourcePod: network-check-source-7bc5b6bf85-nq8l4 targetEndpoint: a1c7a5fdf34ff4267bc50d990a441f39-8b65e73731109ac8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-21T17:18:36Z" message: 'load-balancer-api-external: tcp connection to a1c7a5fdf34ff4267bc50d990a441f39-8b65e73731109ac8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.467565ms message: 'load-balancer-api-external: tcp connection to a1c7a5fdf34ff4267bc50d990a441f39-8b65e73731109ac8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:54:36Z" - latency: 8.305785ms message: 'load-balancer-api-external: resolved host name a1c7a5fdf34ff4267bc50d990a441f39-8b65e73731109ac8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:54:36Z" - latency: 3.408016ms message: 'load-balancer-api-external: tcp connection to a1c7a5fdf34ff4267bc50d990a441f39-8b65e73731109ac8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:53:36Z" - latency: 7.762651ms message: 'load-balancer-api-external: resolved host name a1c7a5fdf34ff4267bc50d990a441f39-8b65e73731109ac8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:53:36Z" - latency: 4.632652ms message: 'load-balancer-api-external: tcp connection to a1c7a5fdf34ff4267bc50d990a441f39-8b65e73731109ac8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:52:36Z" - latency: 9.383398ms message: 'load-balancer-api-external: resolved host name a1c7a5fdf34ff4267bc50d990a441f39-8b65e73731109ac8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:52:36Z" - latency: 4.510696ms message: 'load-balancer-api-external: tcp connection to a1c7a5fdf34ff4267bc50d990a441f39-8b65e73731109ac8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:51:36Z" - latency: 7.302937ms message: 'load-balancer-api-external: resolved host name a1c7a5fdf34ff4267bc50d990a441f39-8b65e73731109ac8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:51:36Z" - latency: 4.868147ms message: 'load-balancer-api-external: tcp connection to a1c7a5fdf34ff4267bc50d990a441f39-8b65e73731109ac8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:50:36Z" - latency: 6.691908ms message: 'load-balancer-api-external: resolved host name a1c7a5fdf34ff4267bc50d990a441f39-8b65e73731109ac8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:50:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T17:12:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-12-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-12.ec2.internal uid: e5ec48e3-cdca-4372-9f4b-54807020147f resourceVersion: "61460" uid: f9da2418-c652-4670-b927-120f535a3feb spec: sourcePod: network-check-source-7bc5b6bf85-nq8l4 targetEndpoint: a1c7a5fdf34ff4267bc50d990a441f39-8b65e73731109ac8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-21T17:18:36Z" message: 'load-balancer-api-internal: tcp connection to a1c7a5fdf34ff4267bc50d990a441f39-8b65e73731109ac8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.443017ms message: 'load-balancer-api-internal: tcp connection to a1c7a5fdf34ff4267bc50d990a441f39-8b65e73731109ac8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:54:36Z" - latency: 8.351389ms message: 'load-balancer-api-internal: resolved host name a1c7a5fdf34ff4267bc50d990a441f39-8b65e73731109ac8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:54:36Z" - latency: 3.420763ms message: 'load-balancer-api-internal: tcp connection to a1c7a5fdf34ff4267bc50d990a441f39-8b65e73731109ac8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:53:36Z" - latency: 7.705608ms message: 'load-balancer-api-internal: resolved host name a1c7a5fdf34ff4267bc50d990a441f39-8b65e73731109ac8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:53:36Z" - latency: 4.609126ms message: 'load-balancer-api-internal: tcp connection to a1c7a5fdf34ff4267bc50d990a441f39-8b65e73731109ac8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:52:36Z" - latency: 9.19205ms message: 'load-balancer-api-internal: resolved host name a1c7a5fdf34ff4267bc50d990a441f39-8b65e73731109ac8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:52:36Z" - latency: 5.500537ms message: 'load-balancer-api-internal: tcp connection to a1c7a5fdf34ff4267bc50d990a441f39-8b65e73731109ac8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:51:36Z" - latency: 7.377475ms message: 'load-balancer-api-internal: resolved host name a1c7a5fdf34ff4267bc50d990a441f39-8b65e73731109ac8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:51:36Z" - latency: 4.881423ms message: 'load-balancer-api-internal: tcp connection to a1c7a5fdf34ff4267bc50d990a441f39-8b65e73731109ac8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:50:36Z" - latency: 6.747658ms message: 'load-balancer-api-internal: resolved host name a1c7a5fdf34ff4267bc50d990a441f39-8b65e73731109ac8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:50:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T17:12:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-12-to-network-check-target-ip-10-0-128-12 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-12.ec2.internal uid: e5ec48e3-cdca-4372-9f4b-54807020147f resourceVersion: "61455" uid: 875140ea-ae79-41da-86f8-ccb155ce169e spec: sourcePod: network-check-source-7bc5b6bf85-nq8l4 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-21T17:19:36Z" message: 'network-check-target-ip-10-0-128-12: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 882.45µs message: 'network-check-target-ip-10-0-128-12: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:54:36Z" - latency: 985.446µs message: 'network-check-target-ip-10-0-128-12: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:53:36Z" - latency: 1.701122ms message: 'network-check-target-ip-10-0-128-12: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:52:36Z" - latency: 950.065µs message: 'network-check-target-ip-10-0-128-12: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:51:36Z" - latency: 915.088µs message: 'network-check-target-ip-10-0-128-12: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:50:36Z" - latency: 1.096273ms message: 'network-check-target-ip-10-0-128-12: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:49:36Z" - latency: 1.427851ms message: 'network-check-target-ip-10-0-128-12: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:48:36Z" - latency: 864.98µs message: 'network-check-target-ip-10-0-128-12: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:47:36Z" - latency: 952.013µs message: 'network-check-target-ip-10-0-128-12: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:46:36Z" - latency: 924.836µs message: 'network-check-target-ip-10-0-128-12: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:45:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T17:12:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-12-to-network-check-target-ip-10-0-141-39 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-12.ec2.internal uid: e5ec48e3-cdca-4372-9f4b-54807020147f resourceVersion: "61457" uid: 39e55168-1c8b-4fbb-a223-7f460a24ef9d spec: sourcePod: network-check-source-7bc5b6bf85-nq8l4 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-21T17:19:36Z" message: 'network-check-target-ip-10-0-141-39: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.904254ms message: 'network-check-target-ip-10-0-141-39: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:54:36Z" - latency: 1.92792ms message: 'network-check-target-ip-10-0-141-39: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:53:36Z" - latency: 2.647364ms message: 'network-check-target-ip-10-0-141-39: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:52:36Z" - latency: 2.214414ms message: 'network-check-target-ip-10-0-141-39: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:51:36Z" - latency: 2.099016ms message: 'network-check-target-ip-10-0-141-39: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:50:36Z" - latency: 2.136544ms message: 'network-check-target-ip-10-0-141-39: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:49:36Z" - latency: 2.149803ms message: 'network-check-target-ip-10-0-141-39: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:48:36Z" - latency: 2.175712ms message: 'network-check-target-ip-10-0-141-39: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:47:36Z" - latency: 2.131538ms message: 'network-check-target-ip-10-0-141-39: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:46:36Z" - latency: 2.113796ms message: 'network-check-target-ip-10-0-141-39: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:45:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T17:12:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-12-to-network-check-target-ip-10-0-142-109 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-12.ec2.internal uid: e5ec48e3-cdca-4372-9f4b-54807020147f resourceVersion: "61456" uid: fba82685-d8d5-4eb0-bb48-201c2342d366 spec: sourcePod: network-check-source-7bc5b6bf85-nq8l4 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-21T17:19:36Z" message: 'network-check-target-ip-10-0-142-109: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.115484ms message: 'network-check-target-ip-10-0-142-109: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:54:36Z" - latency: 2.045226ms message: 'network-check-target-ip-10-0-142-109: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:53:36Z" - latency: 2.202117ms message: 'network-check-target-ip-10-0-142-109: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:52:36Z" - latency: 1.9731ms message: 'network-check-target-ip-10-0-142-109: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:51:36Z" - latency: 2.204433ms message: 'network-check-target-ip-10-0-142-109: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:50:36Z" - latency: 2.216098ms message: 'network-check-target-ip-10-0-142-109: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:49:36Z" - latency: 2.298301ms message: 'network-check-target-ip-10-0-142-109: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:48:36Z" - latency: 2.213826ms message: 'network-check-target-ip-10-0-142-109: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:47:36Z" - latency: 2.073181ms message: 'network-check-target-ip-10-0-142-109: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:46:36Z" - latency: 2.24401ms message: 'network-check-target-ip-10-0-142-109: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:45:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T17:12:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-12-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-12.ec2.internal uid: e5ec48e3-cdca-4372-9f4b-54807020147f resourceVersion: "61458" uid: 9c4c8d82-badc-491e-be38-693c1b47bf65 spec: sourcePod: network-check-source-7bc5b6bf85-nq8l4 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-21T17:18:36Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 908.203µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:54:36Z" - latency: 2.184079ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T17:54:36Z" - latency: 874.263µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:53:36Z" - latency: 2.103195ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T17:53:36Z" - latency: 854.744µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:52:36Z" - latency: 2.169666ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T17:52:36Z" - latency: 1.217207ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:51:36Z" - latency: 1.86263ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T17:51:36Z" - latency: 1.060133ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:50:36Z" - latency: 1.771714ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T17:50:36Z" kind: List metadata: resourceVersion: ""