apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T00:15:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-230-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-230.ec2.internal uid: 8187b8d3-a87e-4a36-9713-7288bac4faef resourceVersion: "19569" uid: 710a0d0d-7614-4c79-b821-a46da040c995 spec: sourcePod: network-check-source-7f44b6dd87-66fkn targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-28T00:22:57Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 996.164µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:36:57Z" - latency: 854.223µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:35:57Z" - latency: 882.846µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:34:57Z" - latency: 782.524µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:33:57Z" - latency: 978.417µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:32:57Z" - latency: 892.258µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:31:57Z" - latency: 1.359017ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:30:57Z" - latency: 883.305µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:29:57Z" - latency: 784.463µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:28:57Z" - latency: 845.469µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:27:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T00:15:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-230-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-230.ec2.internal uid: 8187b8d3-a87e-4a36-9713-7288bac4faef resourceVersion: "20733" uid: d8525856-c436-418a-bd4b-a2981397aa19 spec: sourcePod: network-check-source-7f44b6dd87-66fkn targetEndpoint: a337948354e564750b340007faaec616-c20bdea35089ac5c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T00:21:57Z" message: 'load-balancer-api-external: tcp connection to a337948354e564750b340007faaec616-c20bdea35089ac5c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.66603ms message: 'load-balancer-api-external: tcp connection to a337948354e564750b340007faaec616-c20bdea35089ac5c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:39:57Z" - latency: 6.41455ms message: 'load-balancer-api-external: resolved host name a337948354e564750b340007faaec616-c20bdea35089ac5c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T00:39:57Z" - latency: 4.583317ms message: 'load-balancer-api-external: tcp connection to a337948354e564750b340007faaec616-c20bdea35089ac5c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:38:57Z" - latency: 6.565349ms message: 'load-balancer-api-external: resolved host name a337948354e564750b340007faaec616-c20bdea35089ac5c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T00:38:57Z" - latency: 3.496542ms message: 'load-balancer-api-external: tcp connection to a337948354e564750b340007faaec616-c20bdea35089ac5c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:37:57Z" - latency: 8.55163ms message: 'load-balancer-api-external: resolved host name a337948354e564750b340007faaec616-c20bdea35089ac5c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T00:37:57Z" - latency: 5.286507ms message: 'load-balancer-api-external: tcp connection to a337948354e564750b340007faaec616-c20bdea35089ac5c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:36:57Z" - latency: 6.119348ms message: 'load-balancer-api-external: resolved host name a337948354e564750b340007faaec616-c20bdea35089ac5c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T00:36:57Z" - latency: 4.005577ms message: 'load-balancer-api-external: tcp connection to a337948354e564750b340007faaec616-c20bdea35089ac5c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:35:57Z" - latency: 6.256592ms message: 'load-balancer-api-external: resolved host name a337948354e564750b340007faaec616-c20bdea35089ac5c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T00:35:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T00:15:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-230-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-230.ec2.internal uid: 8187b8d3-a87e-4a36-9713-7288bac4faef resourceVersion: "20732" uid: a6cf7eb9-9e56-4a87-aad3-2f30f26c50ea spec: sourcePod: network-check-source-7f44b6dd87-66fkn targetEndpoint: a337948354e564750b340007faaec616-c20bdea35089ac5c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T00:21:57Z" message: 'load-balancer-api-internal: tcp connection to a337948354e564750b340007faaec616-c20bdea35089ac5c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.983426ms message: 'load-balancer-api-internal: tcp connection to a337948354e564750b340007faaec616-c20bdea35089ac5c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:39:57Z" - latency: 6.438589ms message: 'load-balancer-api-internal: resolved host name a337948354e564750b340007faaec616-c20bdea35089ac5c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T00:39:57Z" - latency: 4.63655ms message: 'load-balancer-api-internal: tcp connection to a337948354e564750b340007faaec616-c20bdea35089ac5c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:38:57Z" - latency: 6.502699ms message: 'load-balancer-api-internal: resolved host name a337948354e564750b340007faaec616-c20bdea35089ac5c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T00:38:57Z" - latency: 3.526267ms message: 'load-balancer-api-internal: tcp connection to a337948354e564750b340007faaec616-c20bdea35089ac5c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:37:57Z" - latency: 8.518358ms message: 'load-balancer-api-internal: resolved host name a337948354e564750b340007faaec616-c20bdea35089ac5c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T00:37:57Z" - latency: 5.332351ms message: 'load-balancer-api-internal: tcp connection to a337948354e564750b340007faaec616-c20bdea35089ac5c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:36:57Z" - latency: 6.064631ms message: 'load-balancer-api-internal: resolved host name a337948354e564750b340007faaec616-c20bdea35089ac5c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T00:36:57Z" - latency: 5.349356ms message: 'load-balancer-api-internal: tcp connection to a337948354e564750b340007faaec616-c20bdea35089ac5c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:35:57Z" - latency: 6.330629ms message: 'load-balancer-api-internal: resolved host name a337948354e564750b340007faaec616-c20bdea35089ac5c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T00:35:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T00:15:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-230-to-network-check-target-ip-10-0-128-163 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-230.ec2.internal uid: 8187b8d3-a87e-4a36-9713-7288bac4faef resourceVersion: "19567" uid: 0132d8b6-072a-4986-a3e1-b8072508909d spec: sourcePod: network-check-source-7f44b6dd87-66fkn targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-28T00:22:57Z" message: 'network-check-target-ip-10-0-128-163: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.142142ms message: 'network-check-target-ip-10-0-128-163: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:36:57Z" - latency: 2.25389ms message: 'network-check-target-ip-10-0-128-163: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:35:57Z" - latency: 2.018681ms message: 'network-check-target-ip-10-0-128-163: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:34:57Z" - latency: 1.834887ms message: 'network-check-target-ip-10-0-128-163: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:33:57Z" - latency: 1.690332ms message: 'network-check-target-ip-10-0-128-163: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:32:57Z" - latency: 2.039844ms message: 'network-check-target-ip-10-0-128-163: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:31:57Z" - latency: 2.290166ms message: 'network-check-target-ip-10-0-128-163: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:30:57Z" - latency: 2.005783ms message: 'network-check-target-ip-10-0-128-163: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:29:57Z" - latency: 1.665942ms message: 'network-check-target-ip-10-0-128-163: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:28:57Z" - latency: 1.945711ms message: 'network-check-target-ip-10-0-128-163: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:27:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T00:15:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-230-to-network-check-target-ip-10-0-132-16 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-230.ec2.internal uid: 8187b8d3-a87e-4a36-9713-7288bac4faef resourceVersion: "19568" uid: 2ffceebf-9c46-4955-8aae-711b443e26d4 spec: sourcePod: network-check-source-7f44b6dd87-66fkn targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-28T00:22:57Z" message: 'network-check-target-ip-10-0-132-16: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.920664ms message: 'network-check-target-ip-10-0-132-16: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:36:57Z" - latency: 1.760804ms message: 'network-check-target-ip-10-0-132-16: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:35:57Z" - latency: 1.842287ms message: 'network-check-target-ip-10-0-132-16: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:34:57Z" - latency: 1.46168ms message: 'network-check-target-ip-10-0-132-16: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:33:57Z" - latency: 1.648267ms message: 'network-check-target-ip-10-0-132-16: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:32:57Z" - latency: 1.634118ms message: 'network-check-target-ip-10-0-132-16: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:31:57Z" - latency: 2.091885ms message: 'network-check-target-ip-10-0-132-16: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:30:57Z" - latency: 1.881888ms message: 'network-check-target-ip-10-0-132-16: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:29:57Z" - latency: 1.910223ms message: 'network-check-target-ip-10-0-132-16: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:28:57Z" - latency: 1.675763ms message: 'network-check-target-ip-10-0-132-16: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:27:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T00:15:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-230-to-network-check-target-ip-10-0-142-230 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-230.ec2.internal uid: 8187b8d3-a87e-4a36-9713-7288bac4faef resourceVersion: "19566" uid: aeb3ee0b-7412-4d05-a663-1d16d9a26489 spec: sourcePod: network-check-source-7f44b6dd87-66fkn targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-28T00:22:57Z" message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 871.506µs message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:36:57Z" - latency: 1.296103ms message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:35:57Z" - latency: 1.36868ms message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:34:57Z" - latency: 902.541µs message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:33:57Z" - latency: 830.84µs message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:32:57Z" - latency: 855.01µs message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:31:57Z" - latency: 1.19516ms message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:30:57Z" - latency: 864.446µs message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:29:57Z" - latency: 775.753µs message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:28:57Z" - latency: 932.067µs message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:27:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T00:15:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-230-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-230.ec2.internal uid: 8187b8d3-a87e-4a36-9713-7288bac4faef resourceVersion: "20731" uid: 62753d58-b23d-478a-8b90-9aa0aa84416f spec: sourcePod: network-check-source-7f44b6dd87-66fkn targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-28T00:21:57Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 969.619µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:39:57Z" - latency: 1.599975ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T00:39:57Z" - latency: 1.086578ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:38:57Z" - latency: 1.501134ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T00:38:57Z" - latency: 897.747µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:37:57Z" - latency: 1.539806ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T00:37:57Z" - latency: 1.148818ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:36:57Z" - latency: 1.60302ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T00:36:57Z" - latency: 840.129µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T00:35:57Z" - latency: 1.628102ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T00:35:57Z" kind: List metadata: resourceVersion: ""