apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T11:41:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-116-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-116.ec2.internal uid: 5beb1d6d-95d6-4f3e-97aa-e832d2840e4a resourceVersion: "60835" uid: d8d29bf5-40cb-436c-8666-1c959635f18a spec: sourcePod: network-check-source-869dcfcdcd-jb84d targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-14T11:48:15Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.300732ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:23:15Z" - latency: 1.104819ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:22:15Z" - latency: 972.241µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:21:15Z" - latency: 1.267101ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:20:15Z" - latency: 1.44059ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:19:15Z" - latency: 2.081152ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:18:15Z" - latency: 952.506µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:17:15Z" - latency: 820.281µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:16:15Z" - latency: 880.085µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:15:15Z" - latency: 847.081µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:14:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T11:41:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-116-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-116.ec2.internal uid: 5beb1d6d-95d6-4f3e-97aa-e832d2840e4a resourceVersion: "60836" uid: 7e94cd58-249f-43fe-8f6b-ba04b84cf0fd spec: sourcePod: network-check-source-869dcfcdcd-jb84d targetEndpoint: aba79760491ee4d199c55d9ec714234d-82f3519b3a2372e4.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-14T11:47:15Z" message: 'load-balancer-api-external: tcp connection to aba79760491ee4d199c55d9ec714234d-82f3519b3a2372e4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.287371ms message: 'load-balancer-api-external: tcp connection to aba79760491ee4d199c55d9ec714234d-82f3519b3a2372e4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:23:15Z" - latency: 7.181081ms message: 'load-balancer-api-external: resolved host name aba79760491ee4d199c55d9ec714234d-82f3519b3a2372e4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T12:23:15Z" - latency: 4.603578ms message: 'load-balancer-api-external: tcp connection to aba79760491ee4d199c55d9ec714234d-82f3519b3a2372e4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:22:15Z" - latency: 6.62739ms message: 'load-balancer-api-external: resolved host name aba79760491ee4d199c55d9ec714234d-82f3519b3a2372e4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T12:22:15Z" - latency: 6.278435ms message: 'load-balancer-api-external: tcp connection to aba79760491ee4d199c55d9ec714234d-82f3519b3a2372e4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:21:15Z" - latency: 6.981656ms message: 'load-balancer-api-external: resolved host name aba79760491ee4d199c55d9ec714234d-82f3519b3a2372e4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T12:21:15Z" - latency: 4.661844ms message: 'load-balancer-api-external: tcp connection to aba79760491ee4d199c55d9ec714234d-82f3519b3a2372e4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:20:15Z" - latency: 7.121825ms message: 'load-balancer-api-external: resolved host name aba79760491ee4d199c55d9ec714234d-82f3519b3a2372e4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T12:20:15Z" - latency: 5.650926ms message: 'load-balancer-api-external: tcp connection to aba79760491ee4d199c55d9ec714234d-82f3519b3a2372e4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:19:15Z" - latency: 6.120923ms message: 'load-balancer-api-external: resolved host name aba79760491ee4d199c55d9ec714234d-82f3519b3a2372e4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T12:19:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T11:41:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-116-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-116.ec2.internal uid: 5beb1d6d-95d6-4f3e-97aa-e832d2840e4a resourceVersion: "60837" uid: c1578e29-f471-4c9e-a142-982e8c566cab spec: sourcePod: network-check-source-869dcfcdcd-jb84d targetEndpoint: aba79760491ee4d199c55d9ec714234d-82f3519b3a2372e4.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-14T11:47:15Z" message: 'load-balancer-api-internal: tcp connection to aba79760491ee4d199c55d9ec714234d-82f3519b3a2372e4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.910769ms message: 'load-balancer-api-internal: tcp connection to aba79760491ee4d199c55d9ec714234d-82f3519b3a2372e4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:23:15Z" - latency: 7.267778ms message: 'load-balancer-api-internal: resolved host name aba79760491ee4d199c55d9ec714234d-82f3519b3a2372e4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T12:23:15Z" - latency: 4.589554ms message: 'load-balancer-api-internal: tcp connection to aba79760491ee4d199c55d9ec714234d-82f3519b3a2372e4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:22:15Z" - latency: 6.601902ms message: 'load-balancer-api-internal: resolved host name aba79760491ee4d199c55d9ec714234d-82f3519b3a2372e4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T12:22:15Z" - latency: 4.237238ms message: 'load-balancer-api-internal: tcp connection to aba79760491ee4d199c55d9ec714234d-82f3519b3a2372e4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:21:15Z" - latency: 7.072286ms message: 'load-balancer-api-internal: resolved host name aba79760491ee4d199c55d9ec714234d-82f3519b3a2372e4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T12:21:15Z" - latency: 5.153899ms message: 'load-balancer-api-internal: tcp connection to aba79760491ee4d199c55d9ec714234d-82f3519b3a2372e4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:20:15Z" - latency: 7.093704ms message: 'load-balancer-api-internal: resolved host name aba79760491ee4d199c55d9ec714234d-82f3519b3a2372e4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T12:20:15Z" - latency: 4.412079ms message: 'load-balancer-api-internal: tcp connection to aba79760491ee4d199c55d9ec714234d-82f3519b3a2372e4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:19:15Z" - latency: 6.20606ms message: 'load-balancer-api-internal: resolved host name aba79760491ee4d199c55d9ec714234d-82f3519b3a2372e4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T12:19:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T11:41:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-116-to-network-check-target-ip-10-0-132-116 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-116.ec2.internal uid: 5beb1d6d-95d6-4f3e-97aa-e832d2840e4a resourceVersion: "60834" uid: a0479acf-020c-4384-a7cd-e314da85f27e spec: sourcePod: network-check-source-869dcfcdcd-jb84d targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-14T11:48:15Z" message: 'network-check-target-ip-10-0-132-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 888.388µs message: 'network-check-target-ip-10-0-132-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:23:15Z" - latency: 844.6µs message: 'network-check-target-ip-10-0-132-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:22:15Z" - latency: 1.36147ms message: 'network-check-target-ip-10-0-132-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:21:15Z" - latency: 915.795µs message: 'network-check-target-ip-10-0-132-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:20:15Z" - latency: 1.644368ms message: 'network-check-target-ip-10-0-132-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:19:15Z" - latency: 1.154855ms message: 'network-check-target-ip-10-0-132-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:18:15Z" - latency: 1.227551ms message: 'network-check-target-ip-10-0-132-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:17:15Z" - latency: 1.697789ms message: 'network-check-target-ip-10-0-132-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:16:15Z" - latency: 1.283808ms message: 'network-check-target-ip-10-0-132-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:15:15Z" - latency: 1.345443ms message: 'network-check-target-ip-10-0-132-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:14:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T11:41:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-116-to-network-check-target-ip-10-0-136-173 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-116.ec2.internal uid: 5beb1d6d-95d6-4f3e-97aa-e832d2840e4a resourceVersion: "60832" uid: ae456de8-cdee-4e12-8b42-83e678d15a22 spec: sourcePod: network-check-source-869dcfcdcd-jb84d targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-14T11:48:15Z" message: 'network-check-target-ip-10-0-136-173: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.244966ms message: 'network-check-target-ip-10-0-136-173: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:23:15Z" - latency: 2.288496ms message: 'network-check-target-ip-10-0-136-173: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:22:15Z" - latency: 2.192132ms message: 'network-check-target-ip-10-0-136-173: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:21:15Z" - latency: 2.783286ms message: 'network-check-target-ip-10-0-136-173: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:20:15Z" - latency: 2.62111ms message: 'network-check-target-ip-10-0-136-173: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:19:15Z" - latency: 2.595194ms message: 'network-check-target-ip-10-0-136-173: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:18:15Z" - latency: 2.305618ms message: 'network-check-target-ip-10-0-136-173: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:17:15Z" - latency: 2.186723ms message: 'network-check-target-ip-10-0-136-173: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:16:15Z" - latency: 2.32603ms message: 'network-check-target-ip-10-0-136-173: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:15:15Z" - latency: 1.867398ms message: 'network-check-target-ip-10-0-136-173: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:14:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T11:41:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-116-to-network-check-target-ip-10-0-136-205 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-116.ec2.internal uid: 5beb1d6d-95d6-4f3e-97aa-e832d2840e4a resourceVersion: "60831" uid: 56e84393-2486-4623-9d9c-20d80ea97b5b spec: sourcePod: network-check-source-869dcfcdcd-jb84d targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-14T11:48:15Z" message: 'network-check-target-ip-10-0-136-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.089831ms message: 'network-check-target-ip-10-0-136-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:23:15Z" - latency: 2.12511ms message: 'network-check-target-ip-10-0-136-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:22:15Z" - latency: 2.037284ms message: 'network-check-target-ip-10-0-136-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:21:15Z" - latency: 2.237847ms message: 'network-check-target-ip-10-0-136-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:20:15Z" - latency: 2.34848ms message: 'network-check-target-ip-10-0-136-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:19:15Z" - latency: 2.15548ms message: 'network-check-target-ip-10-0-136-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:18:15Z" - latency: 2.152956ms message: 'network-check-target-ip-10-0-136-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:17:15Z" - latency: 2.062445ms message: 'network-check-target-ip-10-0-136-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:16:15Z" - latency: 1.875843ms message: 'network-check-target-ip-10-0-136-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:15:15Z" - latency: 2.039266ms message: 'network-check-target-ip-10-0-136-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:14:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T11:41:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-116-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-116.ec2.internal uid: 5beb1d6d-95d6-4f3e-97aa-e832d2840e4a resourceVersion: "60833" uid: 989d91f1-3e94-4a97-8789-231717abe6b5 spec: sourcePod: network-check-source-869dcfcdcd-jb84d targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-14T11:47:15Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 919.847µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:23:15Z" - latency: 1.839432ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T12:23:15Z" - latency: 874.545µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:22:15Z" - latency: 1.711328ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T12:22:15Z" - latency: 1.316922ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:21:15Z" - latency: 1.588119ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T12:21:15Z" - latency: 914.405µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:20:15Z" - latency: 1.936131ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T12:20:15Z" - latency: 872.657µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T12:19:15Z" - latency: 1.911295ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T12:19:15Z" kind: List metadata: resourceVersion: ""