apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T17:02:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-133-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-133.ec2.internal uid: 58e4312b-289f-4bed-91ed-428f17253787 resourceVersion: "21282" uid: da947f35-ded9-4fab-a894-29f5125d92c9 spec: sourcePod: network-check-source-56499946bc-vrs8b targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-01T17:09:08Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.199683ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:23:08Z" - latency: 984.17µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:22:08Z" - latency: 1.053081ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:21:08Z" - latency: 1.111228ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:20:08Z" - latency: 948.301µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:19:08Z" - latency: 884.289µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:18:08Z" - latency: 1.096701ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:17:08Z" - latency: 948.859µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:16:08Z" - latency: 919.944µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:15:08Z" - latency: 966.652µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:14:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T17:02:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-133-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-133.ec2.internal uid: 58e4312b-289f-4bed-91ed-428f17253787 resourceVersion: "19941" uid: 3a24de1b-e9f5-4080-8e72-f7d03eef8d3a spec: sourcePod: network-check-source-56499946bc-vrs8b targetEndpoint: a4801e912e8b0404db0d1873ccfc6255-39ed2e0e0c36d04e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-01T17:08:08Z" message: 'load-balancer-api-external: tcp connection to a4801e912e8b0404db0d1873ccfc6255-39ed2e0e0c36d04e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.399721ms message: 'load-balancer-api-external: tcp connection to a4801e912e8b0404db0d1873ccfc6255-39ed2e0e0c36d04e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:20:08Z" - latency: 9.565138ms message: 'load-balancer-api-external: resolved host name a4801e912e8b0404db0d1873ccfc6255-39ed2e0e0c36d04e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T17:20:08Z" - latency: 4.66267ms message: 'load-balancer-api-external: tcp connection to a4801e912e8b0404db0d1873ccfc6255-39ed2e0e0c36d04e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:19:08Z" - latency: 8.214749ms message: 'load-balancer-api-external: resolved host name a4801e912e8b0404db0d1873ccfc6255-39ed2e0e0c36d04e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T17:19:08Z" - latency: 6.238436ms message: 'load-balancer-api-external: tcp connection to a4801e912e8b0404db0d1873ccfc6255-39ed2e0e0c36d04e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:18:08Z" - latency: 8.587103ms message: 'load-balancer-api-external: resolved host name a4801e912e8b0404db0d1873ccfc6255-39ed2e0e0c36d04e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T17:18:08Z" - latency: 6.014781ms message: 'load-balancer-api-external: tcp connection to a4801e912e8b0404db0d1873ccfc6255-39ed2e0e0c36d04e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:17:08Z" - latency: 9.718031ms message: 'load-balancer-api-external: resolved host name a4801e912e8b0404db0d1873ccfc6255-39ed2e0e0c36d04e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T17:17:08Z" - latency: 4.385024ms message: 'load-balancer-api-external: tcp connection to a4801e912e8b0404db0d1873ccfc6255-39ed2e0e0c36d04e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:16:08Z" - latency: 8.905101ms message: 'load-balancer-api-external: resolved host name a4801e912e8b0404db0d1873ccfc6255-39ed2e0e0c36d04e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T17:16:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T17:02:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-133-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-133.ec2.internal uid: 58e4312b-289f-4bed-91ed-428f17253787 resourceVersion: "19942" uid: f78a54bf-7de1-42b0-8b90-af2032cae281 spec: sourcePod: network-check-source-56499946bc-vrs8b targetEndpoint: a4801e912e8b0404db0d1873ccfc6255-39ed2e0e0c36d04e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-01T17:08:08Z" message: 'load-balancer-api-internal: tcp connection to a4801e912e8b0404db0d1873ccfc6255-39ed2e0e0c36d04e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.375989ms message: 'load-balancer-api-internal: tcp connection to a4801e912e8b0404db0d1873ccfc6255-39ed2e0e0c36d04e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:20:08Z" - latency: 9.631041ms message: 'load-balancer-api-internal: resolved host name a4801e912e8b0404db0d1873ccfc6255-39ed2e0e0c36d04e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T17:20:08Z" - latency: 4.770712ms message: 'load-balancer-api-internal: tcp connection to a4801e912e8b0404db0d1873ccfc6255-39ed2e0e0c36d04e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:19:08Z" - latency: 8.20495ms message: 'load-balancer-api-internal: resolved host name a4801e912e8b0404db0d1873ccfc6255-39ed2e0e0c36d04e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T17:19:08Z" - latency: 7.628778ms message: 'load-balancer-api-internal: tcp connection to a4801e912e8b0404db0d1873ccfc6255-39ed2e0e0c36d04e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:18:08Z" - latency: 8.530072ms message: 'load-balancer-api-internal: resolved host name a4801e912e8b0404db0d1873ccfc6255-39ed2e0e0c36d04e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T17:18:08Z" - latency: 4.771909ms message: 'load-balancer-api-internal: tcp connection to a4801e912e8b0404db0d1873ccfc6255-39ed2e0e0c36d04e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:17:08Z" - latency: 9.656757ms message: 'load-balancer-api-internal: resolved host name a4801e912e8b0404db0d1873ccfc6255-39ed2e0e0c36d04e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T17:17:08Z" - latency: 4.393971ms message: 'load-balancer-api-internal: tcp connection to a4801e912e8b0404db0d1873ccfc6255-39ed2e0e0c36d04e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:16:08Z" - latency: 9.025352ms message: 'load-balancer-api-internal: resolved host name a4801e912e8b0404db0d1873ccfc6255-39ed2e0e0c36d04e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T17:16:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T17:02:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-133-to-network-check-target-ip-10-0-137-244 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-133.ec2.internal uid: 58e4312b-289f-4bed-91ed-428f17253787 resourceVersion: "21280" uid: eb5abf21-8433-498a-bffa-22805b6b8935 spec: sourcePod: network-check-source-56499946bc-vrs8b targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-01T17:09:08Z" message: 'network-check-target-ip-10-0-137-244: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.159619ms message: 'network-check-target-ip-10-0-137-244: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:23:08Z" - latency: 2.101583ms message: 'network-check-target-ip-10-0-137-244: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:22:08Z" - latency: 2.224036ms message: 'network-check-target-ip-10-0-137-244: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:21:08Z" - latency: 2.227462ms message: 'network-check-target-ip-10-0-137-244: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:20:08Z" - latency: 2.355523ms message: 'network-check-target-ip-10-0-137-244: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:19:08Z" - latency: 2.212838ms message: 'network-check-target-ip-10-0-137-244: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:18:08Z" - latency: 2.367941ms message: 'network-check-target-ip-10-0-137-244: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:17:08Z" - latency: 2.448776ms message: 'network-check-target-ip-10-0-137-244: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:16:08Z" - latency: 2.389561ms message: 'network-check-target-ip-10-0-137-244: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:15:08Z" - latency: 2.249218ms message: 'network-check-target-ip-10-0-137-244: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:14:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T17:02:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-133-to-network-check-target-ip-10-0-138-194 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-133.ec2.internal uid: 58e4312b-289f-4bed-91ed-428f17253787 resourceVersion: "21281" uid: 2941dad7-8bdb-4d85-a620-0e19da1f8ea5 spec: sourcePod: network-check-source-56499946bc-vrs8b targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-01T17:09:08Z" message: 'network-check-target-ip-10-0-138-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.483372ms message: 'network-check-target-ip-10-0-138-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:23:08Z" - latency: 2.357048ms message: 'network-check-target-ip-10-0-138-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:22:08Z" - latency: 2.237031ms message: 'network-check-target-ip-10-0-138-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:21:08Z" - latency: 2.216032ms message: 'network-check-target-ip-10-0-138-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:20:08Z" - latency: 2.507517ms message: 'network-check-target-ip-10-0-138-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:19:08Z" - latency: 2.387917ms message: 'network-check-target-ip-10-0-138-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:18:08Z" - latency: 2.292031ms message: 'network-check-target-ip-10-0-138-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:17:08Z" - latency: 2.413761ms message: 'network-check-target-ip-10-0-138-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:16:08Z" - latency: 2.071765ms message: 'network-check-target-ip-10-0-138-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:15:08Z" - latency: 2.176053ms message: 'network-check-target-ip-10-0-138-194: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:14:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T17:02:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-133-to-network-check-target-ip-10-0-139-133 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-133.ec2.internal uid: 58e4312b-289f-4bed-91ed-428f17253787 resourceVersion: "21279" uid: 393b7366-1473-4582-85ad-cbd79b28e7c8 spec: sourcePod: network-check-source-56499946bc-vrs8b targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-01T17:09:08Z" message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 869.759µs message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:23:08Z" - latency: 895.939µs message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:22:08Z" - latency: 1.350955ms message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:21:08Z" - latency: 1.294292ms message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:20:08Z" - latency: 865.249µs message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:19:08Z" - latency: 947.435µs message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:18:08Z" - latency: 1.353852ms message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:17:08Z" - latency: 1.436959ms message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:16:08Z" - latency: 840.598µs message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:15:08Z" - latency: 960.531µs message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:14:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T17:02:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-133-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-133.ec2.internal uid: 58e4312b-289f-4bed-91ed-428f17253787 resourceVersion: "19940" uid: 949de59b-307e-4532-931e-7e10e12f327c spec: sourcePod: network-check-source-56499946bc-vrs8b targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-01T17:08:08Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 738.508µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:20:08Z" - latency: 2.854577ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T17:20:08Z" - latency: 891.925µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:19:08Z" - latency: 1.861775ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T17:19:08Z" - latency: 771.512µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:18:08Z" - latency: 1.784645ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T17:18:08Z" - latency: 929.372µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:17:08Z" - latency: 2.278214ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T17:17:08Z" - latency: 906.768µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:16:08Z" - latency: 1.71717ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T17:16:08Z" kind: List metadata: resourceVersion: ""