apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T13:59:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-92-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-92.ec2.internal uid: 2ba943e5-2053-457b-8f64-b145a1142571 resourceVersion: "16281" uid: d0c0b52d-8f30-4527-aa07-4a8355a6e9bf spec: sourcePod: network-check-source-7bc5b6bf85-mclw4 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-17T14:06:42Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.084967ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:20:41Z" - latency: 1.011684ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:19:41Z" - latency: 1.018182ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:18:41Z" - latency: 962.944µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:17:41Z" - latency: 902.84µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:16:41Z" - latency: 1.067398ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:15:41Z" - latency: 901.259µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:14:41Z" - latency: 1.63604ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:13:41Z" - latency: 1.627246ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:12:41Z" - latency: 1.618487ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:11:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T13:59:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-92-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-92.ec2.internal uid: 2ba943e5-2053-457b-8f64-b145a1142571 resourceVersion: "16971" uid: 516299af-b259-4d9a-a1c2-b14fc9ff9fbd spec: sourcePod: network-check-source-7bc5b6bf85-mclw4 targetEndpoint: a42644e2a7cc443fea697dddd520304e-d7de7c099e966a0c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-17T14:05:42Z" message: 'load-balancer-api-external: tcp connection to a42644e2a7cc443fea697dddd520304e-d7de7c099e966a0c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.554865ms message: 'load-balancer-api-external: tcp connection to a42644e2a7cc443fea697dddd520304e-d7de7c099e966a0c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:23:42Z" - latency: 5.307779ms message: 'load-balancer-api-external: resolved host name a42644e2a7cc443fea697dddd520304e-d7de7c099e966a0c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T14:23:41Z" - latency: 4.355402ms message: 'load-balancer-api-external: tcp connection to a42644e2a7cc443fea697dddd520304e-d7de7c099e966a0c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:22:42Z" - latency: 9.117895ms message: 'load-balancer-api-external: resolved host name a42644e2a7cc443fea697dddd520304e-d7de7c099e966a0c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T14:22:41Z" - latency: 4.073214ms message: 'load-balancer-api-external: tcp connection to a42644e2a7cc443fea697dddd520304e-d7de7c099e966a0c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:21:42Z" - latency: 7.750717ms message: 'load-balancer-api-external: resolved host name a42644e2a7cc443fea697dddd520304e-d7de7c099e966a0c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T14:21:41Z" - latency: 5.517225ms message: 'load-balancer-api-external: tcp connection to a42644e2a7cc443fea697dddd520304e-d7de7c099e966a0c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:20:42Z" - latency: 7.473208ms message: 'load-balancer-api-external: resolved host name a42644e2a7cc443fea697dddd520304e-d7de7c099e966a0c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T14:20:41Z" - latency: 3.91527ms message: 'load-balancer-api-external: tcp connection to a42644e2a7cc443fea697dddd520304e-d7de7c099e966a0c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:19:42Z" - latency: 8.527171ms message: 'load-balancer-api-external: resolved host name a42644e2a7cc443fea697dddd520304e-d7de7c099e966a0c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T14:19:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T13:59:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-92-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-92.ec2.internal uid: 2ba943e5-2053-457b-8f64-b145a1142571 resourceVersion: "16970" uid: 878da9cd-e839-4223-a4e5-516f10827c57 spec: sourcePod: network-check-source-7bc5b6bf85-mclw4 targetEndpoint: a42644e2a7cc443fea697dddd520304e-d7de7c099e966a0c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-17T14:05:42Z" message: 'load-balancer-api-internal: tcp connection to a42644e2a7cc443fea697dddd520304e-d7de7c099e966a0c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.587839ms message: 'load-balancer-api-internal: tcp connection to a42644e2a7cc443fea697dddd520304e-d7de7c099e966a0c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:23:42Z" - latency: 5.346723ms message: 'load-balancer-api-internal: resolved host name a42644e2a7cc443fea697dddd520304e-d7de7c099e966a0c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T14:23:41Z" - latency: 4.16734ms message: 'load-balancer-api-internal: tcp connection to a42644e2a7cc443fea697dddd520304e-d7de7c099e966a0c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:22:42Z" - latency: 9.063893ms message: 'load-balancer-api-internal: resolved host name a42644e2a7cc443fea697dddd520304e-d7de7c099e966a0c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T14:22:41Z" - latency: 3.998316ms message: 'load-balancer-api-internal: tcp connection to a42644e2a7cc443fea697dddd520304e-d7de7c099e966a0c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:21:42Z" - latency: 7.693408ms message: 'load-balancer-api-internal: resolved host name a42644e2a7cc443fea697dddd520304e-d7de7c099e966a0c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T14:21:41Z" - latency: 5.489789ms message: 'load-balancer-api-internal: tcp connection to a42644e2a7cc443fea697dddd520304e-d7de7c099e966a0c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:20:42Z" - latency: 7.513943ms message: 'load-balancer-api-internal: resolved host name a42644e2a7cc443fea697dddd520304e-d7de7c099e966a0c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T14:20:41Z" - latency: 3.926879ms message: 'load-balancer-api-internal: tcp connection to a42644e2a7cc443fea697dddd520304e-d7de7c099e966a0c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:19:42Z" - latency: 8.541092ms message: 'load-balancer-api-internal: resolved host name a42644e2a7cc443fea697dddd520304e-d7de7c099e966a0c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T14:19:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T13:59:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-92-to-network-check-target-ip-10-0-134-16 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-92.ec2.internal uid: 2ba943e5-2053-457b-8f64-b145a1142571 resourceVersion: "16280" uid: 3fe74bca-8b3f-4571-96c0-a82a4d17c27b spec: sourcePod: network-check-source-7bc5b6bf85-mclw4 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-17T14:06:41Z" message: 'network-check-target-ip-10-0-134-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.412627ms message: 'network-check-target-ip-10-0-134-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:20:41Z" - latency: 2.334905ms message: 'network-check-target-ip-10-0-134-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:19:41Z" - latency: 2.032119ms message: 'network-check-target-ip-10-0-134-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:18:41Z" - latency: 2.33855ms message: 'network-check-target-ip-10-0-134-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:17:41Z" - latency: 2.097889ms message: 'network-check-target-ip-10-0-134-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:16:41Z" - latency: 1.893976ms message: 'network-check-target-ip-10-0-134-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:15:41Z" - latency: 2.271677ms message: 'network-check-target-ip-10-0-134-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:14:41Z" - latency: 2.157757ms message: 'network-check-target-ip-10-0-134-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:13:41Z" - latency: 2.127171ms message: 'network-check-target-ip-10-0-134-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:12:41Z" - latency: 2.051198ms message: 'network-check-target-ip-10-0-134-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:11:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T13:59:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-92-to-network-check-target-ip-10-0-138-92 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-92.ec2.internal uid: 2ba943e5-2053-457b-8f64-b145a1142571 resourceVersion: "16278" uid: b0f12b34-14b5-4c5f-be83-9c7a9a1026cf spec: sourcePod: network-check-source-7bc5b6bf85-mclw4 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-17T14:06:41Z" message: 'network-check-target-ip-10-0-138-92: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 921.614µs message: 'network-check-target-ip-10-0-138-92: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:20:41Z" - latency: 846.97µs message: 'network-check-target-ip-10-0-138-92: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:19:41Z" - latency: 1.073915ms message: 'network-check-target-ip-10-0-138-92: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:18:41Z" - latency: 1.176459ms message: 'network-check-target-ip-10-0-138-92: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:17:41Z" - latency: 1.013475ms message: 'network-check-target-ip-10-0-138-92: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:16:41Z" - latency: 1.222818ms message: 'network-check-target-ip-10-0-138-92: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:15:41Z" - latency: 896.517µs message: 'network-check-target-ip-10-0-138-92: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:14:41Z" - latency: 784.792µs message: 'network-check-target-ip-10-0-138-92: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:13:41Z" - latency: 919.36µs message: 'network-check-target-ip-10-0-138-92: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:12:41Z" - latency: 2.168971ms message: 'network-check-target-ip-10-0-138-92: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:11:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T13:59:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-92-to-network-check-target-ip-10-0-139-104 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-92.ec2.internal uid: 2ba943e5-2053-457b-8f64-b145a1142571 resourceVersion: "16279" uid: c3a6e061-eacf-4212-af40-b1f71821e962 spec: sourcePod: network-check-source-7bc5b6bf85-mclw4 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-17T14:06:41Z" message: 'network-check-target-ip-10-0-139-104: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.910033ms message: 'network-check-target-ip-10-0-139-104: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:20:41Z" - latency: 1.948518ms message: 'network-check-target-ip-10-0-139-104: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:19:41Z" - latency: 1.968977ms message: 'network-check-target-ip-10-0-139-104: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:18:41Z" - latency: 2.044108ms message: 'network-check-target-ip-10-0-139-104: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:17:41Z" - latency: 2.019182ms message: 'network-check-target-ip-10-0-139-104: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:16:41Z" - latency: 1.922104ms message: 'network-check-target-ip-10-0-139-104: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:15:41Z" - latency: 2.045468ms message: 'network-check-target-ip-10-0-139-104: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:14:41Z" - latency: 1.967793ms message: 'network-check-target-ip-10-0-139-104: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:13:41Z" - latency: 2.051833ms message: 'network-check-target-ip-10-0-139-104: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:12:41Z" - latency: 2.159404ms message: 'network-check-target-ip-10-0-139-104: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:11:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T13:59:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-92-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-92.ec2.internal uid: 2ba943e5-2053-457b-8f64-b145a1142571 resourceVersion: "16969" uid: 4c298cf4-94da-4f4f-abf7-b4c11e3118fd spec: sourcePod: network-check-source-7bc5b6bf85-mclw4 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-17T14:05:41Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 841.326µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:23:41Z" - latency: 1.822535ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T14:23:41Z" - latency: 1.183749ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:22:41Z" - latency: 2.121058ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T14:22:41Z" - latency: 1.005442ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:21:41Z" - latency: 1.782523ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T14:21:41Z" - latency: 1.082153ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:20:41Z" - latency: 1.769218ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T14:20:41Z" - latency: 843.105µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:19:41Z" - latency: 1.549735ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T14:19:41Z" kind: List metadata: resourceVersion: ""