apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T20:28:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-228-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-228.ec2.internal uid: b1b2f103-8e27-475c-889a-5992e855f17d resourceVersion: "84293" uid: 4a08dbda-d0ff-428b-a1cc-f6f9d36308de spec: sourcePod: network-check-source-7d88cb55d8-lxbhh targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-29T20:35:15Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 876.011µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:38:15Z" - latency: 995.991µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:37:15Z" - latency: 1.038513ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:36:15Z" - latency: 970.438µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:35:15Z" - latency: 1.110992ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:34:15Z" - latency: 916.616µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:33:15Z" - latency: 1.225398ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:32:15Z" - latency: 1.170948ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:31:15Z" - latency: 1.394868ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:30:15Z" - latency: 1.178674ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:29:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T20:28:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-228-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-228.ec2.internal uid: b1b2f103-8e27-475c-889a-5992e855f17d resourceVersion: "85959" uid: 507e878f-defa-4a8f-831f-e7e68b2554f8 spec: sourcePod: network-check-source-7d88cb55d8-lxbhh targetEndpoint: a225e1495ba1f4ae5ab07f0498634351-f3c1a27e5acdd0f1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T20:34:15Z" message: 'load-balancer-api-external: tcp connection to a225e1495ba1f4ae5ab07f0498634351-f3c1a27e5acdd0f1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.107315ms message: 'load-balancer-api-external: tcp connection to a225e1495ba1f4ae5ab07f0498634351-f3c1a27e5acdd0f1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:40:15Z" - latency: 6.664174ms message: 'load-balancer-api-external: resolved host name a225e1495ba1f4ae5ab07f0498634351-f3c1a27e5acdd0f1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T21:40:15Z" - latency: 6.691423ms message: 'load-balancer-api-external: tcp connection to a225e1495ba1f4ae5ab07f0498634351-f3c1a27e5acdd0f1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:39:15Z" - latency: 7.682834ms message: 'load-balancer-api-external: resolved host name a225e1495ba1f4ae5ab07f0498634351-f3c1a27e5acdd0f1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T21:39:15Z" - latency: 5.273373ms message: 'load-balancer-api-external: tcp connection to a225e1495ba1f4ae5ab07f0498634351-f3c1a27e5acdd0f1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:38:15Z" - latency: 8.104488ms message: 'load-balancer-api-external: resolved host name a225e1495ba1f4ae5ab07f0498634351-f3c1a27e5acdd0f1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T21:38:15Z" - latency: 3.422808ms message: 'load-balancer-api-external: tcp connection to a225e1495ba1f4ae5ab07f0498634351-f3c1a27e5acdd0f1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:37:15Z" - latency: 7.316201ms message: 'load-balancer-api-external: resolved host name a225e1495ba1f4ae5ab07f0498634351-f3c1a27e5acdd0f1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T21:37:15Z" - latency: 4.584011ms message: 'load-balancer-api-external: tcp connection to a225e1495ba1f4ae5ab07f0498634351-f3c1a27e5acdd0f1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:36:15Z" - latency: 7.158299ms message: 'load-balancer-api-external: resolved host name a225e1495ba1f4ae5ab07f0498634351-f3c1a27e5acdd0f1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T21:36:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T20:28:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-228-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-228.ec2.internal uid: b1b2f103-8e27-475c-889a-5992e855f17d resourceVersion: "85958" uid: 78d8c63a-d522-4063-8ea6-059c322a7ec4 spec: sourcePod: network-check-source-7d88cb55d8-lxbhh targetEndpoint: a225e1495ba1f4ae5ab07f0498634351-f3c1a27e5acdd0f1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T20:34:15Z" message: 'load-balancer-api-internal: tcp connection to a225e1495ba1f4ae5ab07f0498634351-f3c1a27e5acdd0f1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.559755ms message: 'load-balancer-api-internal: tcp connection to a225e1495ba1f4ae5ab07f0498634351-f3c1a27e5acdd0f1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:40:15Z" - latency: 6.712739ms message: 'load-balancer-api-internal: resolved host name a225e1495ba1f4ae5ab07f0498634351-f3c1a27e5acdd0f1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T21:40:15Z" - latency: 6.736869ms message: 'load-balancer-api-internal: tcp connection to a225e1495ba1f4ae5ab07f0498634351-f3c1a27e5acdd0f1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:39:15Z" - latency: 7.729885ms message: 'load-balancer-api-internal: resolved host name a225e1495ba1f4ae5ab07f0498634351-f3c1a27e5acdd0f1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T21:39:15Z" - latency: 4.826697ms message: 'load-balancer-api-internal: tcp connection to a225e1495ba1f4ae5ab07f0498634351-f3c1a27e5acdd0f1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:38:15Z" - latency: 8.192988ms message: 'load-balancer-api-internal: resolved host name a225e1495ba1f4ae5ab07f0498634351-f3c1a27e5acdd0f1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T21:38:15Z" - latency: 3.777384ms message: 'load-balancer-api-internal: tcp connection to a225e1495ba1f4ae5ab07f0498634351-f3c1a27e5acdd0f1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:37:15Z" - latency: 7.407592ms message: 'load-balancer-api-internal: resolved host name a225e1495ba1f4ae5ab07f0498634351-f3c1a27e5acdd0f1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T21:37:15Z" - latency: 4.844899ms message: 'load-balancer-api-internal: tcp connection to a225e1495ba1f4ae5ab07f0498634351-f3c1a27e5acdd0f1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:36:15Z" - latency: 7.222615ms message: 'load-balancer-api-internal: resolved host name a225e1495ba1f4ae5ab07f0498634351-f3c1a27e5acdd0f1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T21:36:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T20:28:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-228-to-network-check-target-ip-10-0-136-123 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-228.ec2.internal uid: b1b2f103-8e27-475c-889a-5992e855f17d resourceVersion: "84292" uid: 672c63b0-286e-405a-b268-5e360f117080 spec: sourcePod: network-check-source-7d88cb55d8-lxbhh targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-29T20:35:15Z" message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.337976ms message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:38:15Z" - latency: 2.228575ms message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:37:15Z" - latency: 2.360506ms message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:36:15Z" - latency: 1.928235ms message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:35:15Z" - latency: 2.067979ms message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:34:15Z" - latency: 2.199463ms message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:33:15Z" - latency: 2.469866ms message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:32:15Z" - latency: 2.290717ms message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:31:15Z" - latency: 2.50203ms message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:30:15Z" - latency: 2.094512ms message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:29:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T20:28:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-228-to-network-check-target-ip-10-0-137-228 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-228.ec2.internal uid: b1b2f103-8e27-475c-889a-5992e855f17d resourceVersion: "84290" uid: ebb89e40-6dc0-45dc-b858-036a501851a3 spec: sourcePod: network-check-source-7d88cb55d8-lxbhh targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-29T20:35:15Z" message: 'network-check-target-ip-10-0-137-228: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.379455ms message: 'network-check-target-ip-10-0-137-228: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:38:15Z" - latency: 1.17535ms message: 'network-check-target-ip-10-0-137-228: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:37:15Z" - latency: 1.03708ms message: 'network-check-target-ip-10-0-137-228: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:36:15Z" - latency: 1.012138ms message: 'network-check-target-ip-10-0-137-228: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:35:15Z" - latency: 989.874µs message: 'network-check-target-ip-10-0-137-228: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:34:15Z" - latency: 956.908µs message: 'network-check-target-ip-10-0-137-228: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:33:15Z" - latency: 1.037876ms message: 'network-check-target-ip-10-0-137-228: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:32:15Z" - latency: 1.023729ms message: 'network-check-target-ip-10-0-137-228: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:31:15Z" - latency: 889.85µs message: 'network-check-target-ip-10-0-137-228: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:30:15Z" - latency: 1.148787ms message: 'network-check-target-ip-10-0-137-228: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:29:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T20:28:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-228-to-network-check-target-ip-10-0-138-67 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-228.ec2.internal uid: b1b2f103-8e27-475c-889a-5992e855f17d resourceVersion: "84291" uid: 7fc96f10-59b2-46ed-9c92-085d76270633 spec: sourcePod: network-check-source-7d88cb55d8-lxbhh targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-29T20:35:15Z" message: 'network-check-target-ip-10-0-138-67: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.352855ms message: 'network-check-target-ip-10-0-138-67: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:38:15Z" - latency: 2.394112ms message: 'network-check-target-ip-10-0-138-67: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:37:15Z" - latency: 2.325198ms message: 'network-check-target-ip-10-0-138-67: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:36:15Z" - latency: 2.137931ms message: 'network-check-target-ip-10-0-138-67: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:35:15Z" - latency: 2.292054ms message: 'network-check-target-ip-10-0-138-67: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:34:15Z" - latency: 2.215895ms message: 'network-check-target-ip-10-0-138-67: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:33:15Z" - latency: 2.369923ms message: 'network-check-target-ip-10-0-138-67: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:32:15Z" - latency: 2.340723ms message: 'network-check-target-ip-10-0-138-67: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:31:15Z" - latency: 2.296399ms message: 'network-check-target-ip-10-0-138-67: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:30:15Z" - latency: 2.217913ms message: 'network-check-target-ip-10-0-138-67: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:29:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T20:28:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-228-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-228.ec2.internal uid: b1b2f103-8e27-475c-889a-5992e855f17d resourceVersion: "85957" uid: 762feded-bfd5-47dd-b1a5-e90806bccc84 spec: sourcePod: network-check-source-7d88cb55d8-lxbhh targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-29T20:34:15Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.182958ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:40:15Z" - latency: 2.048928ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T21:40:15Z" - latency: 1.016503ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:39:15Z" - latency: 1.928205ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T21:39:15Z" - latency: 762.406µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:38:15Z" - latency: 2.272064ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T21:38:15Z" - latency: 1.145891ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:37:15Z" - latency: 2.032091ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T21:37:15Z" - latency: 932.875µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:36:15Z" - latency: 1.809122ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T21:36:15Z" kind: List metadata: resourceVersion: ""