apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T10:47:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-230-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-230.ec2.internal uid: 4e5c5bc7-6753-4a2c-87ad-a678739a5f44 resourceVersion: "41912" uid: 90872374-d949-473f-8f0d-7359264bb7b9 spec: sourcePod: network-check-source-6f78d59f99-w7wqz targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T10:54:56Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.430205ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:29:56Z" - latency: 922.141µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:28:56Z" - latency: 1.189006ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:27:56Z" - latency: 1.139754ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:26:56Z" - latency: 1.107412ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:25:56Z" - latency: 1.164628ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:24:56Z" - latency: 1.194091ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:23:56Z" - latency: 1.126351ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:22:56Z" - latency: 1.508692ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:21:56Z" - latency: 910.048µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:20:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T10:47:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-230-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-230.ec2.internal uid: 4e5c5bc7-6753-4a2c-87ad-a678739a5f44 resourceVersion: "50969" uid: 46343864-2c77-4f9b-b5bc-c3d84a076a15 spec: sourcePod: network-check-source-6f78d59f99-w7wqz targetEndpoint: a65ce49a39b3f4de082acfc8a7572d63-bef556b44c741830.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T10:53:56Z" message: 'load-balancer-api-external: tcp connection to a65ce49a39b3f4de082acfc8a7572d63-bef556b44c741830.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 17.851165ms message: 'load-balancer-api-external: tcp connection to a65ce49a39b3f4de082acfc8a7572d63-bef556b44c741830.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:35:56Z" - latency: 7.719218ms message: 'load-balancer-api-external: resolved host name a65ce49a39b3f4de082acfc8a7572d63-bef556b44c741830.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T11:35:56Z" - latency: 15.36085ms message: 'load-balancer-api-external: tcp connection to a65ce49a39b3f4de082acfc8a7572d63-bef556b44c741830.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:34:56Z" - latency: 8.563947ms message: 'load-balancer-api-external: resolved host name a65ce49a39b3f4de082acfc8a7572d63-bef556b44c741830.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T11:34:56Z" - latency: 14.865836ms message: 'load-balancer-api-external: tcp connection to a65ce49a39b3f4de082acfc8a7572d63-bef556b44c741830.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:33:56Z" - latency: 10.357199ms message: 'load-balancer-api-external: resolved host name a65ce49a39b3f4de082acfc8a7572d63-bef556b44c741830.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T11:33:56Z" - latency: 15.86591ms message: 'load-balancer-api-external: tcp connection to a65ce49a39b3f4de082acfc8a7572d63-bef556b44c741830.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:32:56Z" - latency: 8.639665ms message: 'load-balancer-api-external: resolved host name a65ce49a39b3f4de082acfc8a7572d63-bef556b44c741830.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T11:32:56Z" - latency: 18.851541ms message: 'load-balancer-api-external: tcp connection to a65ce49a39b3f4de082acfc8a7572d63-bef556b44c741830.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:31:56Z" - latency: 11.437154ms message: 'load-balancer-api-external: resolved host name a65ce49a39b3f4de082acfc8a7572d63-bef556b44c741830.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T11:31:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T10:47:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-230-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-230.ec2.internal uid: 4e5c5bc7-6753-4a2c-87ad-a678739a5f44 resourceVersion: "50968" uid: e34955fe-5351-45f4-a342-f09bfcfd43e7 spec: sourcePod: network-check-source-6f78d59f99-w7wqz targetEndpoint: a65ce49a39b3f4de082acfc8a7572d63-bef556b44c741830.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T10:53:56Z" message: 'load-balancer-api-internal: tcp connection to a65ce49a39b3f4de082acfc8a7572d63-bef556b44c741830.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 15.854217ms message: 'load-balancer-api-internal: tcp connection to a65ce49a39b3f4de082acfc8a7572d63-bef556b44c741830.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:35:56Z" - latency: 7.783913ms message: 'load-balancer-api-internal: resolved host name a65ce49a39b3f4de082acfc8a7572d63-bef556b44c741830.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T11:35:56Z" - latency: 15.398275ms message: 'load-balancer-api-internal: tcp connection to a65ce49a39b3f4de082acfc8a7572d63-bef556b44c741830.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:34:56Z" - latency: 8.536472ms message: 'load-balancer-api-internal: resolved host name a65ce49a39b3f4de082acfc8a7572d63-bef556b44c741830.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T11:34:56Z" - latency: 18.591242ms message: 'load-balancer-api-internal: tcp connection to a65ce49a39b3f4de082acfc8a7572d63-bef556b44c741830.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:33:56Z" - latency: 10.461099ms message: 'load-balancer-api-internal: resolved host name a65ce49a39b3f4de082acfc8a7572d63-bef556b44c741830.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T11:33:56Z" - latency: 20.300498ms message: 'load-balancer-api-internal: tcp connection to a65ce49a39b3f4de082acfc8a7572d63-bef556b44c741830.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:32:56Z" - latency: 8.571872ms message: 'load-balancer-api-internal: resolved host name a65ce49a39b3f4de082acfc8a7572d63-bef556b44c741830.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T11:32:56Z" - latency: 15.863384ms message: 'load-balancer-api-internal: tcp connection to a65ce49a39b3f4de082acfc8a7572d63-bef556b44c741830.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:31:56Z" - latency: 11.517806ms message: 'load-balancer-api-internal: resolved host name a65ce49a39b3f4de082acfc8a7572d63-bef556b44c741830.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T11:31:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T10:47:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-230-to-network-check-target-ip-10-0-132-202 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-230.ec2.internal uid: 4e5c5bc7-6753-4a2c-87ad-a678739a5f44 resourceVersion: "41909" uid: 3a0dd2ad-4cf7-48b1-b0eb-7e06e599652e spec: sourcePod: network-check-source-6f78d59f99-w7wqz targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T10:54:56Z" message: 'network-check-target-ip-10-0-132-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.085322ms message: 'network-check-target-ip-10-0-132-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:29:56Z" - latency: 1.889365ms message: 'network-check-target-ip-10-0-132-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:28:56Z" - latency: 2.008762ms message: 'network-check-target-ip-10-0-132-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:27:56Z" - latency: 2.017939ms message: 'network-check-target-ip-10-0-132-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:26:56Z" - latency: 1.535578ms message: 'network-check-target-ip-10-0-132-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:25:56Z" - latency: 2.159398ms message: 'network-check-target-ip-10-0-132-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:24:56Z" - latency: 2.032115ms message: 'network-check-target-ip-10-0-132-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:23:56Z" - latency: 2.05452ms message: 'network-check-target-ip-10-0-132-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:22:56Z" - latency: 2.636634ms message: 'network-check-target-ip-10-0-132-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:21:56Z" - latency: 1.768478ms message: 'network-check-target-ip-10-0-132-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:20:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T10:47:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-230-to-network-check-target-ip-10-0-137-242 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-230.ec2.internal uid: 4e5c5bc7-6753-4a2c-87ad-a678739a5f44 resourceVersion: "41911" uid: 0690f04b-d705-40fa-9a03-4e2b883dad41 spec: sourcePod: network-check-source-6f78d59f99-w7wqz targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T10:54:56Z" message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.273366ms message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:29:56Z" - latency: 2.307149ms message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:28:56Z" - latency: 2.298215ms message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:27:56Z" - latency: 2.361341ms message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:26:56Z" - latency: 2.163743ms message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:25:56Z" - latency: 2.736422ms message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:24:56Z" - latency: 2.409249ms message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:23:56Z" - latency: 2.102791ms message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:22:56Z" - latency: 2.349225ms message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:21:56Z" - latency: 2.448369ms message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:20:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T10:47:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-230-to-network-check-target-ip-10-0-140-230 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-230.ec2.internal uid: 4e5c5bc7-6753-4a2c-87ad-a678739a5f44 resourceVersion: "41908" uid: 59089966-ff92-4810-8774-d9f27cc7a074 spec: sourcePod: network-check-source-6f78d59f99-w7wqz targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T10:54:56Z" message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.684598ms message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:29:56Z" - latency: 830.762µs message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:28:56Z" - latency: 995.321µs message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:27:56Z" - latency: 1.728762ms message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:26:56Z" - latency: 1.562106ms message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:25:56Z" - latency: 1.901475ms message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:24:56Z" - latency: 941.344µs message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:23:56Z" - latency: 940.702µs message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:22:56Z" - latency: 1.4652ms message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:21:56Z" - latency: 851.575µs message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:20:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T10:47:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-230-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-230.ec2.internal uid: 4e5c5bc7-6753-4a2c-87ad-a678739a5f44 resourceVersion: "50967" uid: e69d88eb-b632-4c91-b5fb-e6b20b67e88d spec: sourcePod: network-check-source-6f78d59f99-w7wqz targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T10:53:56Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.045178ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:35:56Z" - latency: 2.585881ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T11:35:56Z" - latency: 866.514µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:34:56Z" - latency: 2.410425ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T11:34:56Z" - latency: 933.071µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:33:56Z" - latency: 2.94863ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T11:33:56Z" - latency: 835.379µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:32:56Z" - latency: 1.87226ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T11:32:56Z" - latency: 1.081275ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T11:31:56Z" - latency: 2.405888ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T11:31:56Z" kind: List metadata: resourceVersion: ""