apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T21:51:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-189-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-189.ec2.internal uid: 1b8b5fe1-4aa3-4079-aa92-f94c357b75ab resourceVersion: "45281" uid: c75a9d90-6b2c-494a-9dfe-ee1d38723213 spec: sourcePod: network-check-source-dbd9cf844-jhw2q targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-09T21:58:14Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.532489ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:19:14Z" - latency: 878.929µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:18:14Z" - latency: 1.327589ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:17:14Z" - latency: 898.948µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:16:14Z" - latency: 1.029129ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:15:14Z" - latency: 942.091µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:14:14Z" - latency: 847.237µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:13:14Z" - latency: 764.084µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:12:14Z" - latency: 1.010818ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:11:14Z" - latency: 1.051648ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:10:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T21:51:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-189-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-189.ec2.internal uid: 1b8b5fe1-4aa3-4079-aa92-f94c357b75ab resourceVersion: "47335" uid: 7e34e704-181e-4489-97b4-eff08090acd8 spec: sourcePod: network-check-source-dbd9cf844-jhw2q targetEndpoint: ade396db01fc84283aba61ef485ef2b9-04419338d6947fa1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T21:57:14Z" message: 'load-balancer-api-external: tcp connection to ade396db01fc84283aba61ef485ef2b9-04419338d6947fa1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.597596ms message: 'load-balancer-api-external: tcp connection to ade396db01fc84283aba61ef485ef2b9-04419338d6947fa1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:21:14Z" - latency: 8.345249ms message: 'load-balancer-api-external: resolved host name ade396db01fc84283aba61ef485ef2b9-04419338d6947fa1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T22:21:14Z" - latency: 4.237193ms message: 'load-balancer-api-external: tcp connection to ade396db01fc84283aba61ef485ef2b9-04419338d6947fa1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:20:14Z" - latency: 8.815954ms message: 'load-balancer-api-external: resolved host name ade396db01fc84283aba61ef485ef2b9-04419338d6947fa1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T22:20:14Z" - latency: 3.260157ms message: 'load-balancer-api-external: tcp connection to ade396db01fc84283aba61ef485ef2b9-04419338d6947fa1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:19:14Z" - latency: 8.154743ms message: 'load-balancer-api-external: resolved host name ade396db01fc84283aba61ef485ef2b9-04419338d6947fa1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T22:19:14Z" - latency: 4.602438ms message: 'load-balancer-api-external: tcp connection to ade396db01fc84283aba61ef485ef2b9-04419338d6947fa1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:18:14Z" - latency: 8.754915ms message: 'load-balancer-api-external: resolved host name ade396db01fc84283aba61ef485ef2b9-04419338d6947fa1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T22:18:14Z" - latency: 4.936155ms message: 'load-balancer-api-external: tcp connection to ade396db01fc84283aba61ef485ef2b9-04419338d6947fa1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:17:14Z" - latency: 8.451943ms message: 'load-balancer-api-external: resolved host name ade396db01fc84283aba61ef485ef2b9-04419338d6947fa1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T22:17:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T21:51:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-189-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-189.ec2.internal uid: 1b8b5fe1-4aa3-4079-aa92-f94c357b75ab resourceVersion: "47334" uid: 71040555-8cf1-48cc-87cd-10a6eefde205 spec: sourcePod: network-check-source-dbd9cf844-jhw2q targetEndpoint: ade396db01fc84283aba61ef485ef2b9-04419338d6947fa1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T21:57:14Z" message: 'load-balancer-api-internal: tcp connection to ade396db01fc84283aba61ef485ef2b9-04419338d6947fa1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.901901ms message: 'load-balancer-api-internal: tcp connection to ade396db01fc84283aba61ef485ef2b9-04419338d6947fa1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:21:14Z" - latency: 8.397131ms message: 'load-balancer-api-internal: resolved host name ade396db01fc84283aba61ef485ef2b9-04419338d6947fa1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T22:21:14Z" - latency: 5.589471ms message: 'load-balancer-api-internal: tcp connection to ade396db01fc84283aba61ef485ef2b9-04419338d6947fa1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:20:14Z" - latency: 8.785364ms message: 'load-balancer-api-internal: resolved host name ade396db01fc84283aba61ef485ef2b9-04419338d6947fa1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T22:20:14Z" - latency: 3.282925ms message: 'load-balancer-api-internal: tcp connection to ade396db01fc84283aba61ef485ef2b9-04419338d6947fa1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:19:14Z" - latency: 8.189942ms message: 'load-balancer-api-internal: resolved host name ade396db01fc84283aba61ef485ef2b9-04419338d6947fa1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T22:19:14Z" - latency: 4.536432ms message: 'load-balancer-api-internal: tcp connection to ade396db01fc84283aba61ef485ef2b9-04419338d6947fa1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:18:14Z" - latency: 8.855666ms message: 'load-balancer-api-internal: resolved host name ade396db01fc84283aba61ef485ef2b9-04419338d6947fa1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T22:18:14Z" - latency: 4.904464ms message: 'load-balancer-api-internal: tcp connection to ade396db01fc84283aba61ef485ef2b9-04419338d6947fa1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:17:14Z" - latency: 8.48323ms message: 'load-balancer-api-internal: resolved host name ade396db01fc84283aba61ef485ef2b9-04419338d6947fa1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T22:17:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T21:51:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-189-to-network-check-target-ip-10-0-128-8 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-189.ec2.internal uid: 1b8b5fe1-4aa3-4079-aa92-f94c357b75ab resourceVersion: "45279" uid: 27dca7fe-5289-4868-b12b-be4bf2572025 spec: sourcePod: network-check-source-dbd9cf844-jhw2q targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-09T21:58:14Z" message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.936066ms message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:19:14Z" - latency: 2.019428ms message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:18:14Z" - latency: 1.897796ms message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:17:14Z" - latency: 1.870422ms message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:16:14Z" - latency: 1.987064ms message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:15:14Z" - latency: 1.855294ms message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:14:14Z" - latency: 1.925836ms message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:13:14Z" - latency: 2.128355ms message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:12:14Z" - latency: 1.876626ms message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:11:14Z" - latency: 1.828506ms message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:10:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T21:51:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-189-to-network-check-target-ip-10-0-132-68 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-189.ec2.internal uid: 1b8b5fe1-4aa3-4079-aa92-f94c357b75ab resourceVersion: "45280" uid: fbf3af70-835c-4741-b37b-f7abad1f7a1b spec: sourcePod: network-check-source-dbd9cf844-jhw2q targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-09T21:58:14Z" message: 'network-check-target-ip-10-0-132-68: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.178015ms message: 'network-check-target-ip-10-0-132-68: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:19:14Z" - latency: 2.160393ms message: 'network-check-target-ip-10-0-132-68: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:18:14Z" - latency: 2.166018ms message: 'network-check-target-ip-10-0-132-68: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:17:14Z" - latency: 2.069872ms message: 'network-check-target-ip-10-0-132-68: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:16:14Z" - latency: 2.119846ms message: 'network-check-target-ip-10-0-132-68: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:15:14Z" - latency: 2.023589ms message: 'network-check-target-ip-10-0-132-68: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:14:14Z" - latency: 2.259719ms message: 'network-check-target-ip-10-0-132-68: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:13:14Z" - latency: 2.152775ms message: 'network-check-target-ip-10-0-132-68: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:12:14Z" - latency: 1.839274ms message: 'network-check-target-ip-10-0-132-68: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:11:14Z" - latency: 2.268551ms message: 'network-check-target-ip-10-0-132-68: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:10:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T21:51:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-189-to-network-check-target-ip-10-0-143-189 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-189.ec2.internal uid: 1b8b5fe1-4aa3-4079-aa92-f94c357b75ab resourceVersion: "45278" uid: 2ec9fc80-2ce7-4620-b4e9-bbfe6da36384 spec: sourcePod: network-check-source-dbd9cf844-jhw2q targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-09T21:58:14Z" message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 911.381µs message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:19:14Z" - latency: 1.618332ms message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:18:14Z" - latency: 1.474634ms message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:17:14Z" - latency: 834.436µs message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:16:14Z" - latency: 852.657µs message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:15:14Z" - latency: 1.471224ms message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:14:14Z" - latency: 792.212µs message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:13:14Z" - latency: 1.208559ms message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:12:14Z" - latency: 775.009µs message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:11:14Z" - latency: 929.58µs message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:10:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T21:51:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-189-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-189.ec2.internal uid: 1b8b5fe1-4aa3-4079-aa92-f94c357b75ab resourceVersion: "47333" uid: d51b371b-584b-4e92-9697-be6bec58c69a spec: sourcePod: network-check-source-dbd9cf844-jhw2q targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-09T21:57:14Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 819.144µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:21:14Z" - latency: 1.893509ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T22:21:14Z" - latency: 811.374µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:20:14Z" - latency: 2.424853ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T22:20:14Z" - latency: 1.12735ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:19:14Z" - latency: 1.765156ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T22:19:14Z" - latency: 843.056µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:18:14Z" - latency: 2.433769ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T22:18:14Z" - latency: 1.005207ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T22:17:14Z" - latency: 1.690222ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T22:17:14Z" kind: List metadata: resourceVersion: ""