apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T21:12:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-214-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-214.ec2.internal uid: 187a1294-578a-4817-8761-4667f64f9667 resourceVersion: "23886" uid: 6135c417-05df-491d-85ca-452bf3d3886b spec: sourcePod: network-check-source-dbd9cf844-zqn2w targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-08T21:19:57Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.558799ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:19:57Z" - latency: 835.442µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:18:57Z" - latency: 1.250265ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:17:57Z" - latency: 1.35398ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:16:57Z" - latency: 1.207074ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:15:57Z" - latency: 1.337275ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:14:57Z" - latency: 868.498µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:13:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T21:12:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-214-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-214.ec2.internal uid: 187a1294-578a-4817-8761-4667f64f9667 resourceVersion: "28827" uid: 109a53a6-2c76-4896-ae41-e338de867d0c spec: sourcePod: network-check-source-dbd9cf844-zqn2w targetEndpoint: ad3718ed0603d4300bb360d45d832477-4950c44c4c17f78d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-08T21:18:57Z" message: 'load-balancer-api-external: tcp connection to ad3718ed0603d4300bb360d45d832477-4950c44c4c17f78d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.313937ms message: 'load-balancer-api-external: tcp connection to ad3718ed0603d4300bb360d45d832477-4950c44c4c17f78d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:24:57Z" - latency: 7.04577ms message: 'load-balancer-api-external: resolved host name ad3718ed0603d4300bb360d45d832477-4950c44c4c17f78d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T21:24:57Z" - latency: 4.069598ms message: 'load-balancer-api-external: tcp connection to ad3718ed0603d4300bb360d45d832477-4950c44c4c17f78d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:23:57Z" - latency: 7.032444ms message: 'load-balancer-api-external: resolved host name ad3718ed0603d4300bb360d45d832477-4950c44c4c17f78d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T21:23:57Z" - latency: 4.461675ms message: 'load-balancer-api-external: tcp connection to ad3718ed0603d4300bb360d45d832477-4950c44c4c17f78d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:22:57Z" - latency: 8.349697ms message: 'load-balancer-api-external: resolved host name ad3718ed0603d4300bb360d45d832477-4950c44c4c17f78d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T21:22:57Z" - latency: 3.671697ms message: 'load-balancer-api-external: tcp connection to ad3718ed0603d4300bb360d45d832477-4950c44c4c17f78d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:21:57Z" - latency: 8.084791ms message: 'load-balancer-api-external: resolved host name ad3718ed0603d4300bb360d45d832477-4950c44c4c17f78d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T21:21:57Z" - latency: 4.983156ms message: 'load-balancer-api-external: tcp connection to ad3718ed0603d4300bb360d45d832477-4950c44c4c17f78d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:20:57Z" - latency: 11.504003ms message: 'load-balancer-api-external: resolved host name ad3718ed0603d4300bb360d45d832477-4950c44c4c17f78d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T21:20:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T21:12:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-214-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-214.ec2.internal uid: 187a1294-578a-4817-8761-4667f64f9667 resourceVersion: "28828" uid: 79d201ec-a571-4588-9f0d-c0219127a8fd spec: sourcePod: network-check-source-dbd9cf844-zqn2w targetEndpoint: ad3718ed0603d4300bb360d45d832477-4950c44c4c17f78d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-08T21:18:57Z" message: 'load-balancer-api-internal: tcp connection to ad3718ed0603d4300bb360d45d832477-4950c44c4c17f78d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.328593ms message: 'load-balancer-api-internal: tcp connection to ad3718ed0603d4300bb360d45d832477-4950c44c4c17f78d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:24:57Z" - latency: 7.112943ms message: 'load-balancer-api-internal: resolved host name ad3718ed0603d4300bb360d45d832477-4950c44c4c17f78d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T21:24:57Z" - latency: 4.130966ms message: 'load-balancer-api-internal: tcp connection to ad3718ed0603d4300bb360d45d832477-4950c44c4c17f78d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:23:57Z" - latency: 7.069825ms message: 'load-balancer-api-internal: resolved host name ad3718ed0603d4300bb360d45d832477-4950c44c4c17f78d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T21:23:57Z" - latency: 4.451011ms message: 'load-balancer-api-internal: tcp connection to ad3718ed0603d4300bb360d45d832477-4950c44c4c17f78d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:22:57Z" - latency: 8.409358ms message: 'load-balancer-api-internal: resolved host name ad3718ed0603d4300bb360d45d832477-4950c44c4c17f78d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T21:22:57Z" - latency: 3.664235ms message: 'load-balancer-api-internal: tcp connection to ad3718ed0603d4300bb360d45d832477-4950c44c4c17f78d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:21:57Z" - latency: 8.111638ms message: 'load-balancer-api-internal: resolved host name ad3718ed0603d4300bb360d45d832477-4950c44c4c17f78d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T21:21:57Z" - latency: 4.990272ms message: 'load-balancer-api-internal: tcp connection to ad3718ed0603d4300bb360d45d832477-4950c44c4c17f78d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:20:57Z" - latency: 9.824685ms message: 'load-balancer-api-internal: resolved host name ad3718ed0603d4300bb360d45d832477-4950c44c4c17f78d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T21:20:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T21:12:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-214-to-network-check-target-ip-10-0-133-247 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-214.ec2.internal uid: 187a1294-578a-4817-8761-4667f64f9667 resourceVersion: "23885" uid: eaf319e0-fbec-4e80-92ca-4e3710563318 spec: sourcePod: network-check-source-dbd9cf844-zqn2w targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-08T21:19:57Z" message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.852545ms message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:19:57Z" - latency: 2.159644ms message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:18:57Z" - latency: 2.084519ms message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:17:57Z" - latency: 2.19274ms message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:16:57Z" - latency: 2.251163ms message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:15:57Z" - latency: 2.060418ms message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:14:57Z" - latency: 2.378324ms message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:13:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T21:12:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-214-to-network-check-target-ip-10-0-139-156 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-214.ec2.internal uid: 187a1294-578a-4817-8761-4667f64f9667 resourceVersion: "23883" uid: 64cc4ca0-2bd9-4486-b5fb-c4f6be939bbb spec: sourcePod: network-check-source-dbd9cf844-zqn2w targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-08T21:19:57Z" message: 'network-check-target-ip-10-0-139-156: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.358254ms message: 'network-check-target-ip-10-0-139-156: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:19:57Z" - latency: 2.200007ms message: 'network-check-target-ip-10-0-139-156: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:18:57Z" - latency: 2.159701ms message: 'network-check-target-ip-10-0-139-156: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:17:57Z" - latency: 2.082011ms message: 'network-check-target-ip-10-0-139-156: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:16:57Z" - latency: 2.844781ms message: 'network-check-target-ip-10-0-139-156: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:15:57Z" - latency: 2.049532ms message: 'network-check-target-ip-10-0-139-156: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:14:57Z" - latency: 1.82394ms message: 'network-check-target-ip-10-0-139-156: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:13:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T21:12:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-214-to-network-check-target-ip-10-0-140-214 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-214.ec2.internal uid: 187a1294-578a-4817-8761-4667f64f9667 resourceVersion: "23884" uid: b331ede7-4cff-4b69-b27e-b09825e67951 spec: sourcePod: network-check-source-dbd9cf844-zqn2w targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-08T21:19:57Z" message: 'network-check-target-ip-10-0-140-214: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.38446ms message: 'network-check-target-ip-10-0-140-214: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:19:57Z" - latency: 812.076µs message: 'network-check-target-ip-10-0-140-214: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:18:57Z" - latency: 1.583385ms message: 'network-check-target-ip-10-0-140-214: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:17:57Z" - latency: 778.554µs message: 'network-check-target-ip-10-0-140-214: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:16:57Z" - latency: 1.915767ms message: 'network-check-target-ip-10-0-140-214: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:15:57Z" - latency: 712.134µs message: 'network-check-target-ip-10-0-140-214: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:14:57Z" - latency: 1.097718ms message: 'network-check-target-ip-10-0-140-214: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:13:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T21:12:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-214-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-214.ec2.internal uid: 187a1294-578a-4817-8761-4667f64f9667 resourceVersion: "28826" uid: 9ea6b5a5-1247-42c4-9366-e9f6759651da spec: sourcePod: network-check-source-dbd9cf844-zqn2w targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-08T21:18:57Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 899.805µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:24:57Z" - latency: 1.666772ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T21:24:57Z" - latency: 1.197344ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:23:57Z" - latency: 1.771436ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T21:23:57Z" - latency: 1.197953ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:22:57Z" - latency: 1.867358ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T21:22:57Z" - latency: 888.815µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:21:57Z" - latency: 2.156215ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T21:21:57Z" - latency: 848.181µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T21:20:57Z" - latency: 7.043376ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T21:20:57Z" kind: List metadata: resourceVersion: ""