apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T19:05:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-32-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-32.ec2.internal uid: 3b441369-231f-4a21-832c-c54fa6e1a32e resourceVersion: "53778" uid: ae5f257b-6fd7-4a2e-9c7a-ed4ee059230e spec: sourcePod: network-check-source-989f8b8dc-sgmv7 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-02T19:12:45Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 966.661µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:40:45Z" - latency: 1.010811ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:39:45Z" - latency: 979.088µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:38:45Z" - latency: 1.056359ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:37:45Z" - latency: 995.42µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:36:45Z" - latency: 1.196056ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:35:45Z" - latency: 1.084512ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:34:45Z" - latency: 1.055287ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:33:45Z" - latency: 953.738µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:32:45Z" - latency: 1.684138ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:31:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T19:05:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-32-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-32.ec2.internal uid: 3b441369-231f-4a21-832c-c54fa6e1a32e resourceVersion: "54655" uid: 97db5e11-65a3-4864-b79f-9aee9c4e98db spec: sourcePod: network-check-source-989f8b8dc-sgmv7 targetEndpoint: a9bad92de7dad4461aa6de28338a8e08-9e47079a13e68e90.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T19:11:45Z" message: 'load-balancer-api-external: tcp connection to a9bad92de7dad4461aa6de28338a8e08-9e47079a13e68e90.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.295779ms message: 'load-balancer-api-external: tcp connection to a9bad92de7dad4461aa6de28338a8e08-9e47079a13e68e90.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:41:45Z" - latency: 8.750185ms message: 'load-balancer-api-external: resolved host name a9bad92de7dad4461aa6de28338a8e08-9e47079a13e68e90.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:41:45Z" - latency: 4.946442ms message: 'load-balancer-api-external: tcp connection to a9bad92de7dad4461aa6de28338a8e08-9e47079a13e68e90.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:40:45Z" - latency: 8.335925ms message: 'load-balancer-api-external: resolved host name a9bad92de7dad4461aa6de28338a8e08-9e47079a13e68e90.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:40:45Z" - latency: 4.125841ms message: 'load-balancer-api-external: tcp connection to a9bad92de7dad4461aa6de28338a8e08-9e47079a13e68e90.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:39:45Z" - latency: 6.872118ms message: 'load-balancer-api-external: resolved host name a9bad92de7dad4461aa6de28338a8e08-9e47079a13e68e90.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:39:45Z" - latency: 5.835551ms message: 'load-balancer-api-external: tcp connection to a9bad92de7dad4461aa6de28338a8e08-9e47079a13e68e90.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:38:45Z" - latency: 7.87745ms message: 'load-balancer-api-external: resolved host name a9bad92de7dad4461aa6de28338a8e08-9e47079a13e68e90.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:38:45Z" - latency: 4.596796ms message: 'load-balancer-api-external: tcp connection to a9bad92de7dad4461aa6de28338a8e08-9e47079a13e68e90.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:37:45Z" - latency: 7.981089ms message: 'load-balancer-api-external: resolved host name a9bad92de7dad4461aa6de28338a8e08-9e47079a13e68e90.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:37:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T19:05:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-32-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-32.ec2.internal uid: 3b441369-231f-4a21-832c-c54fa6e1a32e resourceVersion: "54654" uid: ab36c7db-c11f-44f1-bfcd-3864d17f3daa spec: sourcePod: network-check-source-989f8b8dc-sgmv7 targetEndpoint: a9bad92de7dad4461aa6de28338a8e08-9e47079a13e68e90.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T19:11:45Z" message: 'load-balancer-api-internal: tcp connection to a9bad92de7dad4461aa6de28338a8e08-9e47079a13e68e90.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.603049ms message: 'load-balancer-api-internal: tcp connection to a9bad92de7dad4461aa6de28338a8e08-9e47079a13e68e90.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:41:45Z" - latency: 8.845599ms message: 'load-balancer-api-internal: resolved host name a9bad92de7dad4461aa6de28338a8e08-9e47079a13e68e90.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:41:45Z" - latency: 4.137983ms message: 'load-balancer-api-internal: tcp connection to a9bad92de7dad4461aa6de28338a8e08-9e47079a13e68e90.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:40:45Z" - latency: 8.421155ms message: 'load-balancer-api-internal: resolved host name a9bad92de7dad4461aa6de28338a8e08-9e47079a13e68e90.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:40:45Z" - latency: 3.899149ms message: 'load-balancer-api-internal: tcp connection to a9bad92de7dad4461aa6de28338a8e08-9e47079a13e68e90.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:39:45Z" - latency: 6.739488ms message: 'load-balancer-api-internal: resolved host name a9bad92de7dad4461aa6de28338a8e08-9e47079a13e68e90.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:39:45Z" - latency: 5.797295ms message: 'load-balancer-api-internal: tcp connection to a9bad92de7dad4461aa6de28338a8e08-9e47079a13e68e90.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:38:45Z" - latency: 7.929121ms message: 'load-balancer-api-internal: resolved host name a9bad92de7dad4461aa6de28338a8e08-9e47079a13e68e90.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:38:45Z" - latency: 4.397708ms message: 'load-balancer-api-internal: tcp connection to a9bad92de7dad4461aa6de28338a8e08-9e47079a13e68e90.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:37:45Z" - latency: 8.04206ms message: 'load-balancer-api-internal: resolved host name a9bad92de7dad4461aa6de28338a8e08-9e47079a13e68e90.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T19:37:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T19:05:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-32-to-network-check-target-ip-10-0-135-32 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-32.ec2.internal uid: 3b441369-231f-4a21-832c-c54fa6e1a32e resourceVersion: "53775" uid: 02356ac0-5361-47f9-9e26-d0225c64b7f1 spec: sourcePod: network-check-source-989f8b8dc-sgmv7 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-02T19:12:45Z" message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.083435ms message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:40:45Z" - latency: 967.171µs message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:39:45Z" - latency: 929.205µs message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:38:45Z" - latency: 914.455µs message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:37:45Z" - latency: 977.276µs message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:36:45Z" - latency: 1.505119ms message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:35:45Z" - latency: 892.558µs message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:34:45Z" - latency: 949.325µs message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:33:45Z" - latency: 878.451µs message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:32:45Z" - latency: 1.294938ms message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:31:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T19:05:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-32-to-network-check-target-ip-10-0-138-101 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-32.ec2.internal uid: 3b441369-231f-4a21-832c-c54fa6e1a32e resourceVersion: "53776" uid: 5c4e1889-8676-454e-8f42-cbba81fb1a5c spec: sourcePod: network-check-source-989f8b8dc-sgmv7 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-02T19:12:45Z" message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.396091ms message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:40:45Z" - latency: 2.632969ms message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:39:45Z" - latency: 2.290356ms message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:38:45Z" - latency: 2.273777ms message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:37:45Z" - latency: 2.595971ms message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:36:45Z" - latency: 2.338366ms message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:35:45Z" - latency: 2.335458ms message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:34:45Z" - latency: 2.453549ms message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:33:45Z" - latency: 2.385829ms message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:32:45Z" - latency: 3.267488ms message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:31:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T19:05:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-32-to-network-check-target-ip-10-0-142-150 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-32.ec2.internal uid: 3b441369-231f-4a21-832c-c54fa6e1a32e resourceVersion: "53777" uid: ff653da9-1059-43c7-89b6-988b8c838984 spec: sourcePod: network-check-source-989f8b8dc-sgmv7 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-02T19:12:45Z" message: 'network-check-target-ip-10-0-142-150: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.041295ms message: 'network-check-target-ip-10-0-142-150: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:40:45Z" - latency: 1.926962ms message: 'network-check-target-ip-10-0-142-150: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:39:45Z" - latency: 2.13334ms message: 'network-check-target-ip-10-0-142-150: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:38:45Z" - latency: 2.130904ms message: 'network-check-target-ip-10-0-142-150: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:37:45Z" - latency: 2.231099ms message: 'network-check-target-ip-10-0-142-150: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:36:45Z" - latency: 2.050531ms message: 'network-check-target-ip-10-0-142-150: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:35:45Z" - latency: 1.943579ms message: 'network-check-target-ip-10-0-142-150: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:34:45Z" - latency: 2.913265ms message: 'network-check-target-ip-10-0-142-150: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:33:45Z" - latency: 2.189274ms message: 'network-check-target-ip-10-0-142-150: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:32:45Z" - latency: 2.123237ms message: 'network-check-target-ip-10-0-142-150: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:31:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T19:05:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-32-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-32.ec2.internal uid: 3b441369-231f-4a21-832c-c54fa6e1a32e resourceVersion: "54653" uid: 478655b3-e319-44aa-a91e-20f3feb0d895 spec: sourcePod: network-check-source-989f8b8dc-sgmv7 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-02T19:11:45Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.070886ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:41:45Z" - latency: 1.676908ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T19:41:45Z" - latency: 789.438µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:40:45Z" - latency: 1.954881ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T19:40:45Z" - latency: 864.649µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:39:45Z" - latency: 1.636606ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T19:39:45Z" - latency: 983.041µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:38:45Z" - latency: 1.69126ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T19:38:45Z" - latency: 1.052383ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T19:37:45Z" - latency: 1.853036ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T19:37:45Z" kind: List metadata: resourceVersion: ""