apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T17:37:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-169-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-169.ec2.internal uid: fbc5c14f-85cf-4277-a2e0-094ff236ce6f resourceVersion: "45438" uid: bba708df-cf8e-4ebd-8b1d-9e4ed926e97f spec: sourcePod: network-check-source-dbd9cf844-v2tms targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-10T17:44:02Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.002796ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T18:05:02Z" - latency: 1.173251ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T18:04:02Z" - latency: 1.2397ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T18:03:02Z" - latency: 1.115511ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T18:02:02Z" - latency: 1.00855ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T18:01:02Z" - latency: 1.149395ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T18:00:02Z" - latency: 1.276816ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:59:02Z" - latency: 1.195454ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:58:02Z" - latency: 803.314µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:57:02Z" - latency: 960.204µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:56:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T17:37:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-169-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-169.ec2.internal uid: fbc5c14f-85cf-4277-a2e0-094ff236ce6f resourceVersion: "47511" uid: c9bd100f-35c2-4bc2-8b99-c7fc0818caa2 spec: sourcePod: network-check-source-dbd9cf844-v2tms targetEndpoint: ac9ae24afd57b4f46a8afcf8e3f2a3ef-b754526265a5c131.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-10T17:43:02Z" message: 'load-balancer-api-external: tcp connection to ac9ae24afd57b4f46a8afcf8e3f2a3ef-b754526265a5c131.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.371377ms message: 'load-balancer-api-external: tcp connection to ac9ae24afd57b4f46a8afcf8e3f2a3ef-b754526265a5c131.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T18:07:02Z" - latency: 6.731126ms message: 'load-balancer-api-external: resolved host name ac9ae24afd57b4f46a8afcf8e3f2a3ef-b754526265a5c131.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T18:07:02Z" - latency: 5.217731ms message: 'load-balancer-api-external: tcp connection to ac9ae24afd57b4f46a8afcf8e3f2a3ef-b754526265a5c131.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T18:06:02Z" - latency: 7.133015ms message: 'load-balancer-api-external: resolved host name ac9ae24afd57b4f46a8afcf8e3f2a3ef-b754526265a5c131.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T18:06:02Z" - latency: 4.439552ms message: 'load-balancer-api-external: tcp connection to ac9ae24afd57b4f46a8afcf8e3f2a3ef-b754526265a5c131.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T18:05:02Z" - latency: 7.111401ms message: 'load-balancer-api-external: resolved host name ac9ae24afd57b4f46a8afcf8e3f2a3ef-b754526265a5c131.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T18:05:02Z" - latency: 4.418184ms message: 'load-balancer-api-external: tcp connection to ac9ae24afd57b4f46a8afcf8e3f2a3ef-b754526265a5c131.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T18:04:02Z" - latency: 6.993601ms message: 'load-balancer-api-external: resolved host name ac9ae24afd57b4f46a8afcf8e3f2a3ef-b754526265a5c131.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T18:04:02Z" - latency: 4.882393ms message: 'load-balancer-api-external: tcp connection to ac9ae24afd57b4f46a8afcf8e3f2a3ef-b754526265a5c131.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T18:03:02Z" - latency: 6.138267ms message: 'load-balancer-api-external: resolved host name ac9ae24afd57b4f46a8afcf8e3f2a3ef-b754526265a5c131.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T18:03:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T17:37:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-169-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-169.ec2.internal uid: fbc5c14f-85cf-4277-a2e0-094ff236ce6f resourceVersion: "47512" uid: ce80596b-739f-44d0-8681-211b4859bca3 spec: sourcePod: network-check-source-dbd9cf844-v2tms targetEndpoint: ac9ae24afd57b4f46a8afcf8e3f2a3ef-b754526265a5c131.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-10T17:43:02Z" message: 'load-balancer-api-internal: tcp connection to ac9ae24afd57b4f46a8afcf8e3f2a3ef-b754526265a5c131.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.393694ms message: 'load-balancer-api-internal: tcp connection to ac9ae24afd57b4f46a8afcf8e3f2a3ef-b754526265a5c131.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T18:07:02Z" - latency: 6.76295ms message: 'load-balancer-api-internal: resolved host name ac9ae24afd57b4f46a8afcf8e3f2a3ef-b754526265a5c131.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T18:07:02Z" - latency: 4.419603ms message: 'load-balancer-api-internal: tcp connection to ac9ae24afd57b4f46a8afcf8e3f2a3ef-b754526265a5c131.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T18:06:02Z" - latency: 7.1984ms message: 'load-balancer-api-internal: resolved host name ac9ae24afd57b4f46a8afcf8e3f2a3ef-b754526265a5c131.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T18:06:02Z" - latency: 5.565773ms message: 'load-balancer-api-internal: tcp connection to ac9ae24afd57b4f46a8afcf8e3f2a3ef-b754526265a5c131.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T18:05:02Z" - latency: 7.124515ms message: 'load-balancer-api-internal: resolved host name ac9ae24afd57b4f46a8afcf8e3f2a3ef-b754526265a5c131.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T18:05:02Z" - latency: 3.924393ms message: 'load-balancer-api-internal: tcp connection to ac9ae24afd57b4f46a8afcf8e3f2a3ef-b754526265a5c131.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T18:04:02Z" - latency: 7.030051ms message: 'load-balancer-api-internal: resolved host name ac9ae24afd57b4f46a8afcf8e3f2a3ef-b754526265a5c131.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T18:04:02Z" - latency: 4.898291ms message: 'load-balancer-api-internal: tcp connection to ac9ae24afd57b4f46a8afcf8e3f2a3ef-b754526265a5c131.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T18:03:02Z" - latency: 6.124376ms message: 'load-balancer-api-internal: resolved host name ac9ae24afd57b4f46a8afcf8e3f2a3ef-b754526265a5c131.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T18:03:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T17:37:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-169-to-network-check-target-ip-10-0-133-83 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-169.ec2.internal uid: fbc5c14f-85cf-4277-a2e0-094ff236ce6f resourceVersion: "45436" uid: 1ad88c6d-2497-43e5-98e3-7a6c3dcc125f spec: sourcePod: network-check-source-dbd9cf844-v2tms targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-10T17:44:02Z" message: 'network-check-target-ip-10-0-133-83: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.987385ms message: 'network-check-target-ip-10-0-133-83: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T18:05:02Z" - latency: 1.932996ms message: 'network-check-target-ip-10-0-133-83: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T18:04:02Z" - latency: 2.274682ms message: 'network-check-target-ip-10-0-133-83: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T18:03:02Z" - latency: 2.076883ms message: 'network-check-target-ip-10-0-133-83: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T18:02:02Z" - latency: 2.249623ms message: 'network-check-target-ip-10-0-133-83: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T18:01:02Z" - latency: 1.767783ms message: 'network-check-target-ip-10-0-133-83: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T18:00:02Z" - latency: 1.993484ms message: 'network-check-target-ip-10-0-133-83: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:59:02Z" - latency: 2.121845ms message: 'network-check-target-ip-10-0-133-83: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:58:02Z" - latency: 2.121607ms message: 'network-check-target-ip-10-0-133-83: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:57:02Z" - latency: 2.184551ms message: 'network-check-target-ip-10-0-133-83: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:56:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T17:37:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-169-to-network-check-target-ip-10-0-134-169 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-169.ec2.internal uid: fbc5c14f-85cf-4277-a2e0-094ff236ce6f resourceVersion: "45437" uid: 3c8c2945-f754-48af-939f-cb54bd17eded spec: sourcePod: network-check-source-dbd9cf844-v2tms targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-10T17:44:02Z" message: 'network-check-target-ip-10-0-134-169: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.45524ms message: 'network-check-target-ip-10-0-134-169: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T18:05:02Z" - latency: 820.325µs message: 'network-check-target-ip-10-0-134-169: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T18:04:02Z" - latency: 959.295µs message: 'network-check-target-ip-10-0-134-169: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T18:03:02Z" - latency: 812.069µs message: 'network-check-target-ip-10-0-134-169: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T18:02:02Z" - latency: 863.661µs message: 'network-check-target-ip-10-0-134-169: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T18:01:02Z" - latency: 879.672µs message: 'network-check-target-ip-10-0-134-169: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T18:00:02Z" - latency: 931.701µs message: 'network-check-target-ip-10-0-134-169: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:59:02Z" - latency: 869.845µs message: 'network-check-target-ip-10-0-134-169: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:58:02Z" - latency: 868.043µs message: 'network-check-target-ip-10-0-134-169: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:57:02Z" - latency: 1.394281ms message: 'network-check-target-ip-10-0-134-169: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:56:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T17:37:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-169-to-network-check-target-ip-10-0-138-237 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-169.ec2.internal uid: fbc5c14f-85cf-4277-a2e0-094ff236ce6f resourceVersion: "45435" uid: d337175d-f334-45c5-a2a2-6f99d6633b00 spec: sourcePod: network-check-source-dbd9cf844-v2tms targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-10T17:44:02Z" message: 'network-check-target-ip-10-0-138-237: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.080886ms message: 'network-check-target-ip-10-0-138-237: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T18:05:02Z" - latency: 1.792084ms message: 'network-check-target-ip-10-0-138-237: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T18:04:02Z" - latency: 2.603375ms message: 'network-check-target-ip-10-0-138-237: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T18:03:02Z" - latency: 2.296421ms message: 'network-check-target-ip-10-0-138-237: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T18:02:02Z" - latency: 2.287186ms message: 'network-check-target-ip-10-0-138-237: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T18:01:02Z" - latency: 2.254872ms message: 'network-check-target-ip-10-0-138-237: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T18:00:02Z" - latency: 2.220672ms message: 'network-check-target-ip-10-0-138-237: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:59:02Z" - latency: 2.259291ms message: 'network-check-target-ip-10-0-138-237: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:58:02Z" - latency: 2.093345ms message: 'network-check-target-ip-10-0-138-237: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:57:02Z" - latency: 2.142396ms message: 'network-check-target-ip-10-0-138-237: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:56:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T17:37:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-169-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-169.ec2.internal uid: fbc5c14f-85cf-4277-a2e0-094ff236ce6f resourceVersion: "47510" uid: 01937093-31eb-4b66-a789-739f9ea66dd9 spec: sourcePod: network-check-source-dbd9cf844-v2tms targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-10T17:43:02Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.213649ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T18:07:02Z" - latency: 1.751558ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T18:07:02Z" - latency: 854.72µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T18:06:02Z" - latency: 1.99581ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T18:06:02Z" - latency: 773.372µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T18:05:02Z" - latency: 1.754596ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T18:05:02Z" - latency: 903.101µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T18:04:02Z" - latency: 1.841745ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T18:04:02Z" - latency: 847.402µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T18:03:02Z" - latency: 1.750541ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T18:03:02Z" kind: List metadata: resourceVersion: ""