apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T09:57:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-69-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-69.ec2.internal uid: d71dea77-72d2-4809-9573-ddfcb6e0ac5c resourceVersion: "46646" uid: ee5c8839-74a4-43e5-b2ea-ab097a442d24 spec: sourcePod: network-check-source-989f8b8dc-2rmmn targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-09T10:04:16Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 904.532µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:25:16Z" - latency: 1.353969ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:24:16Z" - latency: 1.210658ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:23:16Z" - latency: 961.065µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:22:16Z" - latency: 949.98µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:21:16Z" - latency: 889.946µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:20:16Z" - latency: 975.243µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:19:16Z" - latency: 1.335516ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:18:16Z" - latency: 942.512µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:17:16Z" - latency: 728.418µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:16:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T09:57:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-69-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-69.ec2.internal uid: d71dea77-72d2-4809-9573-ddfcb6e0ac5c resourceVersion: "49690" uid: dc4626db-dbd9-4144-b17b-bd7a483f31ca spec: sourcePod: network-check-source-989f8b8dc-2rmmn targetEndpoint: ab8225b3aa6dd4799b93e6657fadfa59-7c24328bfda0290d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T10:03:16Z" message: 'load-balancer-api-external: tcp connection to ab8225b3aa6dd4799b93e6657fadfa59-7c24328bfda0290d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.300359ms message: 'load-balancer-api-external: tcp connection to ab8225b3aa6dd4799b93e6657fadfa59-7c24328bfda0290d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:27:16Z" - latency: 8.387705ms message: 'load-balancer-api-external: resolved host name ab8225b3aa6dd4799b93e6657fadfa59-7c24328bfda0290d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T10:27:16Z" - latency: 3.282096ms message: 'load-balancer-api-external: tcp connection to ab8225b3aa6dd4799b93e6657fadfa59-7c24328bfda0290d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:26:16Z" - latency: 8.626952ms message: 'load-balancer-api-external: resolved host name ab8225b3aa6dd4799b93e6657fadfa59-7c24328bfda0290d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T10:26:16Z" - latency: 4.82264ms message: 'load-balancer-api-external: tcp connection to ab8225b3aa6dd4799b93e6657fadfa59-7c24328bfda0290d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:25:16Z" - latency: 7.213125ms message: 'load-balancer-api-external: resolved host name ab8225b3aa6dd4799b93e6657fadfa59-7c24328bfda0290d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T10:25:16Z" - latency: 4.844739ms message: 'load-balancer-api-external: tcp connection to ab8225b3aa6dd4799b93e6657fadfa59-7c24328bfda0290d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:24:16Z" - latency: 10.817828ms message: 'load-balancer-api-external: resolved host name ab8225b3aa6dd4799b93e6657fadfa59-7c24328bfda0290d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T10:24:16Z" - latency: 6.337069ms message: 'load-balancer-api-external: tcp connection to ab8225b3aa6dd4799b93e6657fadfa59-7c24328bfda0290d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:23:16Z" - latency: 8.802534ms message: 'load-balancer-api-external: resolved host name ab8225b3aa6dd4799b93e6657fadfa59-7c24328bfda0290d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T10:23:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T09:57:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-69-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-69.ec2.internal uid: d71dea77-72d2-4809-9573-ddfcb6e0ac5c resourceVersion: "49691" uid: ffa82f6b-5f26-470c-822c-7ff5d4c6b320 spec: sourcePod: network-check-source-989f8b8dc-2rmmn targetEndpoint: ab8225b3aa6dd4799b93e6657fadfa59-7c24328bfda0290d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T10:03:16Z" message: 'load-balancer-api-internal: tcp connection to ab8225b3aa6dd4799b93e6657fadfa59-7c24328bfda0290d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.326929ms message: 'load-balancer-api-internal: tcp connection to ab8225b3aa6dd4799b93e6657fadfa59-7c24328bfda0290d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:27:16Z" - latency: 8.359272ms message: 'load-balancer-api-internal: resolved host name ab8225b3aa6dd4799b93e6657fadfa59-7c24328bfda0290d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T10:27:16Z" - latency: 4.586393ms message: 'load-balancer-api-internal: tcp connection to ab8225b3aa6dd4799b93e6657fadfa59-7c24328bfda0290d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:26:16Z" - latency: 8.591583ms message: 'load-balancer-api-internal: resolved host name ab8225b3aa6dd4799b93e6657fadfa59-7c24328bfda0290d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T10:26:16Z" - latency: 4.310506ms message: 'load-balancer-api-internal: tcp connection to ab8225b3aa6dd4799b93e6657fadfa59-7c24328bfda0290d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:25:16Z" - latency: 7.185014ms message: 'load-balancer-api-internal: resolved host name ab8225b3aa6dd4799b93e6657fadfa59-7c24328bfda0290d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T10:25:16Z" - latency: 3.72356ms message: 'load-balancer-api-internal: tcp connection to ab8225b3aa6dd4799b93e6657fadfa59-7c24328bfda0290d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:24:16Z" - latency: 10.279445ms message: 'load-balancer-api-internal: resolved host name ab8225b3aa6dd4799b93e6657fadfa59-7c24328bfda0290d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T10:24:16Z" - latency: 5.371182ms message: 'load-balancer-api-internal: tcp connection to ab8225b3aa6dd4799b93e6657fadfa59-7c24328bfda0290d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:23:16Z" - latency: 8.774191ms message: 'load-balancer-api-internal: resolved host name ab8225b3aa6dd4799b93e6657fadfa59-7c24328bfda0290d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T10:23:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T09:57:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-69-to-network-check-target-ip-10-0-134-220 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-69.ec2.internal uid: d71dea77-72d2-4809-9573-ddfcb6e0ac5c resourceVersion: "46645" uid: e63ced0d-13db-485e-b8c4-06204bf922ed spec: sourcePod: network-check-source-989f8b8dc-2rmmn targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-09T10:04:16Z" message: 'network-check-target-ip-10-0-134-220: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.174383ms message: 'network-check-target-ip-10-0-134-220: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:25:16Z" - latency: 2.023794ms message: 'network-check-target-ip-10-0-134-220: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:24:16Z" - latency: 1.977337ms message: 'network-check-target-ip-10-0-134-220: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:23:16Z" - latency: 2.376102ms message: 'network-check-target-ip-10-0-134-220: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:22:16Z" - latency: 1.878667ms message: 'network-check-target-ip-10-0-134-220: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:21:16Z" - latency: 2.005703ms message: 'network-check-target-ip-10-0-134-220: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:20:16Z" - latency: 2.082727ms message: 'network-check-target-ip-10-0-134-220: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:19:16Z" - latency: 2.267657ms message: 'network-check-target-ip-10-0-134-220: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:18:16Z" - latency: 2.127988ms message: 'network-check-target-ip-10-0-134-220: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:17:16Z" - latency: 2.059521ms message: 'network-check-target-ip-10-0-134-220: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:16:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T09:57:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-69-to-network-check-target-ip-10-0-138-234 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-69.ec2.internal uid: d71dea77-72d2-4809-9573-ddfcb6e0ac5c resourceVersion: "46643" uid: 2a4aee78-132b-4417-9c01-d290cd81d0ad spec: sourcePod: network-check-source-989f8b8dc-2rmmn targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-09T10:04:16Z" message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.831603ms message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:25:16Z" - latency: 2.223748ms message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:24:16Z" - latency: 1.723518ms message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:23:16Z" - latency: 2.107807ms message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:22:16Z" - latency: 2.011863ms message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:21:16Z" - latency: 1.882451ms message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:20:16Z" - latency: 1.877321ms message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:19:16Z" - latency: 2.192692ms message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:18:16Z" - latency: 1.865232ms message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:17:16Z" - latency: 1.819483ms message: 'network-check-target-ip-10-0-138-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:16:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T09:57:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-69-to-network-check-target-ip-10-0-140-69 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-69.ec2.internal uid: d71dea77-72d2-4809-9573-ddfcb6e0ac5c resourceVersion: "46644" uid: 8278846a-f0ad-405a-a731-04ee1c03cc61 spec: sourcePod: network-check-source-989f8b8dc-2rmmn targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-09T10:04:16Z" message: 'network-check-target-ip-10-0-140-69: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.047516ms message: 'network-check-target-ip-10-0-140-69: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:25:16Z" - latency: 1.426558ms message: 'network-check-target-ip-10-0-140-69: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:24:16Z" - latency: 942.362µs message: 'network-check-target-ip-10-0-140-69: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:23:16Z" - latency: 905.915µs message: 'network-check-target-ip-10-0-140-69: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:22:16Z" - latency: 1.002964ms message: 'network-check-target-ip-10-0-140-69: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:21:16Z" - latency: 1.10053ms message: 'network-check-target-ip-10-0-140-69: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:20:16Z" - latency: 1.193184ms message: 'network-check-target-ip-10-0-140-69: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:19:16Z" - latency: 1.487857ms message: 'network-check-target-ip-10-0-140-69: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:18:16Z" - latency: 1.097111ms message: 'network-check-target-ip-10-0-140-69: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:17:16Z" - latency: 885.079µs message: 'network-check-target-ip-10-0-140-69: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:16:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T09:57:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-69-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-69.ec2.internal uid: d71dea77-72d2-4809-9573-ddfcb6e0ac5c resourceVersion: "49687" uid: 12f8281e-01a4-4b9e-816a-b953c4cdf10e spec: sourcePod: network-check-source-989f8b8dc-2rmmn targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-09T10:03:16Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 813.882µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:27:16Z" - latency: 2.298452ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T10:27:16Z" - latency: 790.262µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:26:16Z" - latency: 2.54847ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T10:26:16Z" - latency: 1.344315ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:25:16Z" - latency: 1.874492ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T10:25:16Z" - latency: 781.852µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:24:16Z" - latency: 1.809905ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T10:24:16Z" - latency: 1.017725ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:23:16Z" - latency: 1.767369ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T10:23:16Z" kind: List metadata: resourceVersion: ""