apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T19:38:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-115-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-115.ec2.internal uid: f4a9edc0-31b1-4399-ad5e-f1af99608317 resourceVersion: "159331" uid: 73eefa44-42ed-4dc1-b619-f69c4561adc1 spec: sourcePod: network-check-source-6f78d59f99-l2ccl targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T19:45:35Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.381459ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:48:35Z" - latency: 930.244µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:47:35Z" - latency: 912.308µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:46:35Z" - latency: 11.827153ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:45:35Z" - latency: 1.061525ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:44:35Z" - latency: 991.87µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:43:35Z" - latency: 864.287µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:42:35Z" - latency: 898.934µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:41:35Z" - latency: 1.104733ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:40:35Z" - latency: 1.087769ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:39:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T19:38:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-115-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-115.ec2.internal uid: f4a9edc0-31b1-4399-ad5e-f1af99608317 resourceVersion: "160839" uid: c9039e31-6190-4371-ab24-71ab4091dbf7 spec: sourcePod: network-check-source-6f78d59f99-l2ccl targetEndpoint: aaccc72ea71ef4fc48dcb8c82ae987dd-c2b27caf6a02449c.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T19:44:35Z" message: 'load-balancer-api-external: tcp connection to aaccc72ea71ef4fc48dcb8c82ae987dd-c2b27caf6a02449c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 18.131824ms message: 'load-balancer-api-external: tcp connection to aaccc72ea71ef4fc48dcb8c82ae987dd-c2b27caf6a02449c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:50:35Z" - latency: 6.60028ms message: 'load-balancer-api-external: resolved host name aaccc72ea71ef4fc48dcb8c82ae987dd-c2b27caf6a02449c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:50:35Z" - latency: 17.342626ms message: 'load-balancer-api-external: tcp connection to aaccc72ea71ef4fc48dcb8c82ae987dd-c2b27caf6a02449c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:49:35Z" - latency: 10.563762ms message: 'load-balancer-api-external: resolved host name aaccc72ea71ef4fc48dcb8c82ae987dd-c2b27caf6a02449c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:49:35Z" - latency: 16.279815ms message: 'load-balancer-api-external: tcp connection to aaccc72ea71ef4fc48dcb8c82ae987dd-c2b27caf6a02449c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:48:35Z" - latency: 7.787397ms message: 'load-balancer-api-external: resolved host name aaccc72ea71ef4fc48dcb8c82ae987dd-c2b27caf6a02449c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:48:35Z" - latency: 21.950238ms message: 'load-balancer-api-external: tcp connection to aaccc72ea71ef4fc48dcb8c82ae987dd-c2b27caf6a02449c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:47:35Z" - latency: 8.600747ms message: 'load-balancer-api-external: resolved host name aaccc72ea71ef4fc48dcb8c82ae987dd-c2b27caf6a02449c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:47:35Z" - latency: 17.431221ms message: 'load-balancer-api-external: tcp connection to aaccc72ea71ef4fc48dcb8c82ae987dd-c2b27caf6a02449c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:46:35Z" - latency: 9.251167ms message: 'load-balancer-api-external: resolved host name aaccc72ea71ef4fc48dcb8c82ae987dd-c2b27caf6a02449c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:46:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T19:38:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-115-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-115.ec2.internal uid: f4a9edc0-31b1-4399-ad5e-f1af99608317 resourceVersion: "160840" uid: 6efcde30-b5fb-4788-beeb-eff4df2b126e spec: sourcePod: network-check-source-6f78d59f99-l2ccl targetEndpoint: aaccc72ea71ef4fc48dcb8c82ae987dd-c2b27caf6a02449c.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T19:44:35Z" message: 'load-balancer-api-internal: tcp connection to aaccc72ea71ef4fc48dcb8c82ae987dd-c2b27caf6a02449c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 17.851572ms message: 'load-balancer-api-internal: tcp connection to aaccc72ea71ef4fc48dcb8c82ae987dd-c2b27caf6a02449c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:50:35Z" - latency: 6.674296ms message: 'load-balancer-api-internal: resolved host name aaccc72ea71ef4fc48dcb8c82ae987dd-c2b27caf6a02449c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:50:35Z" - latency: 17.375586ms message: 'load-balancer-api-internal: tcp connection to aaccc72ea71ef4fc48dcb8c82ae987dd-c2b27caf6a02449c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:49:35Z" - latency: 10.510852ms message: 'load-balancer-api-internal: resolved host name aaccc72ea71ef4fc48dcb8c82ae987dd-c2b27caf6a02449c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:49:35Z" - latency: 16.231529ms message: 'load-balancer-api-internal: tcp connection to aaccc72ea71ef4fc48dcb8c82ae987dd-c2b27caf6a02449c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:48:35Z" - latency: 7.825175ms message: 'load-balancer-api-internal: resolved host name aaccc72ea71ef4fc48dcb8c82ae987dd-c2b27caf6a02449c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:48:35Z" - latency: 21.778694ms message: 'load-balancer-api-internal: tcp connection to aaccc72ea71ef4fc48dcb8c82ae987dd-c2b27caf6a02449c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:47:35Z" - latency: 8.568694ms message: 'load-balancer-api-internal: resolved host name aaccc72ea71ef4fc48dcb8c82ae987dd-c2b27caf6a02449c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:47:35Z" - latency: 17.37569ms message: 'load-balancer-api-internal: tcp connection to aaccc72ea71ef4fc48dcb8c82ae987dd-c2b27caf6a02449c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:46:35Z" - latency: 9.302901ms message: 'load-balancer-api-internal: resolved host name aaccc72ea71ef4fc48dcb8c82ae987dd-c2b27caf6a02449c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:46:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T19:38:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-115-to-network-check-target-ip-10-0-132-115 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-115.ec2.internal uid: f4a9edc0-31b1-4399-ad5e-f1af99608317 resourceVersion: "159327" uid: 721845e3-b1a8-4113-874d-408f9e504a42 spec: sourcePod: network-check-source-6f78d59f99-l2ccl targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T19:45:35Z" message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.583772ms message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:48:35Z" - latency: 941.643µs message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:47:35Z" - latency: 1.126427ms message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:46:35Z" - latency: 17.330333ms message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:45:35Z" - latency: 1.415656ms message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:44:35Z" - latency: 872.324µs message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:43:35Z" - latency: 916.922µs message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:42:35Z" - latency: 826.67µs message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:41:35Z" - latency: 890.3µs message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:40:35Z" - latency: 1.276502ms message: 'network-check-target-ip-10-0-132-115: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:39:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T19:38:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-115-to-network-check-target-ip-10-0-132-4 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-115.ec2.internal uid: f4a9edc0-31b1-4399-ad5e-f1af99608317 resourceVersion: "159328" uid: 3dee88b5-fce3-491b-bb3c-ab8b11bda07d spec: sourcePod: network-check-source-6f78d59f99-l2ccl targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T19:45:35Z" message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.535686ms message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:48:35Z" - latency: 2.893306ms message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:47:35Z" - latency: 2.753512ms message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:46:35Z" - latency: 12.210856ms message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:45:35Z" - latency: 2.57658ms message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:44:35Z" - latency: 2.506171ms message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:43:35Z" - latency: 2.573822ms message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:42:35Z" - latency: 2.559962ms message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:41:35Z" - latency: 2.424352ms message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:40:35Z" - latency: 2.452286ms message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:39:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T19:38:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-115-to-network-check-target-ip-10-0-133-26 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-115.ec2.internal uid: f4a9edc0-31b1-4399-ad5e-f1af99608317 resourceVersion: "159330" uid: 420e3556-74f7-47e5-8161-196e7475c49c spec: sourcePod: network-check-source-6f78d59f99-l2ccl targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T19:45:35Z" message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.539685ms message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:48:35Z" - latency: 2.657655ms message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:47:35Z" - latency: 2.263748ms message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:46:35Z" - latency: 11.974843ms message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:45:35Z" - latency: 2.479337ms message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:44:35Z" - latency: 2.152282ms message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:43:35Z" - latency: 2.507484ms message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:42:35Z" - latency: 2.170797ms message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:41:35Z" - latency: 2.34179ms message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:40:35Z" - latency: 2.282329ms message: 'network-check-target-ip-10-0-133-26: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:39:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T19:38:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-115-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-115.ec2.internal uid: f4a9edc0-31b1-4399-ad5e-f1af99608317 resourceVersion: "160838" uid: d74c94ea-162e-4d47-9133-6c5e767b9c84 spec: sourcePod: network-check-source-6f78d59f99-l2ccl targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T19:44:35Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 888.225µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:50:35Z" - latency: 2.134571ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T20:50:35Z" - latency: 999.869µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:49:35Z" - latency: 1.653445ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T20:49:35Z" - latency: 957.927µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:48:35Z" - latency: 2.589234ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T20:48:35Z" - latency: 1.047115ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:47:35Z" - latency: 1.973132ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T20:47:35Z" - latency: 1.213209ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:46:35Z" - latency: 2.215008ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T20:46:35Z" kind: List metadata: resourceVersion: ""