apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T21:02:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-17-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-17.ec2.internal uid: 083f9db4-af53-4399-9f5c-0e1f8488a78b resourceVersion: "36983" uid: 149453b5-0c70-411a-a9ce-05fbdab8aabc spec: sourcePod: network-check-source-8894fc9bd-jvjcc targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-16T21:09:37Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.189414ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:23:37Z" - latency: 1.201943ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:22:37Z" - latency: 893.103µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:21:37Z" - latency: 723.711µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:20:37Z" - latency: 1.171185ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:19:37Z" - latency: 1.041923ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:18:37Z" - latency: 1.148238ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:17:37Z" - latency: 1.088677ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:16:37Z" - latency: 1.358423ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:15:37Z" - latency: 1.145223ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:14:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T21:02:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-17-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-17.ec2.internal uid: 083f9db4-af53-4399-9f5c-0e1f8488a78b resourceVersion: "40110" uid: 31d61d37-43d6-4f13-8aa1-3297fed5a091 spec: sourcePod: network-check-source-8894fc9bd-jvjcc targetEndpoint: a24ad344768d14b4c89b9b7963a8b8b4-6cf3a5a0de4d0e3b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T21:08:37Z" message: 'load-balancer-api-external: tcp connection to a24ad344768d14b4c89b9b7963a8b8b4-6cf3a5a0de4d0e3b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.825334ms message: 'load-balancer-api-external: tcp connection to a24ad344768d14b4c89b9b7963a8b8b4-6cf3a5a0de4d0e3b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:26:37Z" - latency: 8.038306ms message: 'load-balancer-api-external: resolved host name a24ad344768d14b4c89b9b7963a8b8b4-6cf3a5a0de4d0e3b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T21:26:37Z" - latency: 4.135233ms message: 'load-balancer-api-external: tcp connection to a24ad344768d14b4c89b9b7963a8b8b4-6cf3a5a0de4d0e3b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:25:37Z" - latency: 7.485935ms message: 'load-balancer-api-external: resolved host name a24ad344768d14b4c89b9b7963a8b8b4-6cf3a5a0de4d0e3b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T21:25:37Z" - latency: 4.361972ms message: 'load-balancer-api-external: tcp connection to a24ad344768d14b4c89b9b7963a8b8b4-6cf3a5a0de4d0e3b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:24:37Z" - latency: 7.860638ms message: 'load-balancer-api-external: resolved host name a24ad344768d14b4c89b9b7963a8b8b4-6cf3a5a0de4d0e3b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T21:24:37Z" - latency: 5.78463ms message: 'load-balancer-api-external: tcp connection to a24ad344768d14b4c89b9b7963a8b8b4-6cf3a5a0de4d0e3b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:23:37Z" - latency: 8.396026ms message: 'load-balancer-api-external: resolved host name a24ad344768d14b4c89b9b7963a8b8b4-6cf3a5a0de4d0e3b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T21:23:37Z" - latency: 5.868592ms message: 'load-balancer-api-external: tcp connection to a24ad344768d14b4c89b9b7963a8b8b4-6cf3a5a0de4d0e3b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:22:37Z" - latency: 7.160035ms message: 'load-balancer-api-external: resolved host name a24ad344768d14b4c89b9b7963a8b8b4-6cf3a5a0de4d0e3b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T21:22:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T21:02:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-17-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-17.ec2.internal uid: 083f9db4-af53-4399-9f5c-0e1f8488a78b resourceVersion: "40111" uid: 33669550-b23d-46c7-ba0a-b82a31b4cd52 spec: sourcePod: network-check-source-8894fc9bd-jvjcc targetEndpoint: a24ad344768d14b4c89b9b7963a8b8b4-6cf3a5a0de4d0e3b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T21:08:37Z" message: 'load-balancer-api-internal: tcp connection to a24ad344768d14b4c89b9b7963a8b8b4-6cf3a5a0de4d0e3b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.877563ms message: 'load-balancer-api-internal: tcp connection to a24ad344768d14b4c89b9b7963a8b8b4-6cf3a5a0de4d0e3b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:26:37Z" - latency: 8.01388ms message: 'load-balancer-api-internal: resolved host name a24ad344768d14b4c89b9b7963a8b8b4-6cf3a5a0de4d0e3b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T21:26:37Z" - latency: 3.939266ms message: 'load-balancer-api-internal: tcp connection to a24ad344768d14b4c89b9b7963a8b8b4-6cf3a5a0de4d0e3b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:25:37Z" - latency: 7.509509ms message: 'load-balancer-api-internal: resolved host name a24ad344768d14b4c89b9b7963a8b8b4-6cf3a5a0de4d0e3b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T21:25:37Z" - latency: 4.350956ms message: 'load-balancer-api-internal: tcp connection to a24ad344768d14b4c89b9b7963a8b8b4-6cf3a5a0de4d0e3b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:24:37Z" - latency: 7.957998ms message: 'load-balancer-api-internal: resolved host name a24ad344768d14b4c89b9b7963a8b8b4-6cf3a5a0de4d0e3b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T21:24:37Z" - latency: 5.00715ms message: 'load-balancer-api-internal: tcp connection to a24ad344768d14b4c89b9b7963a8b8b4-6cf3a5a0de4d0e3b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:23:37Z" - latency: 8.450506ms message: 'load-balancer-api-internal: resolved host name a24ad344768d14b4c89b9b7963a8b8b4-6cf3a5a0de4d0e3b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T21:23:37Z" - latency: 4.786705ms message: 'load-balancer-api-internal: tcp connection to a24ad344768d14b4c89b9b7963a8b8b4-6cf3a5a0de4d0e3b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:22:37Z" - latency: 7.079483ms message: 'load-balancer-api-internal: resolved host name a24ad344768d14b4c89b9b7963a8b8b4-6cf3a5a0de4d0e3b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T21:22:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T21:02:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-17-to-network-check-target-ip-10-0-138-120 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-17.ec2.internal uid: 083f9db4-af53-4399-9f5c-0e1f8488a78b resourceVersion: "36981" uid: faf8c158-2e69-4b58-a732-b9c3d9f5216c spec: sourcePod: network-check-source-8894fc9bd-jvjcc targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T21:09:37Z" message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.950818ms message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:23:37Z" - latency: 1.636527ms message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:22:37Z" - latency: 1.829654ms message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:21:37Z" - latency: 1.90935ms message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:20:37Z" - latency: 1.805965ms message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:19:37Z" - latency: 1.837019ms message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:18:37Z" - latency: 1.839268ms message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:17:37Z" - latency: 1.927691ms message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:16:37Z" - latency: 1.859122ms message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:15:37Z" - latency: 1.949771ms message: 'network-check-target-ip-10-0-138-120: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:14:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T21:02:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-17-to-network-check-target-ip-10-0-139-17 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-17.ec2.internal uid: 083f9db4-af53-4399-9f5c-0e1f8488a78b resourceVersion: "36982" uid: 80d1f09e-3de2-4c30-8903-0e04db90f0cf spec: sourcePod: network-check-source-8894fc9bd-jvjcc targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T21:09:37Z" message: 'network-check-target-ip-10-0-139-17: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.174007ms message: 'network-check-target-ip-10-0-139-17: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:23:37Z" - latency: 797.071µs message: 'network-check-target-ip-10-0-139-17: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:22:37Z" - latency: 842.092µs message: 'network-check-target-ip-10-0-139-17: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:21:37Z" - latency: 888.767µs message: 'network-check-target-ip-10-0-139-17: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:20:37Z" - latency: 992.216µs message: 'network-check-target-ip-10-0-139-17: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:19:37Z" - latency: 841.478µs message: 'network-check-target-ip-10-0-139-17: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:18:37Z" - latency: 832.014µs message: 'network-check-target-ip-10-0-139-17: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:17:37Z" - latency: 1.071795ms message: 'network-check-target-ip-10-0-139-17: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:16:37Z" - latency: 1.049114ms message: 'network-check-target-ip-10-0-139-17: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:15:37Z" - latency: 782.646µs message: 'network-check-target-ip-10-0-139-17: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:14:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T21:02:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-17-to-network-check-target-ip-10-0-141-171 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-17.ec2.internal uid: 083f9db4-af53-4399-9f5c-0e1f8488a78b resourceVersion: "36980" uid: cce20593-b758-476b-90c5-2f74190b878f spec: sourcePod: network-check-source-8894fc9bd-jvjcc targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T21:09:37Z" message: 'network-check-target-ip-10-0-141-171: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.953199ms message: 'network-check-target-ip-10-0-141-171: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:23:37Z" - latency: 1.857875ms message: 'network-check-target-ip-10-0-141-171: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:22:37Z" - latency: 1.883166ms message: 'network-check-target-ip-10-0-141-171: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:21:37Z" - latency: 2.246451ms message: 'network-check-target-ip-10-0-141-171: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:20:37Z" - latency: 1.884866ms message: 'network-check-target-ip-10-0-141-171: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:19:37Z" - latency: 2.015056ms message: 'network-check-target-ip-10-0-141-171: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:18:37Z" - latency: 2.11926ms message: 'network-check-target-ip-10-0-141-171: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:17:37Z" - latency: 2.148734ms message: 'network-check-target-ip-10-0-141-171: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:16:37Z" - latency: 2.182027ms message: 'network-check-target-ip-10-0-141-171: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:15:37Z" - latency: 2.213612ms message: 'network-check-target-ip-10-0-141-171: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:14:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T21:02:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-17-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-17.ec2.internal uid: 083f9db4-af53-4399-9f5c-0e1f8488a78b resourceVersion: "40109" uid: 4b5beafb-d855-455c-ae99-ce38c69f2cf1 spec: sourcePod: network-check-source-8894fc9bd-jvjcc targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-16T21:08:37Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 815.565µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:26:37Z" - latency: 1.767725ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T21:26:37Z" - latency: 1.00085ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:25:37Z" - latency: 1.606496ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T21:25:37Z" - latency: 940.235µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:24:37Z" - latency: 1.812628ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T21:24:37Z" - latency: 962.928µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:23:37Z" - latency: 1.65192ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T21:23:37Z" - latency: 849.055µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:22:37Z" - latency: 1.630988ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T21:22:37Z" kind: List metadata: resourceVersion: ""