apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T16:20:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-92-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-92.ec2.internal uid: b775a594-5af0-4e97-9893-cd679d2cca94 resourceVersion: "55361" uid: e669494a-7a61-4d5a-9604-e584f51efb2c spec: sourcePod: network-check-source-685456655f-gmmnn targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-08T16:27:17Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.278975ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:48:17Z" - latency: 1.038686ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:47:17Z" - latency: 899.369µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:46:17Z" - latency: 1.193094ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:45:17Z" - latency: 1.222186ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:44:17Z" - latency: 834.504µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:43:17Z" - latency: 806.13µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:42:17Z" - latency: 1.103837ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:41:17Z" - latency: 1.516521ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:40:17Z" - latency: 838.825µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:39:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T16:20:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-92-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-92.ec2.internal uid: b775a594-5af0-4e97-9893-cd679d2cca94 resourceVersion: "57090" uid: 4196ab9e-a124-434f-a14d-36132a3958c1 spec: sourcePod: network-check-source-685456655f-gmmnn targetEndpoint: a0116dc1371b74a5aafcde640e4b49e8-b79245544ff991a7.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-08T16:26:17Z" message: 'load-balancer-api-external: tcp connection to a0116dc1371b74a5aafcde640e4b49e8-b79245544ff991a7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.819715ms message: 'load-balancer-api-external: tcp connection to a0116dc1371b74a5aafcde640e4b49e8-b79245544ff991a7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:50:17Z" - latency: 8.721044ms message: 'load-balancer-api-external: resolved host name a0116dc1371b74a5aafcde640e4b49e8-b79245544ff991a7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T16:50:17Z" - latency: 5.599498ms message: 'load-balancer-api-external: tcp connection to a0116dc1371b74a5aafcde640e4b49e8-b79245544ff991a7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:49:17Z" - latency: 9.604928ms message: 'load-balancer-api-external: resolved host name a0116dc1371b74a5aafcde640e4b49e8-b79245544ff991a7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T16:49:17Z" - latency: 4.48255ms message: 'load-balancer-api-external: tcp connection to a0116dc1371b74a5aafcde640e4b49e8-b79245544ff991a7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:48:17Z" - latency: 8.591154ms message: 'load-balancer-api-external: resolved host name a0116dc1371b74a5aafcde640e4b49e8-b79245544ff991a7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T16:48:17Z" - latency: 4.438016ms message: 'load-balancer-api-external: tcp connection to a0116dc1371b74a5aafcde640e4b49e8-b79245544ff991a7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:47:17Z" - latency: 9.589484ms message: 'load-balancer-api-external: resolved host name a0116dc1371b74a5aafcde640e4b49e8-b79245544ff991a7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T16:47:17Z" - latency: 4.042968ms message: 'load-balancer-api-external: tcp connection to a0116dc1371b74a5aafcde640e4b49e8-b79245544ff991a7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:46:17Z" - latency: 8.654202ms message: 'load-balancer-api-external: resolved host name a0116dc1371b74a5aafcde640e4b49e8-b79245544ff991a7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T16:46:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T16:20:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-92-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-92.ec2.internal uid: b775a594-5af0-4e97-9893-cd679d2cca94 resourceVersion: "57089" uid: dfd07c21-0b9f-42af-abb9-75f5cad39d30 spec: sourcePod: network-check-source-685456655f-gmmnn targetEndpoint: a0116dc1371b74a5aafcde640e4b49e8-b79245544ff991a7.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-08T16:26:17Z" message: 'load-balancer-api-internal: tcp connection to a0116dc1371b74a5aafcde640e4b49e8-b79245544ff991a7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.840849ms message: 'load-balancer-api-internal: tcp connection to a0116dc1371b74a5aafcde640e4b49e8-b79245544ff991a7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:50:17Z" - latency: 8.651005ms message: 'load-balancer-api-internal: resolved host name a0116dc1371b74a5aafcde640e4b49e8-b79245544ff991a7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T16:50:17Z" - latency: 5.60963ms message: 'load-balancer-api-internal: tcp connection to a0116dc1371b74a5aafcde640e4b49e8-b79245544ff991a7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:49:17Z" - latency: 9.465131ms message: 'load-balancer-api-internal: resolved host name a0116dc1371b74a5aafcde640e4b49e8-b79245544ff991a7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T16:49:17Z" - latency: 4.459245ms message: 'load-balancer-api-internal: tcp connection to a0116dc1371b74a5aafcde640e4b49e8-b79245544ff991a7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:48:17Z" - latency: 8.508721ms message: 'load-balancer-api-internal: resolved host name a0116dc1371b74a5aafcde640e4b49e8-b79245544ff991a7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T16:48:17Z" - latency: 4.439399ms message: 'load-balancer-api-internal: tcp connection to a0116dc1371b74a5aafcde640e4b49e8-b79245544ff991a7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:47:17Z" - latency: 9.522752ms message: 'load-balancer-api-internal: resolved host name a0116dc1371b74a5aafcde640e4b49e8-b79245544ff991a7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T16:47:17Z" - latency: 4.028386ms message: 'load-balancer-api-internal: tcp connection to a0116dc1371b74a5aafcde640e4b49e8-b79245544ff991a7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:46:17Z" - latency: 8.546896ms message: 'load-balancer-api-internal: resolved host name a0116dc1371b74a5aafcde640e4b49e8-b79245544ff991a7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T16:46:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T16:20:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-92-to-network-check-target-ip-10-0-128-92 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-92.ec2.internal uid: b775a594-5af0-4e97-9893-cd679d2cca94 resourceVersion: "55358" uid: fe5d6149-0ffe-4d64-9ecd-521577dfbce5 spec: sourcePod: network-check-source-685456655f-gmmnn targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-08T16:27:17Z" message: 'network-check-target-ip-10-0-128-92: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.113061ms message: 'network-check-target-ip-10-0-128-92: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:48:17Z" - latency: 1.095361ms message: 'network-check-target-ip-10-0-128-92: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:47:17Z" - latency: 1.028537ms message: 'network-check-target-ip-10-0-128-92: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:46:17Z" - latency: 1.369053ms message: 'network-check-target-ip-10-0-128-92: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:45:17Z" - latency: 856.801µs message: 'network-check-target-ip-10-0-128-92: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:44:17Z" - latency: 1.103841ms message: 'network-check-target-ip-10-0-128-92: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:43:17Z" - latency: 780.199µs message: 'network-check-target-ip-10-0-128-92: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:42:17Z" - latency: 1.465317ms message: 'network-check-target-ip-10-0-128-92: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:41:17Z" - latency: 1.081406ms message: 'network-check-target-ip-10-0-128-92: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:40:17Z" - latency: 1.150475ms message: 'network-check-target-ip-10-0-128-92: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:39:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T16:20:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-92-to-network-check-target-ip-10-0-135-163 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-92.ec2.internal uid: b775a594-5af0-4e97-9893-cd679d2cca94 resourceVersion: "55359" uid: 4236000b-640c-45de-bf89-64e0f7e5d6fa spec: sourcePod: network-check-source-685456655f-gmmnn targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-08T16:27:17Z" message: 'network-check-target-ip-10-0-135-163: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.113237ms message: 'network-check-target-ip-10-0-135-163: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:48:17Z" - latency: 2.099845ms message: 'network-check-target-ip-10-0-135-163: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:47:17Z" - latency: 1.968568ms message: 'network-check-target-ip-10-0-135-163: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:46:17Z" - latency: 1.954574ms message: 'network-check-target-ip-10-0-135-163: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:45:17Z" - latency: 2.614288ms message: 'network-check-target-ip-10-0-135-163: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:44:17Z" - latency: 2.196732ms message: 'network-check-target-ip-10-0-135-163: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:43:17Z" - latency: 2.007127ms message: 'network-check-target-ip-10-0-135-163: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:42:17Z" - latency: 2.301876ms message: 'network-check-target-ip-10-0-135-163: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:41:17Z" - latency: 2.057375ms message: 'network-check-target-ip-10-0-135-163: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:40:17Z" - latency: 2.081961ms message: 'network-check-target-ip-10-0-135-163: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:39:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T16:20:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-92-to-network-check-target-ip-10-0-139-234 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-92.ec2.internal uid: b775a594-5af0-4e97-9893-cd679d2cca94 resourceVersion: "55360" uid: a66737a5-f76d-4935-b8a8-4e1f284c8d79 spec: sourcePod: network-check-source-685456655f-gmmnn targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-08T16:27:17Z" message: 'network-check-target-ip-10-0-139-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.256991ms message: 'network-check-target-ip-10-0-139-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:48:17Z" - latency: 2.305316ms message: 'network-check-target-ip-10-0-139-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:47:17Z" - latency: 2.099949ms message: 'network-check-target-ip-10-0-139-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:46:17Z" - latency: 2.179344ms message: 'network-check-target-ip-10-0-139-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:45:17Z" - latency: 2.305738ms message: 'network-check-target-ip-10-0-139-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:44:17Z" - latency: 2.127884ms message: 'network-check-target-ip-10-0-139-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:43:17Z" - latency: 2.109592ms message: 'network-check-target-ip-10-0-139-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:42:17Z" - latency: 2.203413ms message: 'network-check-target-ip-10-0-139-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:41:17Z" - latency: 2.390725ms message: 'network-check-target-ip-10-0-139-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:40:17Z" - latency: 2.530991ms message: 'network-check-target-ip-10-0-139-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:39:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T16:20:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-92-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-92.ec2.internal uid: b775a594-5af0-4e97-9893-cd679d2cca94 resourceVersion: "57088" uid: 939ecb0b-e46e-4084-a7ff-b239ebe0ec12 spec: sourcePod: network-check-source-685456655f-gmmnn targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-08T16:26:17Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.002151ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:50:17Z" - latency: 1.826295ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T16:50:17Z" - latency: 871.068µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:49:17Z" - latency: 2.228769ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T16:49:17Z" - latency: 1.322586ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:48:17Z" - latency: 2.025005ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T16:48:17Z" - latency: 1.000721ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:47:17Z" - latency: 2.435598ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T16:47:17Z" - latency: 806.266µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T16:46:17Z" - latency: 1.994072ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T16:46:17Z" kind: List metadata: resourceVersion: ""