apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T17:13:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-224-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-224.ec2.internal uid: 25fa09a6-b3c5-4071-a358-4237cbaf76be resourceVersion: "44235" uid: 9f57180b-9369-491e-8863-5e1ac574bf5c spec: sourcePod: network-check-source-8894fc9bd-mvw99 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-17T17:20:08Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.092862ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:41:08Z" - latency: 1.192414ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:40:08Z" - latency: 1.40359ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:39:08Z" - latency: 965.777µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:38:08Z" - latency: 951.818µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:37:08Z" - latency: 1.0432ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:36:08Z" - latency: 1.513513ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:35:08Z" - latency: 1.063348ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:34:08Z" - latency: 819.682µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:33:08Z" - latency: 1.389946ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:32:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T17:13:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-224-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-224.ec2.internal uid: 25fa09a6-b3c5-4071-a358-4237cbaf76be resourceVersion: "39714" uid: f09af14f-3f51-4a60-89fd-d9c904c833c8 spec: sourcePod: network-check-source-8894fc9bd-mvw99 targetEndpoint: ac80004889c49441e93e336808239913-5e455a0c30e4a692.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-17T17:19:08Z" message: 'load-balancer-api-external: tcp connection to ac80004889c49441e93e336808239913-5e455a0c30e4a692.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.199376ms message: 'load-balancer-api-external: tcp connection to ac80004889c49441e93e336808239913-5e455a0c30e4a692.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:37:08Z" - latency: 9.65741ms message: 'load-balancer-api-external: resolved host name ac80004889c49441e93e336808239913-5e455a0c30e4a692.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:37:08Z" - latency: 4.200708ms message: 'load-balancer-api-external: tcp connection to ac80004889c49441e93e336808239913-5e455a0c30e4a692.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:36:08Z" - latency: 7.226589ms message: 'load-balancer-api-external: resolved host name ac80004889c49441e93e336808239913-5e455a0c30e4a692.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:36:08Z" - latency: 3.848779ms message: 'load-balancer-api-external: tcp connection to ac80004889c49441e93e336808239913-5e455a0c30e4a692.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:35:08Z" - latency: 6.865865ms message: 'load-balancer-api-external: resolved host name ac80004889c49441e93e336808239913-5e455a0c30e4a692.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:35:08Z" - latency: 3.796071ms message: 'load-balancer-api-external: tcp connection to ac80004889c49441e93e336808239913-5e455a0c30e4a692.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:34:08Z" - latency: 7.574251ms message: 'load-balancer-api-external: resolved host name ac80004889c49441e93e336808239913-5e455a0c30e4a692.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:34:08Z" - latency: 3.753217ms message: 'load-balancer-api-external: tcp connection to ac80004889c49441e93e336808239913-5e455a0c30e4a692.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:33:08Z" - latency: 9.330995ms message: 'load-balancer-api-external: resolved host name ac80004889c49441e93e336808239913-5e455a0c30e4a692.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:33:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T17:13:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-224-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-224.ec2.internal uid: 25fa09a6-b3c5-4071-a358-4237cbaf76be resourceVersion: "39713" uid: d5c2fc7d-cb8b-4cd5-aeba-977c536902bc spec: sourcePod: network-check-source-8894fc9bd-mvw99 targetEndpoint: ac80004889c49441e93e336808239913-5e455a0c30e4a692.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-17T17:19:08Z" message: 'load-balancer-api-internal: tcp connection to ac80004889c49441e93e336808239913-5e455a0c30e4a692.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.539348ms message: 'load-balancer-api-internal: tcp connection to ac80004889c49441e93e336808239913-5e455a0c30e4a692.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:37:08Z" - latency: 9.597598ms message: 'load-balancer-api-internal: resolved host name ac80004889c49441e93e336808239913-5e455a0c30e4a692.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:37:08Z" - latency: 5.288691ms message: 'load-balancer-api-internal: tcp connection to ac80004889c49441e93e336808239913-5e455a0c30e4a692.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:36:08Z" - latency: 7.299024ms message: 'load-balancer-api-internal: resolved host name ac80004889c49441e93e336808239913-5e455a0c30e4a692.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:36:08Z" - latency: 4.611726ms message: 'load-balancer-api-internal: tcp connection to ac80004889c49441e93e336808239913-5e455a0c30e4a692.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:35:08Z" - latency: 6.739284ms message: 'load-balancer-api-internal: resolved host name ac80004889c49441e93e336808239913-5e455a0c30e4a692.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:35:08Z" - latency: 5.13922ms message: 'load-balancer-api-internal: tcp connection to ac80004889c49441e93e336808239913-5e455a0c30e4a692.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:34:08Z" - latency: 7.687799ms message: 'load-balancer-api-internal: resolved host name ac80004889c49441e93e336808239913-5e455a0c30e4a692.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:34:08Z" - latency: 6.298803ms message: 'load-balancer-api-internal: tcp connection to ac80004889c49441e93e336808239913-5e455a0c30e4a692.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:33:08Z" - latency: 10.199215ms message: 'load-balancer-api-internal: resolved host name ac80004889c49441e93e336808239913-5e455a0c30e4a692.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:33:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T17:13:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-224-to-network-check-target-ip-10-0-132-98 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-224.ec2.internal uid: 25fa09a6-b3c5-4071-a358-4237cbaf76be resourceVersion: "44234" uid: d47af9b7-ce96-42b9-8232-adb924081478 spec: sourcePod: network-check-source-8894fc9bd-mvw99 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-17T17:20:08Z" message: 'network-check-target-ip-10-0-132-98: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.755525ms message: 'network-check-target-ip-10-0-132-98: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:41:08Z" - latency: 1.749558ms message: 'network-check-target-ip-10-0-132-98: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:40:08Z" - latency: 1.993961ms message: 'network-check-target-ip-10-0-132-98: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:39:08Z" - latency: 1.875876ms message: 'network-check-target-ip-10-0-132-98: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:38:08Z" - latency: 1.766034ms message: 'network-check-target-ip-10-0-132-98: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:37:08Z" - latency: 1.952144ms message: 'network-check-target-ip-10-0-132-98: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:36:08Z" - latency: 1.957834ms message: 'network-check-target-ip-10-0-132-98: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:35:08Z" - latency: 2.040885ms message: 'network-check-target-ip-10-0-132-98: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:34:08Z" - latency: 1.751227ms message: 'network-check-target-ip-10-0-132-98: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:33:08Z" - latency: 1.849494ms message: 'network-check-target-ip-10-0-132-98: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:32:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T17:13:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-224-to-network-check-target-ip-10-0-134-244 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-224.ec2.internal uid: 25fa09a6-b3c5-4071-a358-4237cbaf76be resourceVersion: "44233" uid: 4ffbb856-0526-4803-bb38-6347121a55cb spec: sourcePod: network-check-source-8894fc9bd-mvw99 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-17T17:20:08Z" message: 'network-check-target-ip-10-0-134-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.065214ms message: 'network-check-target-ip-10-0-134-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:41:08Z" - latency: 2.099865ms message: 'network-check-target-ip-10-0-134-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:40:08Z" - latency: 2.130725ms message: 'network-check-target-ip-10-0-134-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:39:08Z" - latency: 2.191776ms message: 'network-check-target-ip-10-0-134-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:38:08Z" - latency: 1.997155ms message: 'network-check-target-ip-10-0-134-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:37:08Z" - latency: 2.003371ms message: 'network-check-target-ip-10-0-134-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:36:08Z" - latency: 2.044732ms message: 'network-check-target-ip-10-0-134-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:35:08Z" - latency: 2.131225ms message: 'network-check-target-ip-10-0-134-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:34:08Z" - latency: 1.9851ms message: 'network-check-target-ip-10-0-134-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:33:08Z" - latency: 2.049742ms message: 'network-check-target-ip-10-0-134-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:32:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T17:13:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-224-to-network-check-target-ip-10-0-138-224 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-224.ec2.internal uid: 25fa09a6-b3c5-4071-a358-4237cbaf76be resourceVersion: "44232" uid: 3113e152-2003-4cb0-a3d2-73d991afa4e9 spec: sourcePod: network-check-source-8894fc9bd-mvw99 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-17T17:20:08Z" message: 'network-check-target-ip-10-0-138-224: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 767.979µs message: 'network-check-target-ip-10-0-138-224: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:41:08Z" - latency: 862.928µs message: 'network-check-target-ip-10-0-138-224: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:40:08Z" - latency: 1.545162ms message: 'network-check-target-ip-10-0-138-224: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:39:08Z" - latency: 1.187154ms message: 'network-check-target-ip-10-0-138-224: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:38:08Z" - latency: 794.308µs message: 'network-check-target-ip-10-0-138-224: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:37:08Z" - latency: 807.595µs message: 'network-check-target-ip-10-0-138-224: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:36:08Z" - latency: 1.615019ms message: 'network-check-target-ip-10-0-138-224: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:35:08Z" - latency: 830.831µs message: 'network-check-target-ip-10-0-138-224: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:34:08Z" - latency: 739.435µs message: 'network-check-target-ip-10-0-138-224: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:33:08Z" - latency: 919.156µs message: 'network-check-target-ip-10-0-138-224: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:32:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T17:13:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-224-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-224.ec2.internal uid: 25fa09a6-b3c5-4071-a358-4237cbaf76be resourceVersion: "39712" uid: b7c5f5e1-adab-4360-9ba1-91ad6270c166 spec: sourcePod: network-check-source-8894fc9bd-mvw99 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-17T17:19:08Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.016575ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:37:08Z" - latency: 1.839365ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T17:37:08Z" - latency: 922.182µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:36:08Z" - latency: 1.732319ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T17:36:08Z" - latency: 961.131µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:35:08Z" - latency: 2.146642ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T17:35:08Z" - latency: 1.128264ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:34:08Z" - latency: 1.803138ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T17:34:08Z" - latency: 869.129µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:33:08Z" - latency: 2.257444ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T17:33:08Z" kind: List metadata: resourceVersion: ""