apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T20:05:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-104-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-104.ec2.internal uid: 0d147275-cfd2-443a-86b6-e1bb1ffce16b resourceVersion: "30573" uid: 995682f3-fd96-4c45-9391-9f3843bef962 spec: sourcePod: network-check-source-dbd9cf844-78gtm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-10T20:12:54Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.667225ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:19:54Z" - latency: 1.768703ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:18:54Z" - latency: 1.039841ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:17:54Z" - latency: 889.464µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:16:54Z" - latency: 1.16571ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:15:54Z" - latency: 972.925µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:14:54Z" - latency: 870.075µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:13:54Z" - latency: 800.975µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:12:54Z" - latency: 905.371µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:11:54Z" - latency: 1.158868ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:10:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T20:05:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-104-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-104.ec2.internal uid: 0d147275-cfd2-443a-86b6-e1bb1ffce16b resourceVersion: "29296" uid: d07ccc44-b462-4b16-9135-42a339a28bd1 spec: sourcePod: network-check-source-dbd9cf844-78gtm targetEndpoint: a5df9098b8b794d869fc2fe23a3a9cc3-5005ffac5df5b2fc.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-10T20:11:54Z" message: 'load-balancer-api-external: tcp connection to a5df9098b8b794d869fc2fe23a3a9cc3-5005ffac5df5b2fc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.293637ms message: 'load-balancer-api-external: tcp connection to a5df9098b8b794d869fc2fe23a3a9cc3-5005ffac5df5b2fc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:17:54Z" - latency: 7.111124ms message: 'load-balancer-api-external: resolved host name a5df9098b8b794d869fc2fe23a3a9cc3-5005ffac5df5b2fc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T20:17:54Z" - latency: 5.1388ms message: 'load-balancer-api-external: tcp connection to a5df9098b8b794d869fc2fe23a3a9cc3-5005ffac5df5b2fc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:16:54Z" - latency: 8.650628ms message: 'load-balancer-api-external: resolved host name a5df9098b8b794d869fc2fe23a3a9cc3-5005ffac5df5b2fc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T20:16:54Z" - latency: 4.182671ms message: 'load-balancer-api-external: tcp connection to a5df9098b8b794d869fc2fe23a3a9cc3-5005ffac5df5b2fc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:15:54Z" - latency: 8.428524ms message: 'load-balancer-api-external: resolved host name a5df9098b8b794d869fc2fe23a3a9cc3-5005ffac5df5b2fc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T20:15:54Z" - latency: 4.829412ms message: 'load-balancer-api-external: tcp connection to a5df9098b8b794d869fc2fe23a3a9cc3-5005ffac5df5b2fc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:14:54Z" - latency: 7.163744ms message: 'load-balancer-api-external: resolved host name a5df9098b8b794d869fc2fe23a3a9cc3-5005ffac5df5b2fc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T20:14:54Z" - latency: 5.260501ms message: 'load-balancer-api-external: tcp connection to a5df9098b8b794d869fc2fe23a3a9cc3-5005ffac5df5b2fc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:13:54Z" - latency: 7.205366ms message: 'load-balancer-api-external: resolved host name a5df9098b8b794d869fc2fe23a3a9cc3-5005ffac5df5b2fc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T20:13:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T20:05:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-104-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-104.ec2.internal uid: 0d147275-cfd2-443a-86b6-e1bb1ffce16b resourceVersion: "29297" uid: 5b046532-a96e-4c1c-a636-fef2847abb15 spec: sourcePod: network-check-source-dbd9cf844-78gtm targetEndpoint: a5df9098b8b794d869fc2fe23a3a9cc3-5005ffac5df5b2fc.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-10T20:11:54Z" message: 'load-balancer-api-internal: tcp connection to a5df9098b8b794d869fc2fe23a3a9cc3-5005ffac5df5b2fc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.234458ms message: 'load-balancer-api-internal: tcp connection to a5df9098b8b794d869fc2fe23a3a9cc3-5005ffac5df5b2fc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:17:54Z" - latency: 7.131491ms message: 'load-balancer-api-internal: resolved host name a5df9098b8b794d869fc2fe23a3a9cc3-5005ffac5df5b2fc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T20:17:54Z" - latency: 5.083948ms message: 'load-balancer-api-internal: tcp connection to a5df9098b8b794d869fc2fe23a3a9cc3-5005ffac5df5b2fc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:16:54Z" - latency: 8.566725ms message: 'load-balancer-api-internal: resolved host name a5df9098b8b794d869fc2fe23a3a9cc3-5005ffac5df5b2fc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T20:16:54Z" - latency: 4.633252ms message: 'load-balancer-api-internal: tcp connection to a5df9098b8b794d869fc2fe23a3a9cc3-5005ffac5df5b2fc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:15:54Z" - latency: 8.50383ms message: 'load-balancer-api-internal: resolved host name a5df9098b8b794d869fc2fe23a3a9cc3-5005ffac5df5b2fc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T20:15:54Z" - latency: 4.906945ms message: 'load-balancer-api-internal: tcp connection to a5df9098b8b794d869fc2fe23a3a9cc3-5005ffac5df5b2fc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:14:54Z" - latency: 7.117546ms message: 'load-balancer-api-internal: resolved host name a5df9098b8b794d869fc2fe23a3a9cc3-5005ffac5df5b2fc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T20:14:54Z" - latency: 5.203467ms message: 'load-balancer-api-internal: tcp connection to a5df9098b8b794d869fc2fe23a3a9cc3-5005ffac5df5b2fc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:13:54Z" - latency: 7.158989ms message: 'load-balancer-api-internal: resolved host name a5df9098b8b794d869fc2fe23a3a9cc3-5005ffac5df5b2fc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T20:13:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T20:05:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-104-to-network-check-target-ip-10-0-137-191 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-104.ec2.internal uid: 0d147275-cfd2-443a-86b6-e1bb1ffce16b resourceVersion: "30570" uid: a326917b-50e8-4e1f-9af5-88180ecd08a8 spec: sourcePod: network-check-source-dbd9cf844-78gtm targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-10T20:12:54Z" message: 'network-check-target-ip-10-0-137-191: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.355676ms message: 'network-check-target-ip-10-0-137-191: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:19:54Z" - latency: 2.157214ms message: 'network-check-target-ip-10-0-137-191: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:18:54Z" - latency: 2.326896ms message: 'network-check-target-ip-10-0-137-191: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:17:54Z" - latency: 2.203314ms message: 'network-check-target-ip-10-0-137-191: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:16:54Z" - latency: 2.425818ms message: 'network-check-target-ip-10-0-137-191: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:15:54Z" - latency: 2.192399ms message: 'network-check-target-ip-10-0-137-191: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:14:54Z" - latency: 2.470435ms message: 'network-check-target-ip-10-0-137-191: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:13:54Z" - latency: 2.557411ms message: 'network-check-target-ip-10-0-137-191: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:12:54Z" - latency: 2.323964ms message: 'network-check-target-ip-10-0-137-191: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:11:54Z" - latency: 2.248955ms message: 'network-check-target-ip-10-0-137-191: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:10:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T20:05:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-104-to-network-check-target-ip-10-0-138-104 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-104.ec2.internal uid: 0d147275-cfd2-443a-86b6-e1bb1ffce16b resourceVersion: "30571" uid: 35efad56-f165-4a01-948c-61484630ffb3 spec: sourcePod: network-check-source-dbd9cf844-78gtm targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-10T20:12:54Z" message: 'network-check-target-ip-10-0-138-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 795.12µs message: 'network-check-target-ip-10-0-138-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:19:54Z" - latency: 811.559µs message: 'network-check-target-ip-10-0-138-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:18:54Z" - latency: 961.434µs message: 'network-check-target-ip-10-0-138-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:17:54Z" - latency: 799.803µs message: 'network-check-target-ip-10-0-138-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:16:54Z" - latency: 990.84µs message: 'network-check-target-ip-10-0-138-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:15:54Z" - latency: 963.227µs message: 'network-check-target-ip-10-0-138-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:14:54Z" - latency: 1.213357ms message: 'network-check-target-ip-10-0-138-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:13:54Z" - latency: 813.92µs message: 'network-check-target-ip-10-0-138-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:12:54Z" - latency: 969.132µs message: 'network-check-target-ip-10-0-138-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:11:54Z" - latency: 1.018643ms message: 'network-check-target-ip-10-0-138-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:10:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T20:05:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-104-to-network-check-target-ip-10-0-139-224 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-104.ec2.internal uid: 0d147275-cfd2-443a-86b6-e1bb1ffce16b resourceVersion: "30572" uid: a490e9f8-4292-4358-baea-f1ff956bb6c5 spec: sourcePod: network-check-source-dbd9cf844-78gtm targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-10T20:12:54Z" message: 'network-check-target-ip-10-0-139-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.701102ms message: 'network-check-target-ip-10-0-139-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:19:54Z" - latency: 2.424389ms message: 'network-check-target-ip-10-0-139-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:18:54Z" - latency: 2.535732ms message: 'network-check-target-ip-10-0-139-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:17:54Z" - latency: 2.383059ms message: 'network-check-target-ip-10-0-139-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:16:54Z" - latency: 2.403444ms message: 'network-check-target-ip-10-0-139-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:15:54Z" - latency: 2.624647ms message: 'network-check-target-ip-10-0-139-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:14:54Z" - latency: 2.379376ms message: 'network-check-target-ip-10-0-139-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:13:54Z" - latency: 2.193984ms message: 'network-check-target-ip-10-0-139-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:12:54Z" - latency: 2.374183ms message: 'network-check-target-ip-10-0-139-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:11:54Z" - latency: 2.571046ms message: 'network-check-target-ip-10-0-139-224: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:10:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T20:05:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-104-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-104.ec2.internal uid: 0d147275-cfd2-443a-86b6-e1bb1ffce16b resourceVersion: "29295" uid: e35613d1-b8f4-4813-8058-0de43cb1a70f spec: sourcePod: network-check-source-dbd9cf844-78gtm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-10T20:11:54Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.006252ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:17:54Z" - latency: 1.705884ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T20:17:54Z" - latency: 1.247469ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:16:54Z" - latency: 1.741249ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T20:16:54Z" - latency: 935.428µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:15:54Z" - latency: 1.562552ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T20:15:54Z" - latency: 788.898µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:14:54Z" - latency: 1.828687ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T20:14:54Z" - latency: 803.576µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T20:13:54Z" - latency: 1.776441ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T20:13:54Z" kind: List metadata: resourceVersion: ""