apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T18:44:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-141-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-141.ec2.internal uid: 0a6debd6-6f45-4836-ad09-15cfa1ea59a6 resourceVersion: "51572" uid: 5175ee21-7fb5-4624-87fe-a31bc7a44c25 spec: sourcePod: network-check-source-6947749cfc-wtpb8 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-12T18:51:45Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.14867ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:19:45Z" - latency: 1.570751ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:18:45Z" - latency: 1.617147ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:17:45Z" - latency: 1.150101ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:16:45Z" - latency: 1.126658ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:15:45Z" - latency: 1.268769ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:14:45Z" - latency: 1.465631ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:13:45Z" - latency: 1.114671ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:12:45Z" - latency: 1.012819ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:11:45Z" - latency: 979.127µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:10:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T18:44:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-141-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-141.ec2.internal uid: 0a6debd6-6f45-4836-ad09-15cfa1ea59a6 resourceVersion: "52632" uid: 56e35488-b850-4801-8a9b-edc1dad90580 spec: sourcePod: network-check-source-6947749cfc-wtpb8 targetEndpoint: ac0c00884d0ed4531b789e2a920bd1a4-c41f17ce784e8ea5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-12T18:50:45Z" message: 'load-balancer-api-external: tcp connection to ac0c00884d0ed4531b789e2a920bd1a4-c41f17ce784e8ea5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.817897ms message: 'load-balancer-api-external: tcp connection to ac0c00884d0ed4531b789e2a920bd1a4-c41f17ce784e8ea5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:20:45Z" - latency: 6.951997ms message: 'load-balancer-api-external: resolved host name ac0c00884d0ed4531b789e2a920bd1a4-c41f17ce784e8ea5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:20:45Z" - latency: 5.455052ms message: 'load-balancer-api-external: tcp connection to ac0c00884d0ed4531b789e2a920bd1a4-c41f17ce784e8ea5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:19:45Z" - latency: 9.077021ms message: 'load-balancer-api-external: resolved host name ac0c00884d0ed4531b789e2a920bd1a4-c41f17ce784e8ea5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:19:45Z" - latency: 5.026289ms message: 'load-balancer-api-external: tcp connection to ac0c00884d0ed4531b789e2a920bd1a4-c41f17ce784e8ea5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:18:45Z" - latency: 8.3802ms message: 'load-balancer-api-external: resolved host name ac0c00884d0ed4531b789e2a920bd1a4-c41f17ce784e8ea5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:18:45Z" - latency: 3.630327ms message: 'load-balancer-api-external: tcp connection to ac0c00884d0ed4531b789e2a920bd1a4-c41f17ce784e8ea5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:17:45Z" - latency: 8.332341ms message: 'load-balancer-api-external: resolved host name ac0c00884d0ed4531b789e2a920bd1a4-c41f17ce784e8ea5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:17:45Z" - latency: 3.290612ms message: 'load-balancer-api-external: tcp connection to ac0c00884d0ed4531b789e2a920bd1a4-c41f17ce784e8ea5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:16:45Z" - latency: 8.304988ms message: 'load-balancer-api-external: resolved host name ac0c00884d0ed4531b789e2a920bd1a4-c41f17ce784e8ea5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:16:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T18:44:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-141-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-141.ec2.internal uid: 0a6debd6-6f45-4836-ad09-15cfa1ea59a6 resourceVersion: "52631" uid: b360afb9-c7f6-4670-9573-f85553b6b64b spec: sourcePod: network-check-source-6947749cfc-wtpb8 targetEndpoint: ac0c00884d0ed4531b789e2a920bd1a4-c41f17ce784e8ea5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-12T18:50:45Z" message: 'load-balancer-api-internal: tcp connection to ac0c00884d0ed4531b789e2a920bd1a4-c41f17ce784e8ea5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.837155ms message: 'load-balancer-api-internal: tcp connection to ac0c00884d0ed4531b789e2a920bd1a4-c41f17ce784e8ea5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:20:45Z" - latency: 6.914184ms message: 'load-balancer-api-internal: resolved host name ac0c00884d0ed4531b789e2a920bd1a4-c41f17ce784e8ea5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:20:45Z" - latency: 5.462681ms message: 'load-balancer-api-internal: tcp connection to ac0c00884d0ed4531b789e2a920bd1a4-c41f17ce784e8ea5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:19:45Z" - latency: 8.956932ms message: 'load-balancer-api-internal: resolved host name ac0c00884d0ed4531b789e2a920bd1a4-c41f17ce784e8ea5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:19:45Z" - latency: 5.140759ms message: 'load-balancer-api-internal: tcp connection to ac0c00884d0ed4531b789e2a920bd1a4-c41f17ce784e8ea5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:18:45Z" - latency: 8.28145ms message: 'load-balancer-api-internal: resolved host name ac0c00884d0ed4531b789e2a920bd1a4-c41f17ce784e8ea5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:18:45Z" - latency: 3.660459ms message: 'load-balancer-api-internal: tcp connection to ac0c00884d0ed4531b789e2a920bd1a4-c41f17ce784e8ea5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:17:45Z" - latency: 8.192146ms message: 'load-balancer-api-internal: resolved host name ac0c00884d0ed4531b789e2a920bd1a4-c41f17ce784e8ea5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:17:45Z" - latency: 4.227129ms message: 'load-balancer-api-internal: tcp connection to ac0c00884d0ed4531b789e2a920bd1a4-c41f17ce784e8ea5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:16:45Z" - latency: 8.271005ms message: 'load-balancer-api-internal: resolved host name ac0c00884d0ed4531b789e2a920bd1a4-c41f17ce784e8ea5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:16:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T18:44:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-141-to-network-check-target-ip-10-0-134-129 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-141.ec2.internal uid: 0a6debd6-6f45-4836-ad09-15cfa1ea59a6 resourceVersion: "51571" uid: 3b6ef891-8cd0-4cbd-9aca-7bb610f5fdb3 spec: sourcePod: network-check-source-6947749cfc-wtpb8 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-12T18:51:45Z" message: 'network-check-target-ip-10-0-134-129: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.060214ms message: 'network-check-target-ip-10-0-134-129: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:19:45Z" - latency: 2.173709ms message: 'network-check-target-ip-10-0-134-129: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:18:45Z" - latency: 2.038412ms message: 'network-check-target-ip-10-0-134-129: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:17:45Z" - latency: 2.147347ms message: 'network-check-target-ip-10-0-134-129: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:16:45Z" - latency: 2.070342ms message: 'network-check-target-ip-10-0-134-129: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:15:45Z" - latency: 2.057174ms message: 'network-check-target-ip-10-0-134-129: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:14:45Z" - latency: 1.897982ms message: 'network-check-target-ip-10-0-134-129: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:13:45Z" - latency: 1.889989ms message: 'network-check-target-ip-10-0-134-129: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:12:45Z" - latency: 2.163294ms message: 'network-check-target-ip-10-0-134-129: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:11:45Z" - latency: 2.139673ms message: 'network-check-target-ip-10-0-134-129: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:10:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T18:44:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-141-to-network-check-target-ip-10-0-141-141 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-141.ec2.internal uid: 0a6debd6-6f45-4836-ad09-15cfa1ea59a6 resourceVersion: "51569" uid: 1de8bc68-d5b4-4406-9dc1-b187a43c1d21 spec: sourcePod: network-check-source-6947749cfc-wtpb8 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-12T18:51:45Z" message: 'network-check-target-ip-10-0-141-141: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.214261ms message: 'network-check-target-ip-10-0-141-141: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:19:45Z" - latency: 974.011µs message: 'network-check-target-ip-10-0-141-141: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:18:45Z" - latency: 850.711µs message: 'network-check-target-ip-10-0-141-141: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:17:45Z" - latency: 1.308089ms message: 'network-check-target-ip-10-0-141-141: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:16:45Z" - latency: 810.737µs message: 'network-check-target-ip-10-0-141-141: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:15:45Z" - latency: 1.001685ms message: 'network-check-target-ip-10-0-141-141: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:14:45Z" - latency: 898.374µs message: 'network-check-target-ip-10-0-141-141: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:13:45Z" - latency: 1.426612ms message: 'network-check-target-ip-10-0-141-141: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:12:45Z" - latency: 1.321701ms message: 'network-check-target-ip-10-0-141-141: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:11:45Z" - latency: 939.943µs message: 'network-check-target-ip-10-0-141-141: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:10:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T18:44:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-141-to-network-check-target-ip-10-0-141-181 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-141.ec2.internal uid: 0a6debd6-6f45-4836-ad09-15cfa1ea59a6 resourceVersion: "51570" uid: a360af48-fd11-465e-bc11-c2857b2bab11 spec: sourcePod: network-check-source-6947749cfc-wtpb8 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-12T18:51:45Z" message: 'network-check-target-ip-10-0-141-181: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.108742ms message: 'network-check-target-ip-10-0-141-181: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:19:45Z" - latency: 2.999261ms message: 'network-check-target-ip-10-0-141-181: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:18:45Z" - latency: 2.160383ms message: 'network-check-target-ip-10-0-141-181: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:17:45Z" - latency: 2.014664ms message: 'network-check-target-ip-10-0-141-181: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:16:45Z" - latency: 2.131167ms message: 'network-check-target-ip-10-0-141-181: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:15:45Z" - latency: 2.356459ms message: 'network-check-target-ip-10-0-141-181: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:14:45Z" - latency: 2.021409ms message: 'network-check-target-ip-10-0-141-181: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:13:45Z" - latency: 2.349925ms message: 'network-check-target-ip-10-0-141-181: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:12:45Z" - latency: 2.477706ms message: 'network-check-target-ip-10-0-141-181: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:11:45Z" - latency: 2.032519ms message: 'network-check-target-ip-10-0-141-181: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:10:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T18:44:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-141-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-141.ec2.internal uid: 0a6debd6-6f45-4836-ad09-15cfa1ea59a6 resourceVersion: "52629" uid: a28c0053-3d3c-4fdd-a11d-62446065c174 spec: sourcePod: network-check-source-6947749cfc-wtpb8 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-12T18:50:45Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 941.993µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:20:45Z" - latency: 1.940907ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T19:20:45Z" - latency: 992.371µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:19:45Z" - latency: 2.080634ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T19:19:45Z" - latency: 980.298µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:18:45Z" - latency: 1.856599ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T19:18:45Z" - latency: 1.194495ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:17:45Z" - latency: 1.816505ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T19:17:45Z" - latency: 1.032592ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:16:45Z" - latency: 1.614634ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T19:16:45Z" kind: List metadata: resourceVersion: ""