apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T20:32:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-101-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-101.ec2.internal uid: 946d97d9-9ffb-496f-a955-3714c8d6b575 resourceVersion: "43546" uid: 749f527a-ec44-4159-8752-0c688839dfcc spec: sourcePod: network-check-source-8894fc9bd-ps9ss targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-16T20:39:12Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.097265ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:00:12Z" - latency: 1.368185ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:59:12Z" - latency: 1.253397ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:58:12Z" - latency: 1.334964ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:57:12Z" - latency: 933.062µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:56:12Z" - latency: 970.884µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:55:12Z" - latency: 1.739689ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:54:12Z" - latency: 1.155362ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:53:12Z" - latency: 1.118063ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:52:12Z" - latency: 1.224367ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:51:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T20:32:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-101-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-101.ec2.internal uid: 946d97d9-9ffb-496f-a955-3714c8d6b575 resourceVersion: "45886" uid: 0ecac89a-d672-44e2-b299-186bb607700c spec: sourcePod: network-check-source-8894fc9bd-ps9ss targetEndpoint: aab4bcb3e98f845cf8500dea467478a4-b79cbe388b62743d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T20:38:12Z" message: 'load-balancer-api-external: tcp connection to aab4bcb3e98f845cf8500dea467478a4-b79cbe388b62743d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.176862ms message: 'load-balancer-api-external: tcp connection to aab4bcb3e98f845cf8500dea467478a4-b79cbe388b62743d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:02:12Z" - latency: 6.912797ms message: 'load-balancer-api-external: resolved host name aab4bcb3e98f845cf8500dea467478a4-b79cbe388b62743d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T21:02:12Z" - latency: 3.583221ms message: 'load-balancer-api-external: tcp connection to aab4bcb3e98f845cf8500dea467478a4-b79cbe388b62743d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:01:12Z" - latency: 6.377856ms message: 'load-balancer-api-external: resolved host name aab4bcb3e98f845cf8500dea467478a4-b79cbe388b62743d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T21:01:12Z" - latency: 3.959728ms message: 'load-balancer-api-external: tcp connection to aab4bcb3e98f845cf8500dea467478a4-b79cbe388b62743d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:00:12Z" - latency: 7.396104ms message: 'load-balancer-api-external: resolved host name aab4bcb3e98f845cf8500dea467478a4-b79cbe388b62743d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T21:00:12Z" - latency: 4.368338ms message: 'load-balancer-api-external: tcp connection to aab4bcb3e98f845cf8500dea467478a4-b79cbe388b62743d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:59:12Z" - latency: 6.480261ms message: 'load-balancer-api-external: resolved host name aab4bcb3e98f845cf8500dea467478a4-b79cbe388b62743d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T20:59:12Z" - latency: 5.049894ms message: 'load-balancer-api-external: tcp connection to aab4bcb3e98f845cf8500dea467478a4-b79cbe388b62743d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:58:12Z" - latency: 7.580814ms message: 'load-balancer-api-external: resolved host name aab4bcb3e98f845cf8500dea467478a4-b79cbe388b62743d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T20:58:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T20:32:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-101-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-101.ec2.internal uid: 946d97d9-9ffb-496f-a955-3714c8d6b575 resourceVersion: "45885" uid: d925aed0-cd1e-437b-af6e-76b330f0dfa0 spec: sourcePod: network-check-source-8894fc9bd-ps9ss targetEndpoint: aab4bcb3e98f845cf8500dea467478a4-b79cbe388b62743d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T20:38:12Z" message: 'load-balancer-api-internal: tcp connection to aab4bcb3e98f845cf8500dea467478a4-b79cbe388b62743d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.782944ms message: 'load-balancer-api-internal: tcp connection to aab4bcb3e98f845cf8500dea467478a4-b79cbe388b62743d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:02:12Z" - latency: 6.825086ms message: 'load-balancer-api-internal: resolved host name aab4bcb3e98f845cf8500dea467478a4-b79cbe388b62743d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T21:02:12Z" - latency: 3.294479ms message: 'load-balancer-api-internal: tcp connection to aab4bcb3e98f845cf8500dea467478a4-b79cbe388b62743d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:01:12Z" - latency: 6.481161ms message: 'load-balancer-api-internal: resolved host name aab4bcb3e98f845cf8500dea467478a4-b79cbe388b62743d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T21:01:12Z" - latency: 4.176886ms message: 'load-balancer-api-internal: tcp connection to aab4bcb3e98f845cf8500dea467478a4-b79cbe388b62743d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:00:12Z" - latency: 7.377729ms message: 'load-balancer-api-internal: resolved host name aab4bcb3e98f845cf8500dea467478a4-b79cbe388b62743d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T21:00:12Z" - latency: 4.5985ms message: 'load-balancer-api-internal: tcp connection to aab4bcb3e98f845cf8500dea467478a4-b79cbe388b62743d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:59:12Z" - latency: 6.4628ms message: 'load-balancer-api-internal: resolved host name aab4bcb3e98f845cf8500dea467478a4-b79cbe388b62743d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T20:59:12Z" - latency: 5.043008ms message: 'load-balancer-api-internal: tcp connection to aab4bcb3e98f845cf8500dea467478a4-b79cbe388b62743d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:58:12Z" - latency: 7.422556ms message: 'load-balancer-api-internal: resolved host name aab4bcb3e98f845cf8500dea467478a4-b79cbe388b62743d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T20:58:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T20:32:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-101-to-network-check-target-ip-10-0-132-101 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-101.ec2.internal uid: 946d97d9-9ffb-496f-a955-3714c8d6b575 resourceVersion: "43543" uid: da4a8afb-b10d-4a92-959d-b0397df2faa9 spec: sourcePod: network-check-source-8894fc9bd-ps9ss targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-16T20:39:12Z" message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 907.438µs message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:00:12Z" - latency: 959.854µs message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:59:12Z" - latency: 863.059µs message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:58:12Z" - latency: 1.529205ms message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:57:12Z" - latency: 932.135µs message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:56:12Z" - latency: 902.328µs message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:55:12Z" - latency: 1.103331ms message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:54:12Z" - latency: 912.328µs message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:53:12Z" - latency: 1.073833ms message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:52:12Z" - latency: 889.624µs message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:51:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T20:32:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-101-to-network-check-target-ip-10-0-137-53 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-101.ec2.internal uid: 946d97d9-9ffb-496f-a955-3714c8d6b575 resourceVersion: "43544" uid: f0465a69-64db-45dd-9ef8-91d720ba21df spec: sourcePod: network-check-source-8894fc9bd-ps9ss targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T20:39:12Z" message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.122334ms message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:00:12Z" - latency: 1.855546ms message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:59:12Z" - latency: 2.103111ms message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:58:12Z" - latency: 2.737806ms message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:57:12Z" - latency: 2.213863ms message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:56:12Z" - latency: 2.182423ms message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:55:12Z" - latency: 2.204234ms message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:54:12Z" - latency: 2.142633ms message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:53:12Z" - latency: 2.3161ms message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:52:12Z" - latency: 2.326276ms message: 'network-check-target-ip-10-0-137-53: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:51:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T20:32:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-101-to-network-check-target-ip-10-0-139-150 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-101.ec2.internal uid: 946d97d9-9ffb-496f-a955-3714c8d6b575 resourceVersion: "43545" uid: d1d70df7-c4fb-4d3b-b929-98a0239a275f spec: sourcePod: network-check-source-8894fc9bd-ps9ss targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T20:39:12Z" message: 'network-check-target-ip-10-0-139-150: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.822445ms message: 'network-check-target-ip-10-0-139-150: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:00:12Z" - latency: 1.832749ms message: 'network-check-target-ip-10-0-139-150: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:59:12Z" - latency: 1.939963ms message: 'network-check-target-ip-10-0-139-150: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:58:12Z" - latency: 1.990053ms message: 'network-check-target-ip-10-0-139-150: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:57:12Z" - latency: 1.853823ms message: 'network-check-target-ip-10-0-139-150: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:56:12Z" - latency: 1.657449ms message: 'network-check-target-ip-10-0-139-150: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:55:12Z" - latency: 1.816499ms message: 'network-check-target-ip-10-0-139-150: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:54:12Z" - latency: 1.811179ms message: 'network-check-target-ip-10-0-139-150: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:53:12Z" - latency: 2.023607ms message: 'network-check-target-ip-10-0-139-150: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:52:12Z" - latency: 2.04349ms message: 'network-check-target-ip-10-0-139-150: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:51:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T20:32:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-101-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-101.ec2.internal uid: 946d97d9-9ffb-496f-a955-3714c8d6b575 resourceVersion: "45884" uid: be8407ee-fadf-4c31-8e85-6e1478f54ecd spec: sourcePod: network-check-source-8894fc9bd-ps9ss targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-16T20:38:12Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.027566ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:02:12Z" - latency: 1.845669ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T21:02:12Z" - latency: 1.040276ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:01:12Z" - latency: 1.757203ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T21:01:12Z" - latency: 784.581µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:00:12Z" - latency: 1.965048ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T21:00:12Z" - latency: 809.597µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:59:12Z" - latency: 1.84245ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T20:59:12Z" - latency: 816.162µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:58:12Z" - latency: 1.717513ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T20:58:12Z" kind: List metadata: resourceVersion: ""