apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T08:18:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-8-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-8.ec2.internal uid: 4c68f437-68cb-401a-a97a-1761deb7a960 resourceVersion: "26695" uid: 3ecf4180-fa6b-4005-bd2d-054685bd2a5e spec: sourcePod: network-check-source-8894fc9bd-cqjnh targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-23T08:25:51Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 947.65µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T09:00:51Z" - latency: 860.362µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:59:51Z" - latency: 897.623µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:58:51Z" - latency: 949.551µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:57:51Z" - latency: 969.655µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:56:51Z" - latency: 874.355µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:55:51Z" - latency: 941.419µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:54:51Z" - latency: 811.628µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:53:51Z" - latency: 939.328µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:52:51Z" - latency: 985.003µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:51:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T08:18:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-8-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-8.ec2.internal uid: 4c68f437-68cb-401a-a97a-1761deb7a960 resourceVersion: "26697" uid: 595af082-bed9-4636-a731-7a9966d79221 spec: sourcePod: network-check-source-8894fc9bd-cqjnh targetEndpoint: aa7784b6b921a46c5adc7d17f6027692-d8cb3280c82ca4fb.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-23T08:24:51Z" message: 'load-balancer-api-external: tcp connection to aa7784b6b921a46c5adc7d17f6027692-d8cb3280c82ca4fb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.664691ms message: 'load-balancer-api-external: tcp connection to aa7784b6b921a46c5adc7d17f6027692-d8cb3280c82ca4fb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T09:00:51Z" - latency: 18.602241ms message: 'load-balancer-api-external: resolved host name aa7784b6b921a46c5adc7d17f6027692-d8cb3280c82ca4fb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T09:00:51Z" - latency: 4.229729ms message: 'load-balancer-api-external: tcp connection to aa7784b6b921a46c5adc7d17f6027692-d8cb3280c82ca4fb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:59:51Z" - latency: 8.835792ms message: 'load-balancer-api-external: resolved host name aa7784b6b921a46c5adc7d17f6027692-d8cb3280c82ca4fb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T08:59:51Z" - latency: 3.901269ms message: 'load-balancer-api-external: tcp connection to aa7784b6b921a46c5adc7d17f6027692-d8cb3280c82ca4fb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:58:51Z" - latency: 9.232181ms message: 'load-balancer-api-external: resolved host name aa7784b6b921a46c5adc7d17f6027692-d8cb3280c82ca4fb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T08:58:51Z" - latency: 4.631312ms message: 'load-balancer-api-external: tcp connection to aa7784b6b921a46c5adc7d17f6027692-d8cb3280c82ca4fb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:57:51Z" - latency: 7.372248ms message: 'load-balancer-api-external: resolved host name aa7784b6b921a46c5adc7d17f6027692-d8cb3280c82ca4fb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T08:57:51Z" - latency: 4.55553ms message: 'load-balancer-api-external: tcp connection to aa7784b6b921a46c5adc7d17f6027692-d8cb3280c82ca4fb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:56:51Z" - latency: 8.460258ms message: 'load-balancer-api-external: resolved host name aa7784b6b921a46c5adc7d17f6027692-d8cb3280c82ca4fb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T08:56:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T08:18:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-8-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-8.ec2.internal uid: 4c68f437-68cb-401a-a97a-1761deb7a960 resourceVersion: "26696" uid: 61c9e550-40c0-4e69-99b8-cdafe499202a spec: sourcePod: network-check-source-8894fc9bd-cqjnh targetEndpoint: aa7784b6b921a46c5adc7d17f6027692-d8cb3280c82ca4fb.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-23T08:24:51Z" message: 'load-balancer-api-internal: tcp connection to aa7784b6b921a46c5adc7d17f6027692-d8cb3280c82ca4fb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.678084ms message: 'load-balancer-api-internal: tcp connection to aa7784b6b921a46c5adc7d17f6027692-d8cb3280c82ca4fb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T09:00:51Z" - latency: 18.644669ms message: 'load-balancer-api-internal: resolved host name aa7784b6b921a46c5adc7d17f6027692-d8cb3280c82ca4fb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T09:00:51Z" - latency: 4.255287ms message: 'load-balancer-api-internal: tcp connection to aa7784b6b921a46c5adc7d17f6027692-d8cb3280c82ca4fb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:59:51Z" - latency: 8.757482ms message: 'load-balancer-api-internal: resolved host name aa7784b6b921a46c5adc7d17f6027692-d8cb3280c82ca4fb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T08:59:51Z" - latency: 4.755384ms message: 'load-balancer-api-internal: tcp connection to aa7784b6b921a46c5adc7d17f6027692-d8cb3280c82ca4fb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:58:51Z" - latency: 9.312286ms message: 'load-balancer-api-internal: resolved host name aa7784b6b921a46c5adc7d17f6027692-d8cb3280c82ca4fb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T08:58:51Z" - latency: 4.660184ms message: 'load-balancer-api-internal: tcp connection to aa7784b6b921a46c5adc7d17f6027692-d8cb3280c82ca4fb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:57:51Z" - latency: 7.304517ms message: 'load-balancer-api-internal: resolved host name aa7784b6b921a46c5adc7d17f6027692-d8cb3280c82ca4fb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T08:57:51Z" - latency: 4.637807ms message: 'load-balancer-api-internal: tcp connection to aa7784b6b921a46c5adc7d17f6027692-d8cb3280c82ca4fb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:56:51Z" - latency: 8.507296ms message: 'load-balancer-api-internal: resolved host name aa7784b6b921a46c5adc7d17f6027692-d8cb3280c82ca4fb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T08:56:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T08:18:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-8-to-network-check-target-ip-10-0-129-53 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-8.ec2.internal uid: 4c68f437-68cb-401a-a97a-1761deb7a960 resourceVersion: "26692" uid: 3e95635a-4519-423d-914d-7933b1f947a9 spec: sourcePod: network-check-source-8894fc9bd-cqjnh targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-23T08:25:51Z" message: 'network-check-target-ip-10-0-129-53: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.301219ms message: 'network-check-target-ip-10-0-129-53: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T09:00:51Z" - latency: 2.118086ms message: 'network-check-target-ip-10-0-129-53: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:59:51Z" - latency: 2.331259ms message: 'network-check-target-ip-10-0-129-53: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:58:51Z" - latency: 2.287357ms message: 'network-check-target-ip-10-0-129-53: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:57:51Z" - latency: 2.137396ms message: 'network-check-target-ip-10-0-129-53: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:56:51Z" - latency: 2.27754ms message: 'network-check-target-ip-10-0-129-53: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:55:51Z" - latency: 2.221606ms message: 'network-check-target-ip-10-0-129-53: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:54:51Z" - latency: 2.234406ms message: 'network-check-target-ip-10-0-129-53: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:53:51Z" - latency: 2.30168ms message: 'network-check-target-ip-10-0-129-53: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:52:51Z" - latency: 2.139055ms message: 'network-check-target-ip-10-0-129-53: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:51:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T08:18:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-8-to-network-check-target-ip-10-0-134-8 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-8.ec2.internal uid: 4c68f437-68cb-401a-a97a-1761deb7a960 resourceVersion: "26691" uid: 13617ab2-b0df-4ea9-9a7d-1f4d0f0ab66f spec: sourcePod: network-check-source-8894fc9bd-cqjnh targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-23T08:25:51Z" message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 823.806µs message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T09:00:51Z" - latency: 756.035µs message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:59:51Z" - latency: 868.25µs message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:58:51Z" - latency: 1.113425ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:57:51Z" - latency: 1.244971ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:56:51Z" - latency: 807.911µs message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:55:51Z" - latency: 807.693µs message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:54:51Z" - latency: 1.248249ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:53:51Z" - latency: 1.17343ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:52:51Z" - latency: 738.172µs message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:51:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T08:18:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-8-to-network-check-target-ip-10-0-135-129 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-8.ec2.internal uid: 4c68f437-68cb-401a-a97a-1761deb7a960 resourceVersion: "26694" uid: 8961cf45-a78f-42e2-8956-e4b127104d97 spec: sourcePod: network-check-source-8894fc9bd-cqjnh targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-23T08:25:51Z" message: 'network-check-target-ip-10-0-135-129: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.034668ms message: 'network-check-target-ip-10-0-135-129: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T09:00:51Z" - latency: 2.042874ms message: 'network-check-target-ip-10-0-135-129: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:59:51Z" - latency: 2.014322ms message: 'network-check-target-ip-10-0-135-129: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:58:51Z" - latency: 2.17715ms message: 'network-check-target-ip-10-0-135-129: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:57:51Z" - latency: 2.01956ms message: 'network-check-target-ip-10-0-135-129: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:56:51Z" - latency: 2.121938ms message: 'network-check-target-ip-10-0-135-129: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:55:51Z" - latency: 2.155161ms message: 'network-check-target-ip-10-0-135-129: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:54:51Z" - latency: 2.109413ms message: 'network-check-target-ip-10-0-135-129: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:53:51Z" - latency: 2.177347ms message: 'network-check-target-ip-10-0-135-129: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:52:51Z" - latency: 2.046449ms message: 'network-check-target-ip-10-0-135-129: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:51:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T08:18:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-8-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-8.ec2.internal uid: 4c68f437-68cb-401a-a97a-1761deb7a960 resourceVersion: "26693" uid: 1a36259e-cf04-4d39-a003-b31f13465f3f spec: sourcePod: network-check-source-8894fc9bd-cqjnh targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-23T08:24:51Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.020527ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T09:00:51Z" - latency: 1.830733ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T09:00:51Z" - latency: 772.916µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:59:51Z" - latency: 1.494272ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T08:59:51Z" - latency: 727.599µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:58:51Z" - latency: 2.205724ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T08:58:51Z" - latency: 1.06802ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:57:51Z" - latency: 1.715122ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T08:57:51Z" - latency: 822.734µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T08:56:51Z" - latency: 1.904813ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T08:56:51Z" kind: List metadata: resourceVersion: ""