apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T15:09:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-218-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-218.ec2.internal uid: 6a0ae1d1-dcb0-4e76-901a-c0ee449bc8ac resourceVersion: "65338" uid: a170c436-cdb9-44e4-b272-d15bb1bc783e spec: sourcePod: network-check-source-7d88cb55d8-mpgd6 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-27T15:16:33Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.11928ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:58:33Z" - latency: 1.200943ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:57:33Z" - latency: 1.165491ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:56:33Z" - latency: 1.26544ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:55:33Z" - latency: 999.493µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:54:33Z" - latency: 834.128µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:53:33Z" - latency: 821.163µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:52:33Z" - latency: 848.076µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:51:33Z" - latency: 1.078138ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:50:33Z" - latency: 1.374655ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:49:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T15:09:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-218-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-218.ec2.internal uid: 6a0ae1d1-dcb0-4e76-901a-c0ee449bc8ac resourceVersion: "63149" uid: f9d19519-66bb-4422-8926-71ea9627ff71 spec: sourcePod: network-check-source-7d88cb55d8-mpgd6 targetEndpoint: aec4395a0df5348538f12988908e86f1-d9d3b76b8a75332a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T15:15:33Z" message: 'load-balancer-api-external: tcp connection to aec4395a0df5348538f12988908e86f1-d9d3b76b8a75332a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.811869ms message: 'load-balancer-api-external: tcp connection to aec4395a0df5348538f12988908e86f1-d9d3b76b8a75332a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:57:33Z" - latency: 7.939661ms message: 'load-balancer-api-external: resolved host name aec4395a0df5348538f12988908e86f1-d9d3b76b8a75332a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T15:57:33Z" - latency: 4.337952ms message: 'load-balancer-api-external: tcp connection to aec4395a0df5348538f12988908e86f1-d9d3b76b8a75332a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:56:33Z" - latency: 6.60356ms message: 'load-balancer-api-external: resolved host name aec4395a0df5348538f12988908e86f1-d9d3b76b8a75332a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T15:56:33Z" - latency: 4.304598ms message: 'load-balancer-api-external: tcp connection to aec4395a0df5348538f12988908e86f1-d9d3b76b8a75332a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:55:33Z" - latency: 7.084632ms message: 'load-balancer-api-external: resolved host name aec4395a0df5348538f12988908e86f1-d9d3b76b8a75332a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T15:55:33Z" - latency: 4.248734ms message: 'load-balancer-api-external: tcp connection to aec4395a0df5348538f12988908e86f1-d9d3b76b8a75332a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:54:33Z" - latency: 7.048579ms message: 'load-balancer-api-external: resolved host name aec4395a0df5348538f12988908e86f1-d9d3b76b8a75332a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T15:54:33Z" - latency: 3.765673ms message: 'load-balancer-api-external: tcp connection to aec4395a0df5348538f12988908e86f1-d9d3b76b8a75332a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:53:33Z" - latency: 6.846015ms message: 'load-balancer-api-external: resolved host name aec4395a0df5348538f12988908e86f1-d9d3b76b8a75332a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T15:53:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T15:09:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-218-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-218.ec2.internal uid: 6a0ae1d1-dcb0-4e76-901a-c0ee449bc8ac resourceVersion: "63150" uid: 299da9a2-faa8-48e4-a490-f6333289c92b spec: sourcePod: network-check-source-7d88cb55d8-mpgd6 targetEndpoint: aec4395a0df5348538f12988908e86f1-d9d3b76b8a75332a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T15:15:33Z" message: 'load-balancer-api-internal: tcp connection to aec4395a0df5348538f12988908e86f1-d9d3b76b8a75332a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.82526ms message: 'load-balancer-api-internal: tcp connection to aec4395a0df5348538f12988908e86f1-d9d3b76b8a75332a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:57:33Z" - latency: 7.984128ms message: 'load-balancer-api-internal: resolved host name aec4395a0df5348538f12988908e86f1-d9d3b76b8a75332a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T15:57:33Z" - latency: 4.36481ms message: 'load-balancer-api-internal: tcp connection to aec4395a0df5348538f12988908e86f1-d9d3b76b8a75332a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:56:33Z" - latency: 6.512934ms message: 'load-balancer-api-internal: resolved host name aec4395a0df5348538f12988908e86f1-d9d3b76b8a75332a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T15:56:33Z" - latency: 4.271358ms message: 'load-balancer-api-internal: tcp connection to aec4395a0df5348538f12988908e86f1-d9d3b76b8a75332a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:55:33Z" - latency: 7.114376ms message: 'load-balancer-api-internal: resolved host name aec4395a0df5348538f12988908e86f1-d9d3b76b8a75332a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T15:55:33Z" - latency: 4.100613ms message: 'load-balancer-api-internal: tcp connection to aec4395a0df5348538f12988908e86f1-d9d3b76b8a75332a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:54:33Z" - latency: 7.139827ms message: 'load-balancer-api-internal: resolved host name aec4395a0df5348538f12988908e86f1-d9d3b76b8a75332a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T15:54:33Z" - latency: 4.575996ms message: 'load-balancer-api-internal: tcp connection to aec4395a0df5348538f12988908e86f1-d9d3b76b8a75332a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:53:33Z" - latency: 6.937533ms message: 'load-balancer-api-internal: resolved host name aec4395a0df5348538f12988908e86f1-d9d3b76b8a75332a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T15:53:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T15:09:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-218-to-network-check-target-ip-10-0-135-218 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-218.ec2.internal uid: 6a0ae1d1-dcb0-4e76-901a-c0ee449bc8ac resourceVersion: "65336" uid: 0e9675c0-87ef-4911-8068-28bc12781892 spec: sourcePod: network-check-source-7d88cb55d8-mpgd6 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-27T15:16:33Z" message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.278052ms message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:58:33Z" - latency: 1.36514ms message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:57:33Z" - latency: 953.298µs message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:56:33Z" - latency: 973.008µs message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:55:33Z" - latency: 1.070332ms message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:54:33Z" - latency: 825.154µs message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:53:33Z" - latency: 911.113µs message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:52:33Z" - latency: 1.316246ms message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:51:33Z" - latency: 813.005µs message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:50:33Z" - latency: 1.545671ms message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:49:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T15:09:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-218-to-network-check-target-ip-10-0-143-164 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-218.ec2.internal uid: 6a0ae1d1-dcb0-4e76-901a-c0ee449bc8ac resourceVersion: "65335" uid: e7828ce5-ae6a-47fc-a8d9-0d8248176e53 spec: sourcePod: network-check-source-7d88cb55d8-mpgd6 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-27T15:16:33Z" message: 'network-check-target-ip-10-0-143-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.138787ms message: 'network-check-target-ip-10-0-143-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:58:33Z" - latency: 1.96444ms message: 'network-check-target-ip-10-0-143-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:57:33Z" - latency: 2.646363ms message: 'network-check-target-ip-10-0-143-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:56:33Z" - latency: 2.465175ms message: 'network-check-target-ip-10-0-143-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:55:33Z" - latency: 2.219521ms message: 'network-check-target-ip-10-0-143-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:54:33Z" - latency: 1.895528ms message: 'network-check-target-ip-10-0-143-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:53:33Z" - latency: 2.38861ms message: 'network-check-target-ip-10-0-143-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:52:33Z" - latency: 1.704077ms message: 'network-check-target-ip-10-0-143-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:51:33Z" - latency: 2.37075ms message: 'network-check-target-ip-10-0-143-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:50:33Z" - latency: 2.518742ms message: 'network-check-target-ip-10-0-143-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:49:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T15:09:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-218-to-network-check-target-ip-10-0-143-46 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-218.ec2.internal uid: 6a0ae1d1-dcb0-4e76-901a-c0ee449bc8ac resourceVersion: "65337" uid: 3ac72aaf-b73c-43dc-907c-60a441156610 spec: sourcePod: network-check-source-7d88cb55d8-mpgd6 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-27T15:16:33Z" message: 'network-check-target-ip-10-0-143-46: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.551201ms message: 'network-check-target-ip-10-0-143-46: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:58:33Z" - latency: 2.316565ms message: 'network-check-target-ip-10-0-143-46: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:57:33Z" - latency: 2.307235ms message: 'network-check-target-ip-10-0-143-46: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:56:33Z" - latency: 1.826812ms message: 'network-check-target-ip-10-0-143-46: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:55:33Z" - latency: 2.23198ms message: 'network-check-target-ip-10-0-143-46: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:54:33Z" - latency: 2.123648ms message: 'network-check-target-ip-10-0-143-46: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:53:33Z" - latency: 2.35264ms message: 'network-check-target-ip-10-0-143-46: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:52:33Z" - latency: 2.187139ms message: 'network-check-target-ip-10-0-143-46: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:51:33Z" - latency: 2.294692ms message: 'network-check-target-ip-10-0-143-46: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:50:33Z" - latency: 2.595494ms message: 'network-check-target-ip-10-0-143-46: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:49:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T15:09:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-218-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-218.ec2.internal uid: 6a0ae1d1-dcb0-4e76-901a-c0ee449bc8ac resourceVersion: "63148" uid: bcc0877f-d93f-4c21-8776-04f9365ff369 spec: sourcePod: network-check-source-7d88cb55d8-mpgd6 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-27T15:15:33Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.11456ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:57:33Z" - latency: 1.698158ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T15:57:33Z" - latency: 1.43856ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:56:33Z" - latency: 1.812687ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T15:56:33Z" - latency: 837.645µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:55:33Z" - latency: 1.834405ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T15:55:33Z" - latency: 926.092µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:54:33Z" - latency: 1.778392ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T15:54:33Z" - latency: 781.978µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T15:53:33Z" - latency: 1.562837ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T15:53:33Z" kind: List metadata: resourceVersion: ""