apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T19:25:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-199-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-199.ec2.internal uid: 5b64539c-af65-440f-9ba9-2773d3b6a6e2 resourceVersion: "22534" uid: e7ec7e7e-76bd-4c86-a7ee-9f15e0bfdb6f spec: sourcePod: network-check-source-56499946bc-vrfs9 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-01T19:32:31Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.082525ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:46:31Z" - latency: 1.072189ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:45:31Z" - latency: 1.137846ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:44:31Z" - latency: 940.066µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:43:31Z" - latency: 1.330349ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:42:31Z" - latency: 1.131014ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:41:31Z" - latency: 1.258116ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:40:31Z" - latency: 1.289124ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:39:31Z" - latency: 1.113106ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:38:31Z" - latency: 1.179367ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:37:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T19:25:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-199-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-199.ec2.internal uid: 5b64539c-af65-440f-9ba9-2773d3b6a6e2 resourceVersion: "21113" uid: 62267888-e77e-4269-88b5-1ba55f0c72af spec: sourcePod: network-check-source-56499946bc-vrfs9 targetEndpoint: a0cc7514a15124f99b8e3af18852f626-4639d2201c37f4d0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-01T19:31:31Z" message: 'load-balancer-api-external: tcp connection to a0cc7514a15124f99b8e3af18852f626-4639d2201c37f4d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.552382ms message: 'load-balancer-api-external: tcp connection to a0cc7514a15124f99b8e3af18852f626-4639d2201c37f4d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:43:31Z" - latency: 8.059756ms message: 'load-balancer-api-external: resolved host name a0cc7514a15124f99b8e3af18852f626-4639d2201c37f4d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T19:43:31Z" - latency: 5.435233ms message: 'load-balancer-api-external: tcp connection to a0cc7514a15124f99b8e3af18852f626-4639d2201c37f4d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:42:31Z" - latency: 7.197338ms message: 'load-balancer-api-external: resolved host name a0cc7514a15124f99b8e3af18852f626-4639d2201c37f4d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T19:42:31Z" - latency: 4.941439ms message: 'load-balancer-api-external: tcp connection to a0cc7514a15124f99b8e3af18852f626-4639d2201c37f4d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:41:31Z" - latency: 7.384358ms message: 'load-balancer-api-external: resolved host name a0cc7514a15124f99b8e3af18852f626-4639d2201c37f4d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T19:41:31Z" - latency: 4.371111ms message: 'load-balancer-api-external: tcp connection to a0cc7514a15124f99b8e3af18852f626-4639d2201c37f4d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:40:31Z" - latency: 7.351228ms message: 'load-balancer-api-external: resolved host name a0cc7514a15124f99b8e3af18852f626-4639d2201c37f4d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T19:40:31Z" - latency: 4.804751ms message: 'load-balancer-api-external: tcp connection to a0cc7514a15124f99b8e3af18852f626-4639d2201c37f4d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:39:31Z" - latency: 7.071873ms message: 'load-balancer-api-external: resolved host name a0cc7514a15124f99b8e3af18852f626-4639d2201c37f4d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T19:39:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T19:25:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-199-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-199.ec2.internal uid: 5b64539c-af65-440f-9ba9-2773d3b6a6e2 resourceVersion: "21114" uid: abd4ac73-6644-42b3-9f86-14cb4a4d6c08 spec: sourcePod: network-check-source-56499946bc-vrfs9 targetEndpoint: a0cc7514a15124f99b8e3af18852f626-4639d2201c37f4d0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-01T19:31:31Z" message: 'load-balancer-api-internal: tcp connection to a0cc7514a15124f99b8e3af18852f626-4639d2201c37f4d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.589489ms message: 'load-balancer-api-internal: tcp connection to a0cc7514a15124f99b8e3af18852f626-4639d2201c37f4d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:43:31Z" - latency: 8.212856ms message: 'load-balancer-api-internal: resolved host name a0cc7514a15124f99b8e3af18852f626-4639d2201c37f4d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T19:43:31Z" - latency: 5.465202ms message: 'load-balancer-api-internal: tcp connection to a0cc7514a15124f99b8e3af18852f626-4639d2201c37f4d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:42:31Z" - latency: 7.142062ms message: 'load-balancer-api-internal: resolved host name a0cc7514a15124f99b8e3af18852f626-4639d2201c37f4d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T19:42:31Z" - latency: 5.278981ms message: 'load-balancer-api-internal: tcp connection to a0cc7514a15124f99b8e3af18852f626-4639d2201c37f4d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:41:31Z" - latency: 7.352797ms message: 'load-balancer-api-internal: resolved host name a0cc7514a15124f99b8e3af18852f626-4639d2201c37f4d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T19:41:31Z" - latency: 5.146629ms message: 'load-balancer-api-internal: tcp connection to a0cc7514a15124f99b8e3af18852f626-4639d2201c37f4d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:40:31Z" - latency: 7.300053ms message: 'load-balancer-api-internal: resolved host name a0cc7514a15124f99b8e3af18852f626-4639d2201c37f4d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T19:40:31Z" - latency: 4.795666ms message: 'load-balancer-api-internal: tcp connection to a0cc7514a15124f99b8e3af18852f626-4639d2201c37f4d0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:39:31Z" - latency: 7.124848ms message: 'load-balancer-api-internal: resolved host name a0cc7514a15124f99b8e3af18852f626-4639d2201c37f4d0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T19:39:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T19:25:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-199-to-network-check-target-ip-10-0-132-199 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-199.ec2.internal uid: 5b64539c-af65-440f-9ba9-2773d3b6a6e2 resourceVersion: "22531" uid: 7d9593cb-72a9-4016-a787-05de0e5ea062 spec: sourcePod: network-check-source-56499946bc-vrfs9 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-01T19:32:31Z" message: 'network-check-target-ip-10-0-132-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 990.476µs message: 'network-check-target-ip-10-0-132-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:46:31Z" - latency: 883.791µs message: 'network-check-target-ip-10-0-132-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:45:31Z" - latency: 1.389778ms message: 'network-check-target-ip-10-0-132-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:44:31Z" - latency: 955.265µs message: 'network-check-target-ip-10-0-132-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:43:31Z" - latency: 1.001529ms message: 'network-check-target-ip-10-0-132-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:42:31Z" - latency: 815.241µs message: 'network-check-target-ip-10-0-132-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:41:31Z" - latency: 866.931µs message: 'network-check-target-ip-10-0-132-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:40:31Z" - latency: 833.466µs message: 'network-check-target-ip-10-0-132-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:39:31Z" - latency: 1.593428ms message: 'network-check-target-ip-10-0-132-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:38:31Z" - latency: 1.251219ms message: 'network-check-target-ip-10-0-132-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:37:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T19:25:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-199-to-network-check-target-ip-10-0-137-164 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-199.ec2.internal uid: 5b64539c-af65-440f-9ba9-2773d3b6a6e2 resourceVersion: "22533" uid: edc1a477-9e68-4a0c-af2b-8a4953eafe55 spec: sourcePod: network-check-source-56499946bc-vrfs9 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-01T19:32:31Z" message: 'network-check-target-ip-10-0-137-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.078842ms message: 'network-check-target-ip-10-0-137-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:46:31Z" - latency: 2.243138ms message: 'network-check-target-ip-10-0-137-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:45:31Z" - latency: 2.045817ms message: 'network-check-target-ip-10-0-137-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:44:31Z" - latency: 1.948855ms message: 'network-check-target-ip-10-0-137-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:43:31Z" - latency: 1.839497ms message: 'network-check-target-ip-10-0-137-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:42:31Z" - latency: 2.177395ms message: 'network-check-target-ip-10-0-137-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:41:31Z" - latency: 2.101328ms message: 'network-check-target-ip-10-0-137-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:40:31Z" - latency: 2.331949ms message: 'network-check-target-ip-10-0-137-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:39:31Z" - latency: 2.195737ms message: 'network-check-target-ip-10-0-137-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:38:31Z" - latency: 2.155789ms message: 'network-check-target-ip-10-0-137-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:37:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T19:25:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-199-to-network-check-target-ip-10-0-140-6 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-199.ec2.internal uid: 5b64539c-af65-440f-9ba9-2773d3b6a6e2 resourceVersion: "22532" uid: ca966900-10aa-41ee-9cd1-5b79b9c02166 spec: sourcePod: network-check-source-56499946bc-vrfs9 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-01T19:32:31Z" message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.892179ms message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:46:31Z" - latency: 2.013559ms message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:45:31Z" - latency: 2.122785ms message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:44:31Z" - latency: 2.051815ms message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:43:31Z" - latency: 2.014359ms message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:42:31Z" - latency: 1.920879ms message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:41:31Z" - latency: 1.839516ms message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:40:31Z" - latency: 1.992579ms message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:39:31Z" - latency: 1.979636ms message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:38:31Z" - latency: 1.728011ms message: 'network-check-target-ip-10-0-140-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:37:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T19:25:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-199-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-199.ec2.internal uid: 5b64539c-af65-440f-9ba9-2773d3b6a6e2 resourceVersion: "21112" uid: db34a84e-b0d8-477a-8ffc-fedf5040d376 spec: sourcePod: network-check-source-56499946bc-vrfs9 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-01T19:31:31Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.122208ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:43:31Z" - latency: 1.738283ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T19:43:31Z" - latency: 979.082µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:42:31Z" - latency: 1.873405ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T19:42:31Z" - latency: 908.563µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:41:31Z" - latency: 1.973412ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T19:41:31Z" - latency: 860.594µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:40:31Z" - latency: 1.867098ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T19:40:31Z" - latency: 870.782µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T19:39:31Z" - latency: 1.747503ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T19:39:31Z" kind: List metadata: resourceVersion: ""