apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T16:35:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-142-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-142.ec2.internal uid: 94418194-16e7-4577-944a-74eb342abb6f resourceVersion: "34378" uid: ac16cc5a-5ecb-4be8-9842-40d774e3c028 spec: sourcePod: network-check-source-8894fc9bd-98qjc targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-17T16:42:47Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.511603ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:56:47Z" - latency: 1.281295ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:55:47Z" - latency: 1.597843ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:54:47Z" - latency: 1.202699ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:53:47Z" - latency: 1.299639ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:52:47Z" - latency: 1.095633ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:51:47Z" - latency: 1.143415ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:50:47Z" - latency: 1.371224ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:49:47Z" - latency: 1.138016ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:48:47Z" - latency: 1.315622ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:47:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T16:35:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-142-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-142.ec2.internal uid: 94418194-16e7-4577-944a-74eb342abb6f resourceVersion: "31405" uid: 28fced95-4c68-4f1a-b159-00c98254f229 spec: sourcePod: network-check-source-8894fc9bd-98qjc targetEndpoint: a0fb60b58264f43cc873eef9bb7b328b-50a15cb302997ce5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-17T16:41:47Z" message: 'load-balancer-api-external: tcp connection to a0fb60b58264f43cc873eef9bb7b328b-50a15cb302997ce5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.474455ms message: 'load-balancer-api-external: tcp connection to a0fb60b58264f43cc873eef9bb7b328b-50a15cb302997ce5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:53:47Z" - latency: 7.234544ms message: 'load-balancer-api-external: resolved host name a0fb60b58264f43cc873eef9bb7b328b-50a15cb302997ce5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T16:53:47Z" - latency: 4.721202ms message: 'load-balancer-api-external: tcp connection to a0fb60b58264f43cc873eef9bb7b328b-50a15cb302997ce5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:52:47Z" - latency: 7.096668ms message: 'load-balancer-api-external: resolved host name a0fb60b58264f43cc873eef9bb7b328b-50a15cb302997ce5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T16:52:47Z" - latency: 5.26448ms message: 'load-balancer-api-external: tcp connection to a0fb60b58264f43cc873eef9bb7b328b-50a15cb302997ce5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:51:47Z" - latency: 5.867519ms message: 'load-balancer-api-external: resolved host name a0fb60b58264f43cc873eef9bb7b328b-50a15cb302997ce5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T16:51:47Z" - latency: 5.579605ms message: 'load-balancer-api-external: tcp connection to a0fb60b58264f43cc873eef9bb7b328b-50a15cb302997ce5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:50:47Z" - latency: 6.828761ms message: 'load-balancer-api-external: resolved host name a0fb60b58264f43cc873eef9bb7b328b-50a15cb302997ce5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T16:50:47Z" - latency: 5.032363ms message: 'load-balancer-api-external: tcp connection to a0fb60b58264f43cc873eef9bb7b328b-50a15cb302997ce5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:49:47Z" - latency: 7.198844ms message: 'load-balancer-api-external: resolved host name a0fb60b58264f43cc873eef9bb7b328b-50a15cb302997ce5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T16:49:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T16:35:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-142-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-142.ec2.internal uid: 94418194-16e7-4577-944a-74eb342abb6f resourceVersion: "31406" uid: b5a2ea7f-0f5d-47cd-b071-643291c912ad spec: sourcePod: network-check-source-8894fc9bd-98qjc targetEndpoint: a0fb60b58264f43cc873eef9bb7b328b-50a15cb302997ce5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-17T16:41:47Z" message: 'load-balancer-api-internal: tcp connection to a0fb60b58264f43cc873eef9bb7b328b-50a15cb302997ce5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.487296ms message: 'load-balancer-api-internal: tcp connection to a0fb60b58264f43cc873eef9bb7b328b-50a15cb302997ce5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:53:47Z" - latency: 7.312379ms message: 'load-balancer-api-internal: resolved host name a0fb60b58264f43cc873eef9bb7b328b-50a15cb302997ce5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T16:53:47Z" - latency: 4.636151ms message: 'load-balancer-api-internal: tcp connection to a0fb60b58264f43cc873eef9bb7b328b-50a15cb302997ce5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:52:47Z" - latency: 8.003683ms message: 'load-balancer-api-internal: resolved host name a0fb60b58264f43cc873eef9bb7b328b-50a15cb302997ce5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T16:52:47Z" - latency: 5.234087ms message: 'load-balancer-api-internal: tcp connection to a0fb60b58264f43cc873eef9bb7b328b-50a15cb302997ce5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:51:47Z" - latency: 6.01984ms message: 'load-balancer-api-internal: resolved host name a0fb60b58264f43cc873eef9bb7b328b-50a15cb302997ce5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T16:51:47Z" - latency: 4.215634ms message: 'load-balancer-api-internal: tcp connection to a0fb60b58264f43cc873eef9bb7b328b-50a15cb302997ce5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:50:47Z" - latency: 6.937491ms message: 'load-balancer-api-internal: resolved host name a0fb60b58264f43cc873eef9bb7b328b-50a15cb302997ce5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T16:50:47Z" - latency: 5.082825ms message: 'load-balancer-api-internal: tcp connection to a0fb60b58264f43cc873eef9bb7b328b-50a15cb302997ce5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:49:47Z" - latency: 7.230402ms message: 'load-balancer-api-internal: resolved host name a0fb60b58264f43cc873eef9bb7b328b-50a15cb302997ce5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T16:49:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T16:35:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-142-to-network-check-target-ip-10-0-130-35 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-142.ec2.internal uid: 94418194-16e7-4577-944a-74eb342abb6f resourceVersion: "34376" uid: f4efcc7e-3822-4fc8-bf7f-cd3190178994 spec: sourcePod: network-check-source-8894fc9bd-98qjc targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-17T16:42:47Z" message: 'network-check-target-ip-10-0-130-35: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.029336ms message: 'network-check-target-ip-10-0-130-35: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:56:47Z" - latency: 2.760923ms message: 'network-check-target-ip-10-0-130-35: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:55:47Z" - latency: 2.17711ms message: 'network-check-target-ip-10-0-130-35: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:54:47Z" - latency: 2.120479ms message: 'network-check-target-ip-10-0-130-35: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:53:47Z" - latency: 2.024498ms message: 'network-check-target-ip-10-0-130-35: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:52:47Z" - latency: 2.088785ms message: 'network-check-target-ip-10-0-130-35: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:51:47Z" - latency: 2.012196ms message: 'network-check-target-ip-10-0-130-35: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:50:47Z" - latency: 3.26476ms message: 'network-check-target-ip-10-0-130-35: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:49:47Z" - latency: 2.353772ms message: 'network-check-target-ip-10-0-130-35: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:48:47Z" - latency: 1.781312ms message: 'network-check-target-ip-10-0-130-35: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:47:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T16:35:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-142-to-network-check-target-ip-10-0-131-177 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-142.ec2.internal uid: 94418194-16e7-4577-944a-74eb342abb6f resourceVersion: "34377" uid: a6cde3b2-81be-4bda-b507-9d97dd0c674c spec: sourcePod: network-check-source-8894fc9bd-98qjc targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-17T16:42:47Z" message: 'network-check-target-ip-10-0-131-177: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.425357ms message: 'network-check-target-ip-10-0-131-177: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:56:47Z" - latency: 2.495987ms message: 'network-check-target-ip-10-0-131-177: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:55:47Z" - latency: 2.467714ms message: 'network-check-target-ip-10-0-131-177: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:54:47Z" - latency: 2.588458ms message: 'network-check-target-ip-10-0-131-177: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:53:47Z" - latency: 1.949425ms message: 'network-check-target-ip-10-0-131-177: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:52:47Z" - latency: 2.361064ms message: 'network-check-target-ip-10-0-131-177: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:51:47Z" - latency: 2.048721ms message: 'network-check-target-ip-10-0-131-177: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:50:47Z" - latency: 2.570157ms message: 'network-check-target-ip-10-0-131-177: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:49:47Z" - latency: 2.115502ms message: 'network-check-target-ip-10-0-131-177: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:48:47Z" - latency: 2.768892ms message: 'network-check-target-ip-10-0-131-177: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:47:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T16:35:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-142-to-network-check-target-ip-10-0-134-142 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-142.ec2.internal uid: 94418194-16e7-4577-944a-74eb342abb6f resourceVersion: "34375" uid: 568ef43a-42be-43f4-a3a9-5968de2a4362 spec: sourcePod: network-check-source-8894fc9bd-98qjc targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-17T16:42:47Z" message: 'network-check-target-ip-10-0-134-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.162842ms message: 'network-check-target-ip-10-0-134-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:56:47Z" - latency: 899.275µs message: 'network-check-target-ip-10-0-134-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:55:47Z" - latency: 1.295263ms message: 'network-check-target-ip-10-0-134-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:54:47Z" - latency: 899.842µs message: 'network-check-target-ip-10-0-134-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:53:47Z" - latency: 1.197712ms message: 'network-check-target-ip-10-0-134-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:52:47Z" - latency: 1.10289ms message: 'network-check-target-ip-10-0-134-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:51:47Z" - latency: 891.347µs message: 'network-check-target-ip-10-0-134-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:50:47Z" - latency: 1.023821ms message: 'network-check-target-ip-10-0-134-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:49:47Z" - latency: 1.033624ms message: 'network-check-target-ip-10-0-134-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:48:47Z" - latency: 935.1µs message: 'network-check-target-ip-10-0-134-142: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:47:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T16:35:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-142-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-142.ec2.internal uid: 94418194-16e7-4577-944a-74eb342abb6f resourceVersion: "31404" uid: f27e7791-f87e-41a7-a0fc-f0018c737b3c spec: sourcePod: network-check-source-8894fc9bd-98qjc targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-17T16:41:47Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 948.894µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:53:47Z" - latency: 2.074616ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T16:53:47Z" - latency: 1.050398ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:52:47Z" - latency: 2.12456ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T16:52:47Z" - latency: 749.413µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:51:47Z" - latency: 1.887422ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T16:51:47Z" - latency: 962.323µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:50:47Z" - latency: 1.792205ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T16:50:47Z" - latency: 1.30927ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:49:47Z" - latency: 2.085079ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T16:49:47Z" kind: List metadata: resourceVersion: ""