apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T18:23:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-181-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-181.ec2.internal uid: 24e2d102-57ac-4fa3-a516-636fc7616cd4 resourceVersion: "44942" uid: b1ac5d16-61e2-4174-8979-7e1e3fa24427 spec: sourcePod: network-check-source-dbd9cf844-7hhtm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-08T18:30:12Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 906.228µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:51:12Z" - latency: 1.132081ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:50:12Z" - latency: 1.406332ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:49:12Z" - latency: 1.34328ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:48:12Z" - latency: 1.130707ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:47:12Z" - latency: 1.136264ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:46:12Z" - latency: 1.345966ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:45:12Z" - latency: 813.233µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:44:12Z" - latency: 1.278139ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:43:12Z" - latency: 888.703µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:42:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T18:23:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-181-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-181.ec2.internal uid: 24e2d102-57ac-4fa3-a516-636fc7616cd4 resourceVersion: "47069" uid: e82ed694-66bc-4837-b5f9-95b343f3a8fd spec: sourcePod: network-check-source-dbd9cf844-7hhtm targetEndpoint: af9fabd93c9954891ba377e3181b81d8-96cdb4f69436208d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-08T18:29:12Z" message: 'load-balancer-api-external: tcp connection to af9fabd93c9954891ba377e3181b81d8-96cdb4f69436208d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.850574ms message: 'load-balancer-api-external: tcp connection to af9fabd93c9954891ba377e3181b81d8-96cdb4f69436208d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:53:12Z" - latency: 8.935704ms message: 'load-balancer-api-external: resolved host name af9fabd93c9954891ba377e3181b81d8-96cdb4f69436208d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T18:53:12Z" - latency: 3.702535ms message: 'load-balancer-api-external: tcp connection to af9fabd93c9954891ba377e3181b81d8-96cdb4f69436208d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:52:12Z" - latency: 7.14743ms message: 'load-balancer-api-external: resolved host name af9fabd93c9954891ba377e3181b81d8-96cdb4f69436208d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T18:52:12Z" - latency: 4.496223ms message: 'load-balancer-api-external: tcp connection to af9fabd93c9954891ba377e3181b81d8-96cdb4f69436208d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:51:12Z" - latency: 7.333563ms message: 'load-balancer-api-external: resolved host name af9fabd93c9954891ba377e3181b81d8-96cdb4f69436208d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T18:51:12Z" - latency: 4.264499ms message: 'load-balancer-api-external: tcp connection to af9fabd93c9954891ba377e3181b81d8-96cdb4f69436208d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:50:12Z" - latency: 8.568866ms message: 'load-balancer-api-external: resolved host name af9fabd93c9954891ba377e3181b81d8-96cdb4f69436208d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T18:50:12Z" - latency: 5.082895ms message: 'load-balancer-api-external: tcp connection to af9fabd93c9954891ba377e3181b81d8-96cdb4f69436208d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:49:12Z" - latency: 9.038148ms message: 'load-balancer-api-external: resolved host name af9fabd93c9954891ba377e3181b81d8-96cdb4f69436208d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T18:49:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T18:23:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-181-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-181.ec2.internal uid: 24e2d102-57ac-4fa3-a516-636fc7616cd4 resourceVersion: "47070" uid: cdd04a49-cd1e-439a-908d-d56a5ea21a74 spec: sourcePod: network-check-source-dbd9cf844-7hhtm targetEndpoint: af9fabd93c9954891ba377e3181b81d8-96cdb4f69436208d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-08T18:29:12Z" message: 'load-balancer-api-internal: tcp connection to af9fabd93c9954891ba377e3181b81d8-96cdb4f69436208d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.877328ms message: 'load-balancer-api-internal: tcp connection to af9fabd93c9954891ba377e3181b81d8-96cdb4f69436208d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:53:12Z" - latency: 8.888731ms message: 'load-balancer-api-internal: resolved host name af9fabd93c9954891ba377e3181b81d8-96cdb4f69436208d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T18:53:12Z" - latency: 4.475603ms message: 'load-balancer-api-internal: tcp connection to af9fabd93c9954891ba377e3181b81d8-96cdb4f69436208d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:52:12Z" - latency: 7.244764ms message: 'load-balancer-api-internal: resolved host name af9fabd93c9954891ba377e3181b81d8-96cdb4f69436208d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T18:52:12Z" - latency: 4.504599ms message: 'load-balancer-api-internal: tcp connection to af9fabd93c9954891ba377e3181b81d8-96cdb4f69436208d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:51:12Z" - latency: 7.300406ms message: 'load-balancer-api-internal: resolved host name af9fabd93c9954891ba377e3181b81d8-96cdb4f69436208d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T18:51:12Z" - latency: 4.191874ms message: 'load-balancer-api-internal: tcp connection to af9fabd93c9954891ba377e3181b81d8-96cdb4f69436208d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:50:12Z" - latency: 8.590769ms message: 'load-balancer-api-internal: resolved host name af9fabd93c9954891ba377e3181b81d8-96cdb4f69436208d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T18:50:12Z" - latency: 5.123393ms message: 'load-balancer-api-internal: tcp connection to af9fabd93c9954891ba377e3181b81d8-96cdb4f69436208d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:49:12Z" - latency: 8.975918ms message: 'load-balancer-api-internal: resolved host name af9fabd93c9954891ba377e3181b81d8-96cdb4f69436208d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T18:49:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T18:23:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-181-to-network-check-target-ip-10-0-131-227 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-181.ec2.internal uid: 24e2d102-57ac-4fa3-a516-636fc7616cd4 resourceVersion: "44939" uid: d524ced3-0e6f-4091-a065-df1ba8bb0402 spec: sourcePod: network-check-source-dbd9cf844-7hhtm targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-08T18:30:12Z" message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.08891ms message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:51:12Z" - latency: 1.827526ms message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:50:12Z" - latency: 2.012565ms message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:49:12Z" - latency: 1.778179ms message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:48:12Z" - latency: 1.894705ms message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:47:12Z" - latency: 2.201024ms message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:46:12Z" - latency: 1.929597ms message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:45:12Z" - latency: 2.043129ms message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:44:12Z" - latency: 1.704667ms message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:43:12Z" - latency: 2.148817ms message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:42:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T18:23:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-181-to-network-check-target-ip-10-0-132-181 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-181.ec2.internal uid: 24e2d102-57ac-4fa3-a516-636fc7616cd4 resourceVersion: "44940" uid: a73659dd-df44-4073-92df-e5180ebddf59 spec: sourcePod: network-check-source-dbd9cf844-7hhtm targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-08T18:30:12Z" message: 'network-check-target-ip-10-0-132-181: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.248545ms message: 'network-check-target-ip-10-0-132-181: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:51:12Z" - latency: 1.278963ms message: 'network-check-target-ip-10-0-132-181: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:50:12Z" - latency: 1.417619ms message: 'network-check-target-ip-10-0-132-181: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:49:12Z" - latency: 916.536µs message: 'network-check-target-ip-10-0-132-181: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:48:12Z" - latency: 1.527317ms message: 'network-check-target-ip-10-0-132-181: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:47:12Z" - latency: 867.684µs message: 'network-check-target-ip-10-0-132-181: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:46:12Z" - latency: 857.801µs message: 'network-check-target-ip-10-0-132-181: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:45:12Z" - latency: 1.132641ms message: 'network-check-target-ip-10-0-132-181: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:44:12Z" - latency: 1.666621ms message: 'network-check-target-ip-10-0-132-181: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:43:12Z" - latency: 918.713µs message: 'network-check-target-ip-10-0-132-181: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:42:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T18:23:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-181-to-network-check-target-ip-10-0-135-16 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-181.ec2.internal uid: 24e2d102-57ac-4fa3-a516-636fc7616cd4 resourceVersion: "44941" uid: 5afcdcb9-d8ec-4e1c-a708-ea92ddf3dad7 spec: sourcePod: network-check-source-dbd9cf844-7hhtm targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-08T18:30:12Z" message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.089882ms message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:51:12Z" - latency: 2.199377ms message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:50:12Z" - latency: 2.454916ms message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:49:12Z" - latency: 2.135582ms message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:48:12Z" - latency: 2.345463ms message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:47:12Z" - latency: 2.582137ms message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:46:12Z" - latency: 2.35216ms message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:45:12Z" - latency: 2.100593ms message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:44:12Z" - latency: 2.383594ms message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:43:12Z" - latency: 1.775708ms message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:42:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T18:23:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-181-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-181.ec2.internal uid: 24e2d102-57ac-4fa3-a516-636fc7616cd4 resourceVersion: "47068" uid: 954544c0-7b93-40f0-a153-45e25d62b436 spec: sourcePod: network-check-source-dbd9cf844-7hhtm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-08T18:29:12Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 980.667µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:53:12Z" - latency: 1.926645ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T18:53:12Z" - latency: 902.099µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:52:12Z" - latency: 1.782214ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T18:52:12Z" - latency: 863.954µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:51:12Z" - latency: 2.014825ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T18:51:12Z" - latency: 869.654µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:50:12Z" - latency: 1.986496ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T18:50:12Z" - latency: 987.689µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:49:12Z" - latency: 1.784402ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T18:49:12Z" kind: List metadata: resourceVersion: ""