apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T02:44:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-175-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-175.ec2.internal uid: 65b41a7c-96bf-4ed2-93ad-0960315ab0ab resourceVersion: "69620" uid: 9bbee8d2-a86c-44d9-aa6b-9507af5b0178 spec: sourcePod: network-check-source-869dcfcdcd-8z5qf targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-10T02:51:09Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 920.533µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:40:09Z" - latency: 929.098µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:39:09Z" - latency: 985.001µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:38:09Z" - latency: 1.14959ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:37:09Z" - latency: 1.143106ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:36:09Z" - latency: 874.96µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:35:09Z" - latency: 1.186435ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:34:09Z" - latency: 881.48µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:33:09Z" - latency: 951.894µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:32:09Z" - latency: 1.263873ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:31:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T02:44:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-175-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-175.ec2.internal uid: 65b41a7c-96bf-4ed2-93ad-0960315ab0ab resourceVersion: "73015" uid: 647d9424-bb4b-46f9-80a8-7465e1118aef spec: sourcePod: network-check-source-869dcfcdcd-8z5qf targetEndpoint: aec77b136a4844f91bd4eb9712d64719-1e0992e256b24443.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T02:50:09Z" message: 'load-balancer-api-external: tcp connection to aec77b136a4844f91bd4eb9712d64719-1e0992e256b24443.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.585598ms message: 'load-balancer-api-external: tcp connection to aec77b136a4844f91bd4eb9712d64719-1e0992e256b24443.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:44:09Z" - latency: 7.146174ms message: 'load-balancer-api-external: resolved host name aec77b136a4844f91bd4eb9712d64719-1e0992e256b24443.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T03:44:09Z" - latency: 5.092798ms message: 'load-balancer-api-external: tcp connection to aec77b136a4844f91bd4eb9712d64719-1e0992e256b24443.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:43:09Z" - latency: 6.452279ms message: 'load-balancer-api-external: resolved host name aec77b136a4844f91bd4eb9712d64719-1e0992e256b24443.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T03:43:09Z" - latency: 3.443356ms message: 'load-balancer-api-external: tcp connection to aec77b136a4844f91bd4eb9712d64719-1e0992e256b24443.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:42:09Z" - latency: 9.590553ms message: 'load-balancer-api-external: resolved host name aec77b136a4844f91bd4eb9712d64719-1e0992e256b24443.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T03:42:09Z" - latency: 5.936239ms message: 'load-balancer-api-external: tcp connection to aec77b136a4844f91bd4eb9712d64719-1e0992e256b24443.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:41:09Z" - latency: 7.013489ms message: 'load-balancer-api-external: resolved host name aec77b136a4844f91bd4eb9712d64719-1e0992e256b24443.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T03:41:09Z" - latency: 3.438997ms message: 'load-balancer-api-external: tcp connection to aec77b136a4844f91bd4eb9712d64719-1e0992e256b24443.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:40:09Z" - latency: 7.439153ms message: 'load-balancer-api-external: resolved host name aec77b136a4844f91bd4eb9712d64719-1e0992e256b24443.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T03:40:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T02:44:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-175-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-175.ec2.internal uid: 65b41a7c-96bf-4ed2-93ad-0960315ab0ab resourceVersion: "73014" uid: cedb275c-301b-4256-8d5b-dda5155d6bc0 spec: sourcePod: network-check-source-869dcfcdcd-8z5qf targetEndpoint: aec77b136a4844f91bd4eb9712d64719-1e0992e256b24443.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T02:50:09Z" message: 'load-balancer-api-internal: tcp connection to aec77b136a4844f91bd4eb9712d64719-1e0992e256b24443.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.746986ms message: 'load-balancer-api-internal: tcp connection to aec77b136a4844f91bd4eb9712d64719-1e0992e256b24443.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:44:09Z" - latency: 7.183843ms message: 'load-balancer-api-internal: resolved host name aec77b136a4844f91bd4eb9712d64719-1e0992e256b24443.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T03:44:09Z" - latency: 5.380983ms message: 'load-balancer-api-internal: tcp connection to aec77b136a4844f91bd4eb9712d64719-1e0992e256b24443.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:43:09Z" - latency: 6.491904ms message: 'load-balancer-api-internal: resolved host name aec77b136a4844f91bd4eb9712d64719-1e0992e256b24443.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T03:43:09Z" - latency: 5.513314ms message: 'load-balancer-api-internal: tcp connection to aec77b136a4844f91bd4eb9712d64719-1e0992e256b24443.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:42:09Z" - latency: 9.552964ms message: 'load-balancer-api-internal: resolved host name aec77b136a4844f91bd4eb9712d64719-1e0992e256b24443.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T03:42:09Z" - latency: 5.889831ms message: 'load-balancer-api-internal: tcp connection to aec77b136a4844f91bd4eb9712d64719-1e0992e256b24443.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:41:09Z" - latency: 6.922626ms message: 'load-balancer-api-internal: resolved host name aec77b136a4844f91bd4eb9712d64719-1e0992e256b24443.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T03:41:09Z" - latency: 3.366307ms message: 'load-balancer-api-internal: tcp connection to aec77b136a4844f91bd4eb9712d64719-1e0992e256b24443.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:40:09Z" - latency: 7.400904ms message: 'load-balancer-api-internal: resolved host name aec77b136a4844f91bd4eb9712d64719-1e0992e256b24443.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T03:40:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T02:44:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-175-to-network-check-target-ip-10-0-136-90 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-175.ec2.internal uid: 65b41a7c-96bf-4ed2-93ad-0960315ab0ab resourceVersion: "69618" uid: ac602d1b-8d1e-4706-abe2-f363782d5dd2 spec: sourcePod: network-check-source-869dcfcdcd-8z5qf targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-10T02:51:09Z" message: 'network-check-target-ip-10-0-136-90: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.13733ms message: 'network-check-target-ip-10-0-136-90: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:40:09Z" - latency: 2.392373ms message: 'network-check-target-ip-10-0-136-90: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:39:09Z" - latency: 2.027172ms message: 'network-check-target-ip-10-0-136-90: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:38:09Z" - latency: 2.366191ms message: 'network-check-target-ip-10-0-136-90: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:37:09Z" - latency: 2.466366ms message: 'network-check-target-ip-10-0-136-90: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:36:09Z" - latency: 2.569094ms message: 'network-check-target-ip-10-0-136-90: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:35:09Z" - latency: 2.194759ms message: 'network-check-target-ip-10-0-136-90: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:34:09Z" - latency: 2.28856ms message: 'network-check-target-ip-10-0-136-90: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:33:09Z" - latency: 2.271843ms message: 'network-check-target-ip-10-0-136-90: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:32:09Z" - latency: 2.128826ms message: 'network-check-target-ip-10-0-136-90: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:31:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T02:44:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-175-to-network-check-target-ip-10-0-139-175 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-175.ec2.internal uid: 65b41a7c-96bf-4ed2-93ad-0960315ab0ab resourceVersion: "69617" uid: 0d000669-6b9d-4679-976b-bfc03fcdfc3e spec: sourcePod: network-check-source-869dcfcdcd-8z5qf targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-10T02:51:09Z" message: 'network-check-target-ip-10-0-139-175: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 994.728µs message: 'network-check-target-ip-10-0-139-175: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:40:09Z" - latency: 865.218µs message: 'network-check-target-ip-10-0-139-175: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:39:09Z" - latency: 977.413µs message: 'network-check-target-ip-10-0-139-175: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:38:09Z" - latency: 941.857µs message: 'network-check-target-ip-10-0-139-175: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:37:09Z" - latency: 994.842µs message: 'network-check-target-ip-10-0-139-175: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:36:09Z" - latency: 1.102123ms message: 'network-check-target-ip-10-0-139-175: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:35:09Z" - latency: 951.934µs message: 'network-check-target-ip-10-0-139-175: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:34:09Z" - latency: 822.78µs message: 'network-check-target-ip-10-0-139-175: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:33:09Z" - latency: 936.864µs message: 'network-check-target-ip-10-0-139-175: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:32:09Z" - latency: 925.516µs message: 'network-check-target-ip-10-0-139-175: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:31:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T02:44:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-175-to-network-check-target-ip-10-0-143-93 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-175.ec2.internal uid: 65b41a7c-96bf-4ed2-93ad-0960315ab0ab resourceVersion: "69619" uid: f4653707-c739-4c51-b6ef-92e3109bb43b spec: sourcePod: network-check-source-869dcfcdcd-8z5qf targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-10T02:51:09Z" message: 'network-check-target-ip-10-0-143-93: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.052082ms message: 'network-check-target-ip-10-0-143-93: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:40:09Z" - latency: 1.906231ms message: 'network-check-target-ip-10-0-143-93: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:39:09Z" - latency: 1.697073ms message: 'network-check-target-ip-10-0-143-93: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:38:09Z" - latency: 2.156785ms message: 'network-check-target-ip-10-0-143-93: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:37:09Z" - latency: 2.08169ms message: 'network-check-target-ip-10-0-143-93: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:36:09Z" - latency: 1.725046ms message: 'network-check-target-ip-10-0-143-93: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:35:09Z" - latency: 2.215461ms message: 'network-check-target-ip-10-0-143-93: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:34:09Z" - latency: 2.208664ms message: 'network-check-target-ip-10-0-143-93: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:33:09Z" - latency: 1.967529ms message: 'network-check-target-ip-10-0-143-93: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:32:09Z" - latency: 2.120325ms message: 'network-check-target-ip-10-0-143-93: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:31:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T02:44:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-175-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-175.ec2.internal uid: 65b41a7c-96bf-4ed2-93ad-0960315ab0ab resourceVersion: "73013" uid: ffd9f3b0-4dba-4813-8645-67933c18a706 spec: sourcePod: network-check-source-869dcfcdcd-8z5qf targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-10T02:50:09Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.1995ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:44:09Z" - latency: 1.838325ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T03:44:09Z" - latency: 1.252993ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:43:09Z" - latency: 1.850351ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T03:43:09Z" - latency: 1.30794ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:42:09Z" - latency: 1.723747ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T03:42:09Z" - latency: 894.937µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:41:09Z" - latency: 2.232193ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T03:41:09Z" - latency: 1.280678ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:40:09Z" - latency: 1.921181ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T03:40:09Z" kind: List metadata: resourceVersion: ""