apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T10:16:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-110-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-110.ec2.internal uid: f48aa8bc-e8fa-4a38-b524-876642ebc325 resourceVersion: "19810" uid: 276ceb42-adac-4fce-b8e3-f93565054628 spec: sourcePod: network-check-source-7f44b6dd87-87txm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-29T10:23:34Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 998.501µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:37:34Z" - latency: 895µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:36:34Z" - latency: 1.086365ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:35:34Z" - latency: 820.586µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:34:34Z" - latency: 873.811µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:33:34Z" - latency: 1.112974ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:32:34Z" - latency: 944.988µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:31:34Z" - latency: 1.003634ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:30:34Z" - latency: 996.686µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:29:34Z" - latency: 785.93µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:28:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T10:16:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-110-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-110.ec2.internal uid: f48aa8bc-e8fa-4a38-b524-876642ebc325 resourceVersion: "20964" uid: 258e3d5f-6ac2-4cda-9ae6-ec0372ee4786 spec: sourcePod: network-check-source-7f44b6dd87-87txm targetEndpoint: aec86d4065136492e91307be5c2a17f6-a3cc38d8baf03169.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-29T10:22:34Z" message: 'load-balancer-api-external: tcp connection to aec86d4065136492e91307be5c2a17f6-a3cc38d8baf03169.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.811755ms message: 'load-balancer-api-external: tcp connection to aec86d4065136492e91307be5c2a17f6-a3cc38d8baf03169.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:40:34Z" - latency: 9.073023ms message: 'load-balancer-api-external: resolved host name aec86d4065136492e91307be5c2a17f6-a3cc38d8baf03169.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T10:40:34Z" - latency: 4.233493ms message: 'load-balancer-api-external: tcp connection to aec86d4065136492e91307be5c2a17f6-a3cc38d8baf03169.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:39:34Z" - latency: 6.473674ms message: 'load-balancer-api-external: resolved host name aec86d4065136492e91307be5c2a17f6-a3cc38d8baf03169.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T10:39:34Z" - latency: 5.138183ms message: 'load-balancer-api-external: tcp connection to aec86d4065136492e91307be5c2a17f6-a3cc38d8baf03169.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:38:34Z" - latency: 6.262499ms message: 'load-balancer-api-external: resolved host name aec86d4065136492e91307be5c2a17f6-a3cc38d8baf03169.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T10:38:34Z" - latency: 3.993124ms message: 'load-balancer-api-external: tcp connection to aec86d4065136492e91307be5c2a17f6-a3cc38d8baf03169.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:37:34Z" - latency: 7.172736ms message: 'load-balancer-api-external: resolved host name aec86d4065136492e91307be5c2a17f6-a3cc38d8baf03169.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T10:37:34Z" - latency: 8.170424ms message: 'load-balancer-api-external: tcp connection to aec86d4065136492e91307be5c2a17f6-a3cc38d8baf03169.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:36:34Z" - latency: 6.191338ms message: 'load-balancer-api-external: resolved host name aec86d4065136492e91307be5c2a17f6-a3cc38d8baf03169.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T10:36:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T10:16:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-110-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-110.ec2.internal uid: f48aa8bc-e8fa-4a38-b524-876642ebc325 resourceVersion: "20965" uid: 50cb08b4-d61d-46d9-8b63-2b93f7013063 spec: sourcePod: network-check-source-7f44b6dd87-87txm targetEndpoint: aec86d4065136492e91307be5c2a17f6-a3cc38d8baf03169.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-29T10:22:34Z" message: 'load-balancer-api-internal: tcp connection to aec86d4065136492e91307be5c2a17f6-a3cc38d8baf03169.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.813428ms message: 'load-balancer-api-internal: tcp connection to aec86d4065136492e91307be5c2a17f6-a3cc38d8baf03169.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:40:34Z" - latency: 9.05634ms message: 'load-balancer-api-internal: resolved host name aec86d4065136492e91307be5c2a17f6-a3cc38d8baf03169.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T10:40:34Z" - latency: 4.179987ms message: 'load-balancer-api-internal: tcp connection to aec86d4065136492e91307be5c2a17f6-a3cc38d8baf03169.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:39:34Z" - latency: 6.509474ms message: 'load-balancer-api-internal: resolved host name aec86d4065136492e91307be5c2a17f6-a3cc38d8baf03169.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T10:39:34Z" - latency: 5.10967ms message: 'load-balancer-api-internal: tcp connection to aec86d4065136492e91307be5c2a17f6-a3cc38d8baf03169.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:38:34Z" - latency: 6.29869ms message: 'load-balancer-api-internal: resolved host name aec86d4065136492e91307be5c2a17f6-a3cc38d8baf03169.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T10:38:34Z" - latency: 5.963223ms message: 'load-balancer-api-internal: tcp connection to aec86d4065136492e91307be5c2a17f6-a3cc38d8baf03169.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:37:34Z" - latency: 7.27429ms message: 'load-balancer-api-internal: resolved host name aec86d4065136492e91307be5c2a17f6-a3cc38d8baf03169.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T10:37:34Z" - latency: 5.120454ms message: 'load-balancer-api-internal: tcp connection to aec86d4065136492e91307be5c2a17f6-a3cc38d8baf03169.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:36:34Z" - latency: 6.146637ms message: 'load-balancer-api-internal: resolved host name aec86d4065136492e91307be5c2a17f6-a3cc38d8baf03169.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T10:36:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T10:16:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-110-to-network-check-target-ip-10-0-134-110 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-110.ec2.internal uid: f48aa8bc-e8fa-4a38-b524-876642ebc325 resourceVersion: "19807" uid: ca4a0027-63b3-4f45-a807-796ec8aff243 spec: sourcePod: network-check-source-7f44b6dd87-87txm targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-29T10:23:34Z" message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 946.807µs message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:37:34Z" - latency: 793.244µs message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:36:34Z" - latency: 891.848µs message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:35:34Z" - latency: 866.684µs message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:34:34Z" - latency: 992.338µs message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:33:34Z" - latency: 1.248853ms message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:32:34Z" - latency: 836.212µs message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:31:34Z" - latency: 1.292765ms message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:30:34Z" - latency: 817.584µs message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:29:34Z" - latency: 1.137059ms message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:28:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T10:16:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-110-to-network-check-target-ip-10-0-136-144 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-110.ec2.internal uid: f48aa8bc-e8fa-4a38-b524-876642ebc325 resourceVersion: "19808" uid: 2e8fab11-ee8d-4ae8-9ca6-a290ad7556ff spec: sourcePod: network-check-source-7f44b6dd87-87txm targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-29T10:23:34Z" message: 'network-check-target-ip-10-0-136-144: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.305723ms message: 'network-check-target-ip-10-0-136-144: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:37:34Z" - latency: 2.068694ms message: 'network-check-target-ip-10-0-136-144: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:36:34Z" - latency: 2.382452ms message: 'network-check-target-ip-10-0-136-144: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:35:34Z" - latency: 2.469844ms message: 'network-check-target-ip-10-0-136-144: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:34:34Z" - latency: 2.116225ms message: 'network-check-target-ip-10-0-136-144: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:33:34Z" - latency: 2.6447ms message: 'network-check-target-ip-10-0-136-144: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:32:34Z" - latency: 2.204923ms message: 'network-check-target-ip-10-0-136-144: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:31:34Z" - latency: 2.458209ms message: 'network-check-target-ip-10-0-136-144: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:30:34Z" - latency: 2.271287ms message: 'network-check-target-ip-10-0-136-144: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:29:34Z" - latency: 2.252551ms message: 'network-check-target-ip-10-0-136-144: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:28:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T10:16:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-110-to-network-check-target-ip-10-0-137-11 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-110.ec2.internal uid: f48aa8bc-e8fa-4a38-b524-876642ebc325 resourceVersion: "19809" uid: 6577ec89-ce18-4e9a-8af8-9d0d5786f6ea spec: sourcePod: network-check-source-7f44b6dd87-87txm targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-29T10:23:34Z" message: 'network-check-target-ip-10-0-137-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.273678ms message: 'network-check-target-ip-10-0-137-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:37:34Z" - latency: 2.088923ms message: 'network-check-target-ip-10-0-137-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:36:34Z" - latency: 2.14866ms message: 'network-check-target-ip-10-0-137-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:35:34Z" - latency: 2.121542ms message: 'network-check-target-ip-10-0-137-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:34:34Z" - latency: 2.115858ms message: 'network-check-target-ip-10-0-137-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:33:34Z" - latency: 2.106499ms message: 'network-check-target-ip-10-0-137-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:32:34Z" - latency: 2.189526ms message: 'network-check-target-ip-10-0-137-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:31:34Z" - latency: 2.206256ms message: 'network-check-target-ip-10-0-137-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:30:34Z" - latency: 2.215837ms message: 'network-check-target-ip-10-0-137-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:29:34Z" - latency: 2.058574ms message: 'network-check-target-ip-10-0-137-11: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:28:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T10:16:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-110-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-110.ec2.internal uid: f48aa8bc-e8fa-4a38-b524-876642ebc325 resourceVersion: "20963" uid: 1d9ed6a4-5b8b-4215-bbf6-954be112a7d2 spec: sourcePod: network-check-source-7f44b6dd87-87txm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-29T10:22:34Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.088811ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:40:34Z" - latency: 1.542756ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T10:40:34Z" - latency: 1.037204ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:39:34Z" - latency: 1.691159ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T10:39:34Z" - latency: 802.434µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:38:34Z" - latency: 1.688914ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T10:38:34Z" - latency: 802.983µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:37:34Z" - latency: 1.669284ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T10:37:34Z" - latency: 1.14983ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:36:34Z" - latency: 1.619529ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T10:36:34Z" kind: List metadata: resourceVersion: ""