apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T07:10:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-100-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-100.ec2.internal uid: 59d11bb3-3809-4437-b261-15ca4adeff4c resourceVersion: "41344" uid: d218a640-2d19-43dd-8fa7-bf0bf1d33edf spec: sourcePod: network-check-source-8894fc9bd-zx2wb targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-20T07:17:43Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.311327ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:38:43Z" - latency: 1.069451ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:37:43Z" - latency: 885.435µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:36:43Z" - latency: 1.16034ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:35:43Z" - latency: 1.160189ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:34:43Z" - latency: 795.271µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:33:43Z" - latency: 1.069527ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:32:43Z" - latency: 775.069µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:31:43Z" - latency: 1.187066ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:30:43Z" - latency: 939.601µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:29:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T07:10:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-100-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-100.ec2.internal uid: 59d11bb3-3809-4437-b261-15ca4adeff4c resourceVersion: "43012" uid: b749b030-5966-4b70-9d01-e172546b6395 spec: sourcePod: network-check-source-8894fc9bd-zx2wb targetEndpoint: a07e24f9fbf1c46eaad0bf3b5f52d137-c53836f9df16fe2b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-20T07:16:43Z" message: 'load-balancer-api-external: tcp connection to a07e24f9fbf1c46eaad0bf3b5f52d137-c53836f9df16fe2b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.430565ms message: 'load-balancer-api-external: tcp connection to a07e24f9fbf1c46eaad0bf3b5f52d137-c53836f9df16fe2b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:40:43Z" - latency: 15.26885ms message: 'load-balancer-api-external: resolved host name a07e24f9fbf1c46eaad0bf3b5f52d137-c53836f9df16fe2b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T07:40:43Z" - latency: 3.993654ms message: 'load-balancer-api-external: tcp connection to a07e24f9fbf1c46eaad0bf3b5f52d137-c53836f9df16fe2b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:39:43Z" - latency: 12.364534ms message: 'load-balancer-api-external: resolved host name a07e24f9fbf1c46eaad0bf3b5f52d137-c53836f9df16fe2b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T07:39:43Z" - latency: 5.524305ms message: 'load-balancer-api-external: tcp connection to a07e24f9fbf1c46eaad0bf3b5f52d137-c53836f9df16fe2b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:38:43Z" - latency: 13.963922ms message: 'load-balancer-api-external: resolved host name a07e24f9fbf1c46eaad0bf3b5f52d137-c53836f9df16fe2b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T07:38:43Z" - latency: 4.676955ms message: 'load-balancer-api-external: tcp connection to a07e24f9fbf1c46eaad0bf3b5f52d137-c53836f9df16fe2b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:37:43Z" - latency: 10.929206ms message: 'load-balancer-api-external: resolved host name a07e24f9fbf1c46eaad0bf3b5f52d137-c53836f9df16fe2b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T07:37:43Z" - latency: 4.382762ms message: 'load-balancer-api-external: tcp connection to a07e24f9fbf1c46eaad0bf3b5f52d137-c53836f9df16fe2b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:36:43Z" - latency: 13.546027ms message: 'load-balancer-api-external: resolved host name a07e24f9fbf1c46eaad0bf3b5f52d137-c53836f9df16fe2b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T07:36:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T07:10:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-100-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-100.ec2.internal uid: 59d11bb3-3809-4437-b261-15ca4adeff4c resourceVersion: "43011" uid: 95192d77-4b2b-4970-9452-94c72f38c90b spec: sourcePod: network-check-source-8894fc9bd-zx2wb targetEndpoint: a07e24f9fbf1c46eaad0bf3b5f52d137-c53836f9df16fe2b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-20T07:16:43Z" message: 'load-balancer-api-internal: tcp connection to a07e24f9fbf1c46eaad0bf3b5f52d137-c53836f9df16fe2b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.445348ms message: 'load-balancer-api-internal: tcp connection to a07e24f9fbf1c46eaad0bf3b5f52d137-c53836f9df16fe2b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:40:43Z" - latency: 15.308756ms message: 'load-balancer-api-internal: resolved host name a07e24f9fbf1c46eaad0bf3b5f52d137-c53836f9df16fe2b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T07:40:43Z" - latency: 3.988135ms message: 'load-balancer-api-internal: tcp connection to a07e24f9fbf1c46eaad0bf3b5f52d137-c53836f9df16fe2b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:39:43Z" - latency: 12.337515ms message: 'load-balancer-api-internal: resolved host name a07e24f9fbf1c46eaad0bf3b5f52d137-c53836f9df16fe2b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T07:39:43Z" - latency: 5.51221ms message: 'load-balancer-api-internal: tcp connection to a07e24f9fbf1c46eaad0bf3b5f52d137-c53836f9df16fe2b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:38:43Z" - latency: 14.043514ms message: 'load-balancer-api-internal: resolved host name a07e24f9fbf1c46eaad0bf3b5f52d137-c53836f9df16fe2b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T07:38:43Z" - latency: 4.708757ms message: 'load-balancer-api-internal: tcp connection to a07e24f9fbf1c46eaad0bf3b5f52d137-c53836f9df16fe2b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:37:43Z" - latency: 10.861909ms message: 'load-balancer-api-internal: resolved host name a07e24f9fbf1c46eaad0bf3b5f52d137-c53836f9df16fe2b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T07:37:43Z" - latency: 3.372372ms message: 'load-balancer-api-internal: tcp connection to a07e24f9fbf1c46eaad0bf3b5f52d137-c53836f9df16fe2b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:36:43Z" - latency: 13.660267ms message: 'load-balancer-api-internal: resolved host name a07e24f9fbf1c46eaad0bf3b5f52d137-c53836f9df16fe2b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T07:36:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T07:10:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-100-to-network-check-target-ip-10-0-130-105 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-100.ec2.internal uid: 59d11bb3-3809-4437-b261-15ca4adeff4c resourceVersion: "41343" uid: f59ee590-dd4f-4288-8656-191e1df68c04 spec: sourcePod: network-check-source-8894fc9bd-zx2wb targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-20T07:17:43Z" message: 'network-check-target-ip-10-0-130-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.617914ms message: 'network-check-target-ip-10-0-130-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:38:43Z" - latency: 2.236673ms message: 'network-check-target-ip-10-0-130-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:37:43Z" - latency: 2.294665ms message: 'network-check-target-ip-10-0-130-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:36:43Z" - latency: 2.415286ms message: 'network-check-target-ip-10-0-130-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:35:43Z" - latency: 2.070803ms message: 'network-check-target-ip-10-0-130-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:34:43Z" - latency: 2.199576ms message: 'network-check-target-ip-10-0-130-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:33:43Z" - latency: 2.084821ms message: 'network-check-target-ip-10-0-130-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:32:43Z" - latency: 1.947488ms message: 'network-check-target-ip-10-0-130-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:31:43Z" - latency: 2.368371ms message: 'network-check-target-ip-10-0-130-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:30:43Z" - latency: 2.837836ms message: 'network-check-target-ip-10-0-130-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:29:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T07:10:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-100-to-network-check-target-ip-10-0-138-178 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-100.ec2.internal uid: 59d11bb3-3809-4437-b261-15ca4adeff4c resourceVersion: "41342" uid: 890a25de-82df-4773-9890-c4da31a4bd1a spec: sourcePod: network-check-source-8894fc9bd-zx2wb targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-20T07:17:43Z" message: 'network-check-target-ip-10-0-138-178: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.180439ms message: 'network-check-target-ip-10-0-138-178: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:38:43Z" - latency: 2.022235ms message: 'network-check-target-ip-10-0-138-178: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:37:43Z" - latency: 2.883458ms message: 'network-check-target-ip-10-0-138-178: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:36:43Z" - latency: 2.135591ms message: 'network-check-target-ip-10-0-138-178: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:35:43Z" - latency: 2.554001ms message: 'network-check-target-ip-10-0-138-178: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:34:43Z" - latency: 2.163846ms message: 'network-check-target-ip-10-0-138-178: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:33:43Z" - latency: 2.522052ms message: 'network-check-target-ip-10-0-138-178: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:32:43Z" - latency: 1.94036ms message: 'network-check-target-ip-10-0-138-178: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:31:43Z" - latency: 2.19036ms message: 'network-check-target-ip-10-0-138-178: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:30:43Z" - latency: 2.016023ms message: 'network-check-target-ip-10-0-138-178: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:29:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T07:10:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-100-to-network-check-target-ip-10-0-142-100 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-100.ec2.internal uid: 59d11bb3-3809-4437-b261-15ca4adeff4c resourceVersion: "41341" uid: 17bca235-f16a-4b06-bfac-ef77f815354e spec: sourcePod: network-check-source-8894fc9bd-zx2wb targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-20T07:17:43Z" message: 'network-check-target-ip-10-0-142-100: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 858.657µs message: 'network-check-target-ip-10-0-142-100: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:38:43Z" - latency: 1.021375ms message: 'network-check-target-ip-10-0-142-100: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:37:43Z" - latency: 876.922µs message: 'network-check-target-ip-10-0-142-100: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:36:43Z" - latency: 1.070101ms message: 'network-check-target-ip-10-0-142-100: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:35:43Z" - latency: 995.83µs message: 'network-check-target-ip-10-0-142-100: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:34:43Z" - latency: 887.459µs message: 'network-check-target-ip-10-0-142-100: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:33:43Z" - latency: 893.319µs message: 'network-check-target-ip-10-0-142-100: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:32:43Z" - latency: 899.099µs message: 'network-check-target-ip-10-0-142-100: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:31:43Z" - latency: 953.792µs message: 'network-check-target-ip-10-0-142-100: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:30:43Z" - latency: 894.103µs message: 'network-check-target-ip-10-0-142-100: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:29:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T07:10:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-100-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-100.ec2.internal uid: 59d11bb3-3809-4437-b261-15ca4adeff4c resourceVersion: "43010" uid: b70ae522-f16f-4a12-9697-890548f6f904 spec: sourcePod: network-check-source-8894fc9bd-zx2wb targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-20T07:16:43Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 993.861µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:40:43Z" - latency: 1.913915ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T07:40:43Z" - latency: 829.471µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:39:43Z" - latency: 1.604608ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T07:39:43Z" - latency: 845.991µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:38:43Z" - latency: 1.734471ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T07:38:43Z" - latency: 844.762µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:37:43Z" - latency: 2.011772ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T07:37:43Z" - latency: 1.054403ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T07:36:43Z" - latency: 1.796971ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T07:36:43Z" kind: List metadata: resourceVersion: ""