apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:30:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-65-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-65.ec2.internal uid: ab5d2c5a-5ffa-4e37-8bea-c9b66b5f8dad resourceVersion: "17995" uid: 55031f6a-75e4-4d92-a32b-b13adc642b45 spec: sourcePod: network-check-source-8894fc9bd-5zhmk targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-24T21:37:05Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 931.898µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:44:05Z" - latency: 764.088µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:43:05Z" - latency: 921.799µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:42:05Z" - latency: 1.304932ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:41:05Z" - latency: 1.293349ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:40:05Z" - latency: 1.321449ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:39:05Z" - latency: 906.507µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:38:05Z" - latency: 961.448µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:37:05Z" - latency: 937.266µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:36:05Z" - latency: 881.887µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:35:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:30:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-65-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-65.ec2.internal uid: ab5d2c5a-5ffa-4e37-8bea-c9b66b5f8dad resourceVersion: "20038" uid: 7fb7317f-cfc9-495c-ad5f-8e2634177d3f spec: sourcePod: network-check-source-8894fc9bd-5zhmk targetEndpoint: abd7b3cda12c344d5850e63591494e17-eec146f821d36006.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T21:36:05Z" message: 'load-balancer-api-external: tcp connection to abd7b3cda12c344d5850e63591494e17-eec146f821d36006.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.849599ms message: 'load-balancer-api-external: tcp connection to abd7b3cda12c344d5850e63591494e17-eec146f821d36006.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:48:05Z" - latency: 8.727691ms message: 'load-balancer-api-external: resolved host name abd7b3cda12c344d5850e63591494e17-eec146f821d36006.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T21:48:05Z" - latency: 4.930386ms message: 'load-balancer-api-external: tcp connection to abd7b3cda12c344d5850e63591494e17-eec146f821d36006.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:47:05Z" - latency: 7.968119ms message: 'load-balancer-api-external: resolved host name abd7b3cda12c344d5850e63591494e17-eec146f821d36006.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T21:47:05Z" - latency: 4.287171ms message: 'load-balancer-api-external: tcp connection to abd7b3cda12c344d5850e63591494e17-eec146f821d36006.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:46:05Z" - latency: 8.717815ms message: 'load-balancer-api-external: resolved host name abd7b3cda12c344d5850e63591494e17-eec146f821d36006.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T21:46:05Z" - latency: 4.339302ms message: 'load-balancer-api-external: tcp connection to abd7b3cda12c344d5850e63591494e17-eec146f821d36006.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:45:05Z" - latency: 8.185431ms message: 'load-balancer-api-external: resolved host name abd7b3cda12c344d5850e63591494e17-eec146f821d36006.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T21:45:05Z" - latency: 4.594138ms message: 'load-balancer-api-external: tcp connection to abd7b3cda12c344d5850e63591494e17-eec146f821d36006.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:44:05Z" - latency: 8.060977ms message: 'load-balancer-api-external: resolved host name abd7b3cda12c344d5850e63591494e17-eec146f821d36006.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T21:44:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:30:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-65-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-65.ec2.internal uid: ab5d2c5a-5ffa-4e37-8bea-c9b66b5f8dad resourceVersion: "20039" uid: 84eb24bd-9a95-453e-a665-3d599e7a4d8d spec: sourcePod: network-check-source-8894fc9bd-5zhmk targetEndpoint: abd7b3cda12c344d5850e63591494e17-eec146f821d36006.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T21:36:05Z" message: 'load-balancer-api-internal: tcp connection to abd7b3cda12c344d5850e63591494e17-eec146f821d36006.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.905419ms message: 'load-balancer-api-internal: tcp connection to abd7b3cda12c344d5850e63591494e17-eec146f821d36006.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:48:05Z" - latency: 8.670298ms message: 'load-balancer-api-internal: resolved host name abd7b3cda12c344d5850e63591494e17-eec146f821d36006.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T21:48:05Z" - latency: 4.918162ms message: 'load-balancer-api-internal: tcp connection to abd7b3cda12c344d5850e63591494e17-eec146f821d36006.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:47:05Z" - latency: 8.035916ms message: 'load-balancer-api-internal: resolved host name abd7b3cda12c344d5850e63591494e17-eec146f821d36006.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T21:47:05Z" - latency: 4.550852ms message: 'load-balancer-api-internal: tcp connection to abd7b3cda12c344d5850e63591494e17-eec146f821d36006.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:46:05Z" - latency: 8.576546ms message: 'load-balancer-api-internal: resolved host name abd7b3cda12c344d5850e63591494e17-eec146f821d36006.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T21:46:05Z" - latency: 4.253754ms message: 'load-balancer-api-internal: tcp connection to abd7b3cda12c344d5850e63591494e17-eec146f821d36006.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:45:05Z" - latency: 8.242776ms message: 'load-balancer-api-internal: resolved host name abd7b3cda12c344d5850e63591494e17-eec146f821d36006.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T21:45:05Z" - latency: 4.607069ms message: 'load-balancer-api-internal: tcp connection to abd7b3cda12c344d5850e63591494e17-eec146f821d36006.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:44:05Z" - latency: 7.98894ms message: 'load-balancer-api-internal: resolved host name abd7b3cda12c344d5850e63591494e17-eec146f821d36006.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T21:44:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:30:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-65-to-network-check-target-ip-10-0-131-55 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-65.ec2.internal uid: ab5d2c5a-5ffa-4e37-8bea-c9b66b5f8dad resourceVersion: "17994" uid: 2773d440-3468-4f5c-b9f5-671cd8c682d3 spec: sourcePod: network-check-source-8894fc9bd-5zhmk targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-24T21:37:05Z" message: 'network-check-target-ip-10-0-131-55: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.297552ms message: 'network-check-target-ip-10-0-131-55: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:44:05Z" - latency: 2.262688ms message: 'network-check-target-ip-10-0-131-55: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:43:05Z" - latency: 2.142205ms message: 'network-check-target-ip-10-0-131-55: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:42:05Z" - latency: 2.083926ms message: 'network-check-target-ip-10-0-131-55: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:41:05Z" - latency: 2.223237ms message: 'network-check-target-ip-10-0-131-55: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:40:05Z" - latency: 2.528328ms message: 'network-check-target-ip-10-0-131-55: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:39:05Z" - latency: 2.0942ms message: 'network-check-target-ip-10-0-131-55: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:38:05Z" - latency: 2.171287ms message: 'network-check-target-ip-10-0-131-55: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:37:05Z" - latency: 2.173914ms message: 'network-check-target-ip-10-0-131-55: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:36:05Z" - latency: 2.089322ms message: 'network-check-target-ip-10-0-131-55: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:35:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:30:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-65-to-network-check-target-ip-10-0-136-65 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-65.ec2.internal uid: ab5d2c5a-5ffa-4e37-8bea-c9b66b5f8dad resourceVersion: "17992" uid: 07c29c3b-c374-4392-b11d-ad40aa5ea9b0 spec: sourcePod: network-check-source-8894fc9bd-5zhmk targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-24T21:37:05Z" message: 'network-check-target-ip-10-0-136-65: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 912.895µs message: 'network-check-target-ip-10-0-136-65: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:44:05Z" - latency: 822.832µs message: 'network-check-target-ip-10-0-136-65: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:43:05Z" - latency: 1.140689ms message: 'network-check-target-ip-10-0-136-65: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:42:05Z" - latency: 805.341µs message: 'network-check-target-ip-10-0-136-65: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:41:05Z" - latency: 929.006µs message: 'network-check-target-ip-10-0-136-65: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:40:05Z" - latency: 1.428092ms message: 'network-check-target-ip-10-0-136-65: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:39:05Z" - latency: 1.026993ms message: 'network-check-target-ip-10-0-136-65: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:38:05Z" - latency: 758.976µs message: 'network-check-target-ip-10-0-136-65: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:37:05Z" - latency: 1.481773ms message: 'network-check-target-ip-10-0-136-65: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:36:05Z" - latency: 876.241µs message: 'network-check-target-ip-10-0-136-65: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:35:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:30:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-65-to-network-check-target-ip-10-0-139-184 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-65.ec2.internal uid: ab5d2c5a-5ffa-4e37-8bea-c9b66b5f8dad resourceVersion: "17993" uid: dc137793-88a8-477d-b2a4-47937b6d5418 spec: sourcePod: network-check-source-8894fc9bd-5zhmk targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-24T21:37:05Z" message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.297902ms message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:44:05Z" - latency: 2.710887ms message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:43:05Z" - latency: 2.026147ms message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:42:05Z" - latency: 2.227737ms message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:41:05Z" - latency: 2.023343ms message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:40:05Z" - latency: 2.064364ms message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:39:05Z" - latency: 2.094437ms message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:38:05Z" - latency: 2.300316ms message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:37:05Z" - latency: 2.415881ms message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:36:05Z" - latency: 2.400049ms message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:35:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:30:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-65-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-65.ec2.internal uid: ab5d2c5a-5ffa-4e37-8bea-c9b66b5f8dad resourceVersion: "20037" uid: f616e460-4814-4d24-861a-e6051a8016f9 spec: sourcePod: network-check-source-8894fc9bd-5zhmk targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-24T21:36:05Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 901.111µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:48:05Z" - latency: 1.965574ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T21:48:05Z" - latency: 678.604µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:47:05Z" - latency: 1.631314ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T21:47:05Z" - latency: 979.604µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:46:05Z" - latency: 1.884366ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T21:46:05Z" - latency: 1.135104ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:45:05Z" - latency: 1.76177ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T21:45:05Z" - latency: 874.027µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:44:05Z" - latency: 1.709938ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T21:44:05Z" kind: List metadata: resourceVersion: ""