apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-07T19:32:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-58-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-58.ec2.internal uid: 60de79ca-45ae-4d1a-b45e-c687ea30e3ce resourceVersion: "28402" uid: 0d4b7aa1-8fe4-40aa-adde-c3dbc154d6ca spec: sourcePod: network-check-source-dbd9cf844-lvdz6 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-07T19:39:34Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 807.213µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:46:34Z" - latency: 1.135376ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:45:34Z" - latency: 1.259003ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:44:34Z" - latency: 905.827µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:43:34Z" - latency: 1.306725ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:42:34Z" - latency: 951.362µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:41:34Z" - latency: 1.183696ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:40:34Z" - latency: 898.737µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:39:34Z" - latency: 3.46836ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:38:34Z" - latency: 1.004034ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:37:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-07T19:32:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-58-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-58.ec2.internal uid: 60de79ca-45ae-4d1a-b45e-c687ea30e3ce resourceVersion: "27117" uid: d21bbba0-f750-4368-9fd8-8bf3cc3122a2 spec: sourcePod: network-check-source-dbd9cf844-lvdz6 targetEndpoint: ac9c951013cc642b49200c941517e5c9-a3adb1b73acacf69.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-07T19:38:34Z" message: 'load-balancer-api-external: tcp connection to ac9c951013cc642b49200c941517e5c9-a3adb1b73acacf69.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.677534ms message: 'load-balancer-api-external: tcp connection to ac9c951013cc642b49200c941517e5c9-a3adb1b73acacf69.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:44:34Z" - latency: 7.329673ms message: 'load-balancer-api-external: resolved host name ac9c951013cc642b49200c941517e5c9-a3adb1b73acacf69.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T19:44:34Z" - latency: 5.860151ms message: 'load-balancer-api-external: tcp connection to ac9c951013cc642b49200c941517e5c9-a3adb1b73acacf69.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:43:34Z" - latency: 7.133926ms message: 'load-balancer-api-external: resolved host name ac9c951013cc642b49200c941517e5c9-a3adb1b73acacf69.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T19:43:34Z" - latency: 5.480942ms message: 'load-balancer-api-external: tcp connection to ac9c951013cc642b49200c941517e5c9-a3adb1b73acacf69.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:42:34Z" - latency: 7.207728ms message: 'load-balancer-api-external: resolved host name ac9c951013cc642b49200c941517e5c9-a3adb1b73acacf69.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T19:42:34Z" - latency: 5.923376ms message: 'load-balancer-api-external: tcp connection to ac9c951013cc642b49200c941517e5c9-a3adb1b73acacf69.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:41:34Z" - latency: 6.951312ms message: 'load-balancer-api-external: resolved host name ac9c951013cc642b49200c941517e5c9-a3adb1b73acacf69.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T19:41:34Z" - latency: 5.033223ms message: 'load-balancer-api-external: tcp connection to ac9c951013cc642b49200c941517e5c9-a3adb1b73acacf69.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:40:34Z" - latency: 7.28648ms message: 'load-balancer-api-external: resolved host name ac9c951013cc642b49200c941517e5c9-a3adb1b73acacf69.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T19:40:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-07T19:32:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-58-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-58.ec2.internal uid: 60de79ca-45ae-4d1a-b45e-c687ea30e3ce resourceVersion: "27116" uid: 24631053-2c7f-4307-b8bc-4a0e5024fa9e spec: sourcePod: network-check-source-dbd9cf844-lvdz6 targetEndpoint: ac9c951013cc642b49200c941517e5c9-a3adb1b73acacf69.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-07T19:38:34Z" message: 'load-balancer-api-internal: tcp connection to ac9c951013cc642b49200c941517e5c9-a3adb1b73acacf69.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.714361ms message: 'load-balancer-api-internal: tcp connection to ac9c951013cc642b49200c941517e5c9-a3adb1b73acacf69.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:44:34Z" - latency: 7.103764ms message: 'load-balancer-api-internal: resolved host name ac9c951013cc642b49200c941517e5c9-a3adb1b73acacf69.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T19:44:34Z" - latency: 5.874283ms message: 'load-balancer-api-internal: tcp connection to ac9c951013cc642b49200c941517e5c9-a3adb1b73acacf69.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:43:34Z" - latency: 6.928643ms message: 'load-balancer-api-internal: resolved host name ac9c951013cc642b49200c941517e5c9-a3adb1b73acacf69.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T19:43:34Z" - latency: 5.514091ms message: 'load-balancer-api-internal: tcp connection to ac9c951013cc642b49200c941517e5c9-a3adb1b73acacf69.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:42:34Z" - latency: 7.146316ms message: 'load-balancer-api-internal: resolved host name ac9c951013cc642b49200c941517e5c9-a3adb1b73acacf69.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T19:42:34Z" - latency: 5.970267ms message: 'load-balancer-api-internal: tcp connection to ac9c951013cc642b49200c941517e5c9-a3adb1b73acacf69.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:41:34Z" - latency: 6.89571ms message: 'load-balancer-api-internal: resolved host name ac9c951013cc642b49200c941517e5c9-a3adb1b73acacf69.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T19:41:34Z" - latency: 5.747138ms message: 'load-balancer-api-internal: tcp connection to ac9c951013cc642b49200c941517e5c9-a3adb1b73acacf69.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:40:34Z" - latency: 7.087036ms message: 'load-balancer-api-internal: resolved host name ac9c951013cc642b49200c941517e5c9-a3adb1b73acacf69.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T19:40:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-07T19:32:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-58-to-network-check-target-ip-10-0-128-213 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-58.ec2.internal uid: 60de79ca-45ae-4d1a-b45e-c687ea30e3ce resourceVersion: "28401" uid: e904518f-1cb5-4633-ad75-91961c93012e spec: sourcePod: network-check-source-dbd9cf844-lvdz6 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-07T19:39:34Z" message: 'network-check-target-ip-10-0-128-213: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.150671ms message: 'network-check-target-ip-10-0-128-213: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:46:34Z" - latency: 2.360127ms message: 'network-check-target-ip-10-0-128-213: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:45:34Z" - latency: 2.31926ms message: 'network-check-target-ip-10-0-128-213: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:44:34Z" - latency: 2.533398ms message: 'network-check-target-ip-10-0-128-213: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:43:34Z" - latency: 2.079856ms message: 'network-check-target-ip-10-0-128-213: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:42:34Z" - latency: 2.171894ms message: 'network-check-target-ip-10-0-128-213: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:41:34Z" - latency: 2.243158ms message: 'network-check-target-ip-10-0-128-213: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:40:34Z" - latency: 2.035698ms message: 'network-check-target-ip-10-0-128-213: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:39:34Z" - latency: 3.306288ms message: 'network-check-target-ip-10-0-128-213: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:38:34Z" - latency: 2.125965ms message: 'network-check-target-ip-10-0-128-213: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:37:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-07T19:32:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-58-to-network-check-target-ip-10-0-136-40 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-58.ec2.internal uid: 60de79ca-45ae-4d1a-b45e-c687ea30e3ce resourceVersion: "28400" uid: 74a65f60-3545-4b88-8577-5adc9353628d spec: sourcePod: network-check-source-dbd9cf844-lvdz6 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-07T19:39:34Z" message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.952202ms message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:46:34Z" - latency: 2.0677ms message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:45:34Z" - latency: 1.666038ms message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:44:34Z" - latency: 1.784265ms message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:43:34Z" - latency: 1.614674ms message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:42:34Z" - latency: 2.08191ms message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:41:34Z" - latency: 1.975757ms message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:40:34Z" - latency: 1.828382ms message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:39:34Z" - latency: 3.48764ms message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:38:34Z" - latency: 1.811717ms message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:37:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-07T19:32:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-58-to-network-check-target-ip-10-0-143-58 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-58.ec2.internal uid: 60de79ca-45ae-4d1a-b45e-c687ea30e3ce resourceVersion: "28399" uid: fdeb4171-f775-45b6-a9d5-ee5bdafcfc04 spec: sourcePod: network-check-source-dbd9cf844-lvdz6 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-07T19:39:34Z" message: 'network-check-target-ip-10-0-143-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.064401ms message: 'network-check-target-ip-10-0-143-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:46:34Z" - latency: 994.498µs message: 'network-check-target-ip-10-0-143-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:45:34Z" - latency: 874.219µs message: 'network-check-target-ip-10-0-143-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:44:34Z" - latency: 1.204456ms message: 'network-check-target-ip-10-0-143-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:43:34Z" - latency: 994.27µs message: 'network-check-target-ip-10-0-143-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:42:34Z" - latency: 909.982µs message: 'network-check-target-ip-10-0-143-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:41:34Z" - latency: 881.693µs message: 'network-check-target-ip-10-0-143-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:40:34Z" - latency: 941.261µs message: 'network-check-target-ip-10-0-143-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:39:34Z" - latency: 2.489602ms message: 'network-check-target-ip-10-0-143-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:38:34Z" - latency: 809.44µs message: 'network-check-target-ip-10-0-143-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:37:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-07T19:32:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-58-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-58.ec2.internal uid: 60de79ca-45ae-4d1a-b45e-c687ea30e3ce resourceVersion: "27115" uid: 711dac57-8d45-47fc-9b77-5c42fd12c4be spec: sourcePod: network-check-source-dbd9cf844-lvdz6 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-07T19:38:34Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 846.942µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:44:34Z" - latency: 1.800904ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-07T19:44:34Z" - latency: 723.52µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:43:34Z" - latency: 1.748884ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-07T19:43:34Z" - latency: 993.563µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:42:34Z" - latency: 1.966054ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-07T19:42:34Z" - latency: 1.113553ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:41:34Z" - latency: 1.772767ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-07T19:41:34Z" - latency: 854.557µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-07T19:40:34Z" - latency: 1.966536ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-07T19:40:34Z" kind: List metadata: resourceVersion: ""