apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T16:42:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-50-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-50.ec2.internal uid: 49c26d79-8172-4f5c-ba11-203d6a25306f resourceVersion: "61529" uid: 8251dbbe-4638-49d2-942e-3d0dd74666dd spec: sourcePod: network-check-source-869dcfcdcd-lwqgf targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-10T16:49:58Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.193708ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:24:58Z" - latency: 1.151568ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:23:58Z" - latency: 1.055473ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:22:58Z" - latency: 1.171575ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:21:58Z" - latency: 1.080167ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:20:58Z" - latency: 888.282µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:19:58Z" - latency: 1.126831ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:18:58Z" - latency: 951.113µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:17:58Z" - latency: 829.565µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:16:58Z" - latency: 888.568µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:15:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T16:42:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-50-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-50.ec2.internal uid: 49c26d79-8172-4f5c-ba11-203d6a25306f resourceVersion: "61531" uid: 97dd8e09-6348-4452-8a6e-e6746c12aa2f spec: sourcePod: network-check-source-869dcfcdcd-lwqgf targetEndpoint: a03912316b7b548b583c96b33b3a872e-05bc7ac406d06760.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T16:48:58Z" message: 'load-balancer-api-external: tcp connection to a03912316b7b548b583c96b33b3a872e-05bc7ac406d06760.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.232401ms message: 'load-balancer-api-external: tcp connection to a03912316b7b548b583c96b33b3a872e-05bc7ac406d06760.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:24:58Z" - latency: 6.932053ms message: 'load-balancer-api-external: resolved host name a03912316b7b548b583c96b33b3a872e-05bc7ac406d06760.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T17:24:58Z" - latency: 3.326327ms message: 'load-balancer-api-external: tcp connection to a03912316b7b548b583c96b33b3a872e-05bc7ac406d06760.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:23:58Z" - latency: 8.285862ms message: 'load-balancer-api-external: resolved host name a03912316b7b548b583c96b33b3a872e-05bc7ac406d06760.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T17:23:58Z" - latency: 3.241423ms message: 'load-balancer-api-external: tcp connection to a03912316b7b548b583c96b33b3a872e-05bc7ac406d06760.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:22:58Z" - latency: 8.050809ms message: 'load-balancer-api-external: resolved host name a03912316b7b548b583c96b33b3a872e-05bc7ac406d06760.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T17:22:58Z" - latency: 4.335308ms message: 'load-balancer-api-external: tcp connection to a03912316b7b548b583c96b33b3a872e-05bc7ac406d06760.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:21:58Z" - latency: 6.942228ms message: 'load-balancer-api-external: resolved host name a03912316b7b548b583c96b33b3a872e-05bc7ac406d06760.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T17:21:58Z" - latency: 5.674656ms message: 'load-balancer-api-external: tcp connection to a03912316b7b548b583c96b33b3a872e-05bc7ac406d06760.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:20:58Z" - latency: 7.231109ms message: 'load-balancer-api-external: resolved host name a03912316b7b548b583c96b33b3a872e-05bc7ac406d06760.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T17:20:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T16:42:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-50-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-50.ec2.internal uid: 49c26d79-8172-4f5c-ba11-203d6a25306f resourceVersion: "61530" uid: 484a7b35-ad78-48c4-bb40-0ff903ed9250 spec: sourcePod: network-check-source-869dcfcdcd-lwqgf targetEndpoint: a03912316b7b548b583c96b33b3a872e-05bc7ac406d06760.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T16:48:58Z" message: 'load-balancer-api-internal: tcp connection to a03912316b7b548b583c96b33b3a872e-05bc7ac406d06760.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.502691ms message: 'load-balancer-api-internal: tcp connection to a03912316b7b548b583c96b33b3a872e-05bc7ac406d06760.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:24:58Z" - latency: 6.879298ms message: 'load-balancer-api-internal: resolved host name a03912316b7b548b583c96b33b3a872e-05bc7ac406d06760.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T17:24:58Z" - latency: 3.335652ms message: 'load-balancer-api-internal: tcp connection to a03912316b7b548b583c96b33b3a872e-05bc7ac406d06760.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:23:58Z" - latency: 8.372555ms message: 'load-balancer-api-internal: resolved host name a03912316b7b548b583c96b33b3a872e-05bc7ac406d06760.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T17:23:58Z" - latency: 3.225488ms message: 'load-balancer-api-internal: tcp connection to a03912316b7b548b583c96b33b3a872e-05bc7ac406d06760.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:22:58Z" - latency: 8.021102ms message: 'load-balancer-api-internal: resolved host name a03912316b7b548b583c96b33b3a872e-05bc7ac406d06760.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T17:22:58Z" - latency: 4.332211ms message: 'load-balancer-api-internal: tcp connection to a03912316b7b548b583c96b33b3a872e-05bc7ac406d06760.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:21:58Z" - latency: 6.971996ms message: 'load-balancer-api-internal: resolved host name a03912316b7b548b583c96b33b3a872e-05bc7ac406d06760.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T17:21:58Z" - latency: 4.842796ms message: 'load-balancer-api-internal: tcp connection to a03912316b7b548b583c96b33b3a872e-05bc7ac406d06760.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:20:58Z" - latency: 7.154152ms message: 'load-balancer-api-internal: resolved host name a03912316b7b548b583c96b33b3a872e-05bc7ac406d06760.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T17:20:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T16:42:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-50-to-network-check-target-ip-10-0-131-107 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-50.ec2.internal uid: 49c26d79-8172-4f5c-ba11-203d6a25306f resourceVersion: "61526" uid: a68204dd-59f2-428c-b8f6-c8d26d277987 spec: sourcePod: network-check-source-869dcfcdcd-lwqgf targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-10T16:49:58Z" message: 'network-check-target-ip-10-0-131-107: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.25818ms message: 'network-check-target-ip-10-0-131-107: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:24:58Z" - latency: 2.752331ms message: 'network-check-target-ip-10-0-131-107: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:23:58Z" - latency: 2.472723ms message: 'network-check-target-ip-10-0-131-107: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:22:58Z" - latency: 2.171988ms message: 'network-check-target-ip-10-0-131-107: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:21:58Z" - latency: 2.222448ms message: 'network-check-target-ip-10-0-131-107: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:20:58Z" - latency: 2.236375ms message: 'network-check-target-ip-10-0-131-107: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:19:58Z" - latency: 2.451596ms message: 'network-check-target-ip-10-0-131-107: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:18:58Z" - latency: 2.194581ms message: 'network-check-target-ip-10-0-131-107: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:17:58Z" - latency: 2.210441ms message: 'network-check-target-ip-10-0-131-107: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:16:58Z" - latency: 2.073199ms message: 'network-check-target-ip-10-0-131-107: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:15:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T16:42:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-50-to-network-check-target-ip-10-0-134-41 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-50.ec2.internal uid: 49c26d79-8172-4f5c-ba11-203d6a25306f resourceVersion: "61527" uid: 8a970e9b-c8f2-4393-bac5-24e6b48c3ffd spec: sourcePod: network-check-source-869dcfcdcd-lwqgf targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-10T16:49:58Z" message: 'network-check-target-ip-10-0-134-41: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.959496ms message: 'network-check-target-ip-10-0-134-41: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:24:58Z" - latency: 2.385502ms message: 'network-check-target-ip-10-0-134-41: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:23:58Z" - latency: 2.341295ms message: 'network-check-target-ip-10-0-134-41: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:22:58Z" - latency: 2.273716ms message: 'network-check-target-ip-10-0-134-41: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:21:58Z" - latency: 2.135426ms message: 'network-check-target-ip-10-0-134-41: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:20:58Z" - latency: 1.773622ms message: 'network-check-target-ip-10-0-134-41: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:19:58Z" - latency: 2.564408ms message: 'network-check-target-ip-10-0-134-41: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:18:58Z" - latency: 2.232171ms message: 'network-check-target-ip-10-0-134-41: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:17:58Z" - latency: 2.433192ms message: 'network-check-target-ip-10-0-134-41: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:16:58Z" - latency: 2.318541ms message: 'network-check-target-ip-10-0-134-41: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:15:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T16:42:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-50-to-network-check-target-ip-10-0-137-50 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-50.ec2.internal uid: 49c26d79-8172-4f5c-ba11-203d6a25306f resourceVersion: "61525" uid: dc48d354-3522-42cf-8ac9-febf45147c2e spec: sourcePod: network-check-source-869dcfcdcd-lwqgf targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-10T16:49:58Z" message: 'network-check-target-ip-10-0-137-50: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 886.792µs message: 'network-check-target-ip-10-0-137-50: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:24:58Z" - latency: 1.415431ms message: 'network-check-target-ip-10-0-137-50: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:23:58Z" - latency: 915.79µs message: 'network-check-target-ip-10-0-137-50: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:22:58Z" - latency: 894.248µs message: 'network-check-target-ip-10-0-137-50: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:21:58Z" - latency: 888.243µs message: 'network-check-target-ip-10-0-137-50: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:20:58Z" - latency: 832.463µs message: 'network-check-target-ip-10-0-137-50: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:19:58Z" - latency: 1.023189ms message: 'network-check-target-ip-10-0-137-50: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:18:58Z" - latency: 963.414µs message: 'network-check-target-ip-10-0-137-50: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:17:58Z" - latency: 891.518µs message: 'network-check-target-ip-10-0-137-50: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:16:58Z" - latency: 1.554295ms message: 'network-check-target-ip-10-0-137-50: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:15:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T16:42:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-50-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-50.ec2.internal uid: 49c26d79-8172-4f5c-ba11-203d6a25306f resourceVersion: "61528" uid: a3b459e6-33be-4d59-8bf3-f8c7e6be25ab spec: sourcePod: network-check-source-869dcfcdcd-lwqgf targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-10T16:48:58Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 779.041µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:24:58Z" - latency: 1.830542ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T17:24:58Z" - latency: 1.344435ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:23:58Z" - latency: 1.67451ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T17:23:58Z" - latency: 831.785µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:22:58Z" - latency: 1.56145ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T17:22:58Z" - latency: 851.844µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:21:58Z" - latency: 1.602677ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T17:21:58Z" - latency: 859.616µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:20:58Z" - latency: 2.03366ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T17:20:58Z" kind: List metadata: resourceVersion: ""