apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T12:23:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-10-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-10.ec2.internal uid: f9f9505c-78a5-475a-bc8b-5770f230e5ef resourceVersion: "54415" uid: 1abe5327-9e4b-44e0-9e1c-bf264ecbec2a spec: sourcePod: network-check-source-869dcfcdcd-2xthd targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-16T12:30:22Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 884.851µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:58:22Z" - latency: 925.632µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:57:22Z" - latency: 993.687µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:56:22Z" - latency: 1.249475ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:55:22Z" - latency: 1.266786ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:54:22Z" - latency: 1.134102ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:53:22Z" - latency: 965.147µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:52:22Z" - latency: 1.071219ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:51:22Z" - latency: 1.266319ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:50:22Z" - latency: 879.592µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:49:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T12:23:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-10-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-10.ec2.internal uid: f9f9505c-78a5-475a-bc8b-5770f230e5ef resourceVersion: "55437" uid: c881e87d-e3d6-479f-9552-44ec255ad1ad spec: sourcePod: network-check-source-869dcfcdcd-2xthd targetEndpoint: ae555f7aa4f864568a62f106e9eb599d-e55d0efecdd42f4e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T12:29:22Z" message: 'load-balancer-api-external: tcp connection to ae555f7aa4f864568a62f106e9eb599d-e55d0efecdd42f4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.070188ms message: 'load-balancer-api-external: tcp connection to ae555f7aa4f864568a62f106e9eb599d-e55d0efecdd42f4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:59:22Z" - latency: 7.730851ms message: 'load-balancer-api-external: resolved host name ae555f7aa4f864568a62f106e9eb599d-e55d0efecdd42f4e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T12:59:22Z" - latency: 6.711728ms message: 'load-balancer-api-external: tcp connection to ae555f7aa4f864568a62f106e9eb599d-e55d0efecdd42f4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:58:22Z" - latency: 8.790086ms message: 'load-balancer-api-external: resolved host name ae555f7aa4f864568a62f106e9eb599d-e55d0efecdd42f4e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T12:58:22Z" - latency: 4.160194ms message: 'load-balancer-api-external: tcp connection to ae555f7aa4f864568a62f106e9eb599d-e55d0efecdd42f4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:57:22Z" - latency: 7.658085ms message: 'load-balancer-api-external: resolved host name ae555f7aa4f864568a62f106e9eb599d-e55d0efecdd42f4e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T12:57:22Z" - latency: 4.231108ms message: 'load-balancer-api-external: tcp connection to ae555f7aa4f864568a62f106e9eb599d-e55d0efecdd42f4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:56:22Z" - latency: 8.859949ms message: 'load-balancer-api-external: resolved host name ae555f7aa4f864568a62f106e9eb599d-e55d0efecdd42f4e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T12:56:22Z" - latency: 8.641065ms message: 'load-balancer-api-external: tcp connection to ae555f7aa4f864568a62f106e9eb599d-e55d0efecdd42f4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:55:22Z" - latency: 9.145601ms message: 'load-balancer-api-external: resolved host name ae555f7aa4f864568a62f106e9eb599d-e55d0efecdd42f4e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T12:55:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T12:23:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-10-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-10.ec2.internal uid: f9f9505c-78a5-475a-bc8b-5770f230e5ef resourceVersion: "55438" uid: 82203ede-356c-406c-b3d8-54aa9dafd164 spec: sourcePod: network-check-source-869dcfcdcd-2xthd targetEndpoint: ae555f7aa4f864568a62f106e9eb599d-e55d0efecdd42f4e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T12:29:22Z" message: 'load-balancer-api-internal: tcp connection to ae555f7aa4f864568a62f106e9eb599d-e55d0efecdd42f4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.372107ms message: 'load-balancer-api-internal: tcp connection to ae555f7aa4f864568a62f106e9eb599d-e55d0efecdd42f4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:59:22Z" - latency: 7.689274ms message: 'load-balancer-api-internal: resolved host name ae555f7aa4f864568a62f106e9eb599d-e55d0efecdd42f4e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T12:59:22Z" - latency: 6.698949ms message: 'load-balancer-api-internal: tcp connection to ae555f7aa4f864568a62f106e9eb599d-e55d0efecdd42f4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:58:22Z" - latency: 8.840171ms message: 'load-balancer-api-internal: resolved host name ae555f7aa4f864568a62f106e9eb599d-e55d0efecdd42f4e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T12:58:22Z" - latency: 3.645156ms message: 'load-balancer-api-internal: tcp connection to ae555f7aa4f864568a62f106e9eb599d-e55d0efecdd42f4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:57:22Z" - latency: 7.791225ms message: 'load-balancer-api-internal: resolved host name ae555f7aa4f864568a62f106e9eb599d-e55d0efecdd42f4e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T12:57:22Z" - latency: 4.985673ms message: 'load-balancer-api-internal: tcp connection to ae555f7aa4f864568a62f106e9eb599d-e55d0efecdd42f4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:56:22Z" - latency: 8.956837ms message: 'load-balancer-api-internal: resolved host name ae555f7aa4f864568a62f106e9eb599d-e55d0efecdd42f4e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T12:56:22Z" - latency: 4.865948ms message: 'load-balancer-api-internal: tcp connection to ae555f7aa4f864568a62f106e9eb599d-e55d0efecdd42f4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:55:22Z" - latency: 9.303078ms message: 'load-balancer-api-internal: resolved host name ae555f7aa4f864568a62f106e9eb599d-e55d0efecdd42f4e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T12:55:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T12:23:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-10-to-network-check-target-ip-10-0-129-10 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-10.ec2.internal uid: f9f9505c-78a5-475a-bc8b-5770f230e5ef resourceVersion: "54413" uid: c689124d-2a7f-4442-8cbd-e4f90de7c93c spec: sourcePod: network-check-source-869dcfcdcd-2xthd targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-16T12:30:22Z" message: 'network-check-target-ip-10-0-129-10: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.852383ms message: 'network-check-target-ip-10-0-129-10: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:58:22Z" - latency: 1.856785ms message: 'network-check-target-ip-10-0-129-10: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:57:22Z" - latency: 1.989579ms message: 'network-check-target-ip-10-0-129-10: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:56:22Z" - latency: 1.994435ms message: 'network-check-target-ip-10-0-129-10: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:55:22Z" - latency: 2.629659ms message: 'network-check-target-ip-10-0-129-10: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:54:22Z" - latency: 2.266702ms message: 'network-check-target-ip-10-0-129-10: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:53:22Z" - latency: 2.335901ms message: 'network-check-target-ip-10-0-129-10: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:52:22Z" - latency: 2.292068ms message: 'network-check-target-ip-10-0-129-10: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:51:22Z" - latency: 2.152164ms message: 'network-check-target-ip-10-0-129-10: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:50:22Z" - latency: 1.922726ms message: 'network-check-target-ip-10-0-129-10: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:49:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T12:23:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-10-to-network-check-target-ip-10-0-137-10 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-10.ec2.internal uid: f9f9505c-78a5-475a-bc8b-5770f230e5ef resourceVersion: "54412" uid: b109da70-7ac7-49c9-81b5-dc5d01cc557f spec: sourcePod: network-check-source-869dcfcdcd-2xthd targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-16T12:30:22Z" message: 'network-check-target-ip-10-0-137-10: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.590643ms message: 'network-check-target-ip-10-0-137-10: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:58:22Z" - latency: 926.061µs message: 'network-check-target-ip-10-0-137-10: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:57:22Z" - latency: 1.041516ms message: 'network-check-target-ip-10-0-137-10: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:56:22Z" - latency: 1.017514ms message: 'network-check-target-ip-10-0-137-10: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:55:22Z" - latency: 1.00632ms message: 'network-check-target-ip-10-0-137-10: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:54:22Z" - latency: 1.065517ms message: 'network-check-target-ip-10-0-137-10: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:53:22Z" - latency: 997.706µs message: 'network-check-target-ip-10-0-137-10: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:52:22Z" - latency: 1.098059ms message: 'network-check-target-ip-10-0-137-10: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:51:22Z" - latency: 1.006698ms message: 'network-check-target-ip-10-0-137-10: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:50:22Z" - latency: 972.313µs message: 'network-check-target-ip-10-0-137-10: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:49:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T12:23:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-10-to-network-check-target-ip-10-0-139-167 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-10.ec2.internal uid: f9f9505c-78a5-475a-bc8b-5770f230e5ef resourceVersion: "54414" uid: 63783760-45a0-492e-97f2-fc274ebe67f2 spec: sourcePod: network-check-source-869dcfcdcd-2xthd targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-16T12:30:22Z" message: 'network-check-target-ip-10-0-139-167: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.696703ms message: 'network-check-target-ip-10-0-139-167: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:58:22Z" - latency: 2.103241ms message: 'network-check-target-ip-10-0-139-167: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:57:22Z" - latency: 2.284748ms message: 'network-check-target-ip-10-0-139-167: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:56:22Z" - latency: 2.632747ms message: 'network-check-target-ip-10-0-139-167: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:55:22Z" - latency: 2.674966ms message: 'network-check-target-ip-10-0-139-167: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:54:22Z" - latency: 2.385255ms message: 'network-check-target-ip-10-0-139-167: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:53:22Z" - latency: 2.358462ms message: 'network-check-target-ip-10-0-139-167: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:52:22Z" - latency: 2.394127ms message: 'network-check-target-ip-10-0-139-167: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:51:22Z" - latency: 2.533298ms message: 'network-check-target-ip-10-0-139-167: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:50:22Z" - latency: 2.164626ms message: 'network-check-target-ip-10-0-139-167: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:49:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T12:23:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-10-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-10.ec2.internal uid: f9f9505c-78a5-475a-bc8b-5770f230e5ef resourceVersion: "55436" uid: 7726a19d-d223-4c48-9be5-e56fbfc1376f spec: sourcePod: network-check-source-869dcfcdcd-2xthd targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-16T12:29:22Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 922.454µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:59:22Z" - latency: 2.133095ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T12:59:22Z" - latency: 985.384µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:58:22Z" - latency: 1.927806ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T12:58:22Z" - latency: 1.10368ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:57:22Z" - latency: 1.692847ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T12:57:22Z" - latency: 991.682µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:56:22Z" - latency: 1.981657ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T12:56:22Z" - latency: 1.08467ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T12:55:22Z" - latency: 1.891796ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T12:55:22Z" kind: List metadata: resourceVersion: ""