apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T18:50:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-56-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-56.ec2.internal uid: a930075f-6888-476d-b7ec-0679aeb310a4 resourceVersion: "31977" uid: d8064fb4-fecc-4153-b1e9-d70301aa88b9 spec: sourcePod: network-check-source-8894fc9bd-qlzm7 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-22T18:57:40Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.061138ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:32:40Z" - latency: 1.085677ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:31:40Z" - latency: 1.126317ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:30:40Z" - latency: 1.218407ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:29:40Z" - latency: 1.136682ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:28:40Z" - latency: 1.062135ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:27:40Z" - latency: 1.046566ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:26:40Z" - latency: 1.193709ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:25:40Z" - latency: 1.0763ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:24:40Z" - latency: 1.103169ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:23:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T18:50:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-56-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-56.ec2.internal uid: a930075f-6888-476d-b7ec-0679aeb310a4 resourceVersion: "31978" uid: ec734adf-c0a0-48db-8ad0-ba164ce9dd3c spec: sourcePod: network-check-source-8894fc9bd-qlzm7 targetEndpoint: a336c71b28d684c869ebab43bd948359-b728afee5a341dc5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T18:56:40Z" message: 'load-balancer-api-external: tcp connection to a336c71b28d684c869ebab43bd948359-b728afee5a341dc5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.535576ms message: 'load-balancer-api-external: tcp connection to a336c71b28d684c869ebab43bd948359-b728afee5a341dc5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:32:40Z" - latency: 6.712234ms message: 'load-balancer-api-external: resolved host name a336c71b28d684c869ebab43bd948359-b728afee5a341dc5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:32:40Z" - latency: 3.950856ms message: 'load-balancer-api-external: tcp connection to a336c71b28d684c869ebab43bd948359-b728afee5a341dc5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:31:40Z" - latency: 6.458833ms message: 'load-balancer-api-external: resolved host name a336c71b28d684c869ebab43bd948359-b728afee5a341dc5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:31:40Z" - latency: 5.673839ms message: 'load-balancer-api-external: tcp connection to a336c71b28d684c869ebab43bd948359-b728afee5a341dc5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:30:40Z" - latency: 6.743842ms message: 'load-balancer-api-external: resolved host name a336c71b28d684c869ebab43bd948359-b728afee5a341dc5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:30:40Z" - latency: 4.407965ms message: 'load-balancer-api-external: tcp connection to a336c71b28d684c869ebab43bd948359-b728afee5a341dc5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:29:40Z" - latency: 9.080637ms message: 'load-balancer-api-external: resolved host name a336c71b28d684c869ebab43bd948359-b728afee5a341dc5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:29:40Z" - latency: 4.793409ms message: 'load-balancer-api-external: tcp connection to a336c71b28d684c869ebab43bd948359-b728afee5a341dc5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:28:40Z" - latency: 6.362156ms message: 'load-balancer-api-external: resolved host name a336c71b28d684c869ebab43bd948359-b728afee5a341dc5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:28:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T18:50:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-56-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-56.ec2.internal uid: a930075f-6888-476d-b7ec-0679aeb310a4 resourceVersion: "31979" uid: 40b9f4b8-29d9-4bed-89bb-eafbe198c531 spec: sourcePod: network-check-source-8894fc9bd-qlzm7 targetEndpoint: a336c71b28d684c869ebab43bd948359-b728afee5a341dc5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T18:56:40Z" message: 'load-balancer-api-internal: tcp connection to a336c71b28d684c869ebab43bd948359-b728afee5a341dc5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.490557ms message: 'load-balancer-api-internal: tcp connection to a336c71b28d684c869ebab43bd948359-b728afee5a341dc5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:32:40Z" - latency: 6.759507ms message: 'load-balancer-api-internal: resolved host name a336c71b28d684c869ebab43bd948359-b728afee5a341dc5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:32:40Z" - latency: 4.433503ms message: 'load-balancer-api-internal: tcp connection to a336c71b28d684c869ebab43bd948359-b728afee5a341dc5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:31:40Z" - latency: 6.490465ms message: 'load-balancer-api-internal: resolved host name a336c71b28d684c869ebab43bd948359-b728afee5a341dc5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:31:40Z" - latency: 5.668242ms message: 'load-balancer-api-internal: tcp connection to a336c71b28d684c869ebab43bd948359-b728afee5a341dc5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:30:40Z" - latency: 6.802455ms message: 'load-balancer-api-internal: resolved host name a336c71b28d684c869ebab43bd948359-b728afee5a341dc5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:30:40Z" - latency: 4.391632ms message: 'load-balancer-api-internal: tcp connection to a336c71b28d684c869ebab43bd948359-b728afee5a341dc5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:29:40Z" - latency: 8.9898ms message: 'load-balancer-api-internal: resolved host name a336c71b28d684c869ebab43bd948359-b728afee5a341dc5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:29:40Z" - latency: 4.792833ms message: 'load-balancer-api-internal: tcp connection to a336c71b28d684c869ebab43bd948359-b728afee5a341dc5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:28:40Z" - latency: 6.264031ms message: 'load-balancer-api-internal: resolved host name a336c71b28d684c869ebab43bd948359-b728afee5a341dc5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:28:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T18:50:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-56-to-network-check-target-ip-10-0-134-109 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-56.ec2.internal uid: a930075f-6888-476d-b7ec-0679aeb310a4 resourceVersion: "31974" uid: bac27bc7-6a27-4082-aa4a-8aa834f63325 spec: sourcePod: network-check-source-8894fc9bd-qlzm7 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-22T18:57:40Z" message: 'network-check-target-ip-10-0-134-109: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.339556ms message: 'network-check-target-ip-10-0-134-109: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:32:40Z" - latency: 2.10811ms message: 'network-check-target-ip-10-0-134-109: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:31:40Z" - latency: 2.130184ms message: 'network-check-target-ip-10-0-134-109: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:30:40Z" - latency: 2.205069ms message: 'network-check-target-ip-10-0-134-109: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:29:40Z" - latency: 2.029562ms message: 'network-check-target-ip-10-0-134-109: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:28:40Z" - latency: 2.236169ms message: 'network-check-target-ip-10-0-134-109: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:27:40Z" - latency: 1.898556ms message: 'network-check-target-ip-10-0-134-109: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:26:40Z" - latency: 2.080153ms message: 'network-check-target-ip-10-0-134-109: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:25:40Z" - latency: 2.176875ms message: 'network-check-target-ip-10-0-134-109: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:24:40Z" - latency: 2.406201ms message: 'network-check-target-ip-10-0-134-109: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:23:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T18:50:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-56-to-network-check-target-ip-10-0-138-84 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-56.ec2.internal uid: a930075f-6888-476d-b7ec-0679aeb310a4 resourceVersion: "31975" uid: 69ba64d6-12d5-4c8a-a31d-12f7a7f25945 spec: sourcePod: network-check-source-8894fc9bd-qlzm7 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-22T18:57:40Z" message: 'network-check-target-ip-10-0-138-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.172327ms message: 'network-check-target-ip-10-0-138-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:32:40Z" - latency: 2.135348ms message: 'network-check-target-ip-10-0-138-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:31:40Z" - latency: 2.208644ms message: 'network-check-target-ip-10-0-138-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:30:40Z" - latency: 2.404127ms message: 'network-check-target-ip-10-0-138-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:29:40Z" - latency: 1.998735ms message: 'network-check-target-ip-10-0-138-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:28:40Z" - latency: 2.18571ms message: 'network-check-target-ip-10-0-138-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:27:40Z" - latency: 2.064064ms message: 'network-check-target-ip-10-0-138-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:26:40Z" - latency: 2.331619ms message: 'network-check-target-ip-10-0-138-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:25:40Z" - latency: 2.013919ms message: 'network-check-target-ip-10-0-138-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:24:40Z" - latency: 2.117945ms message: 'network-check-target-ip-10-0-138-84: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:23:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T18:50:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-56-to-network-check-target-ip-10-0-143-56 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-56.ec2.internal uid: a930075f-6888-476d-b7ec-0679aeb310a4 resourceVersion: "31973" uid: 2072e1b6-60e9-42a3-bc54-79044116e384 spec: sourcePod: network-check-source-8894fc9bd-qlzm7 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-22T18:57:40Z" message: 'network-check-target-ip-10-0-143-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.400693ms message: 'network-check-target-ip-10-0-143-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:32:40Z" - latency: 793.013µs message: 'network-check-target-ip-10-0-143-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:31:40Z" - latency: 1.137434ms message: 'network-check-target-ip-10-0-143-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:30:40Z" - latency: 1.458968ms message: 'network-check-target-ip-10-0-143-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:29:40Z" - latency: 1.231364ms message: 'network-check-target-ip-10-0-143-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:28:40Z" - latency: 925.291µs message: 'network-check-target-ip-10-0-143-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:27:40Z" - latency: 747.353µs message: 'network-check-target-ip-10-0-143-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:26:40Z" - latency: 785.882µs message: 'network-check-target-ip-10-0-143-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:25:40Z" - latency: 920.547µs message: 'network-check-target-ip-10-0-143-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:24:40Z" - latency: 898.146µs message: 'network-check-target-ip-10-0-143-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:23:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T18:50:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-56-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-56.ec2.internal uid: a930075f-6888-476d-b7ec-0679aeb310a4 resourceVersion: "31976" uid: ab75331c-b164-4670-96c9-42223a242717 spec: sourcePod: network-check-source-8894fc9bd-qlzm7 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-22T18:56:40Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 965.985µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:32:40Z" - latency: 1.815248ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T19:32:40Z" - latency: 804.206µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:31:40Z" - latency: 1.598153ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T19:31:40Z" - latency: 1.232591ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:30:40Z" - latency: 1.743415ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T19:30:40Z" - latency: 903.751µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:29:40Z" - latency: 1.77659ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T19:29:40Z" - latency: 1.137432ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:28:40Z" - latency: 1.626199ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T19:28:40Z" kind: List metadata: resourceVersion: ""