apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T15:00:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-141-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-141.ec2.internal uid: b5355411-3d25-476c-8284-1f9d93a4e001 resourceVersion: "21689" uid: 94a88bcc-d4a6-4de4-88dc-528082be580f spec: sourcePod: network-check-source-989f8b8dc-w4xx7 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-07T15:07:28Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.006492ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:21:28Z" - latency: 1.486778ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:20:28Z" - latency: 1.508414ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:19:28Z" - latency: 1.015274ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:18:28Z" - latency: 1.221048ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:17:28Z" - latency: 1.02144ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:16:28Z" - latency: 1.492149ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:15:28Z" - latency: 1.029887ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:14:28Z" - latency: 1.033158ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:13:28Z" - latency: 939.563µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:12:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T15:00:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-141-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-141.ec2.internal uid: b5355411-3d25-476c-8284-1f9d93a4e001 resourceVersion: "20069" uid: 9160c00f-cf77-4d7a-8554-196457f0757e spec: sourcePod: network-check-source-989f8b8dc-w4xx7 targetEndpoint: abe54032370c34f799007317e76ed07f-acd64eb330580da5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T15:06:28Z" message: 'load-balancer-api-external: tcp connection to abe54032370c34f799007317e76ed07f-acd64eb330580da5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.021268ms message: 'load-balancer-api-external: tcp connection to abe54032370c34f799007317e76ed07f-acd64eb330580da5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:18:28Z" - latency: 8.455135ms message: 'load-balancer-api-external: resolved host name abe54032370c34f799007317e76ed07f-acd64eb330580da5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T15:18:28Z" - latency: 5.140566ms message: 'load-balancer-api-external: tcp connection to abe54032370c34f799007317e76ed07f-acd64eb330580da5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:17:28Z" - latency: 8.879015ms message: 'load-balancer-api-external: resolved host name abe54032370c34f799007317e76ed07f-acd64eb330580da5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T15:17:28Z" - latency: 4.29819ms message: 'load-balancer-api-external: tcp connection to abe54032370c34f799007317e76ed07f-acd64eb330580da5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:16:28Z" - latency: 8.200718ms message: 'load-balancer-api-external: resolved host name abe54032370c34f799007317e76ed07f-acd64eb330580da5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T15:16:28Z" - latency: 5.05847ms message: 'load-balancer-api-external: tcp connection to abe54032370c34f799007317e76ed07f-acd64eb330580da5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:15:28Z" - latency: 9.670886ms message: 'load-balancer-api-external: resolved host name abe54032370c34f799007317e76ed07f-acd64eb330580da5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T15:15:28Z" - latency: 4.405331ms message: 'load-balancer-api-external: tcp connection to abe54032370c34f799007317e76ed07f-acd64eb330580da5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:14:28Z" - latency: 8.912216ms message: 'load-balancer-api-external: resolved host name abe54032370c34f799007317e76ed07f-acd64eb330580da5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T15:14:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T15:00:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-141-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-141.ec2.internal uid: b5355411-3d25-476c-8284-1f9d93a4e001 resourceVersion: "20070" uid: 9121b281-6ed1-4e96-b9d1-aefd41f9c00a spec: sourcePod: network-check-source-989f8b8dc-w4xx7 targetEndpoint: abe54032370c34f799007317e76ed07f-acd64eb330580da5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T15:06:28Z" message: 'load-balancer-api-internal: tcp connection to abe54032370c34f799007317e76ed07f-acd64eb330580da5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.207578ms message: 'load-balancer-api-internal: tcp connection to abe54032370c34f799007317e76ed07f-acd64eb330580da5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:18:28Z" - latency: 8.329899ms message: 'load-balancer-api-internal: resolved host name abe54032370c34f799007317e76ed07f-acd64eb330580da5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T15:18:28Z" - latency: 5.487889ms message: 'load-balancer-api-internal: tcp connection to abe54032370c34f799007317e76ed07f-acd64eb330580da5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:17:28Z" - latency: 8.826844ms message: 'load-balancer-api-internal: resolved host name abe54032370c34f799007317e76ed07f-acd64eb330580da5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T15:17:28Z" - latency: 4.142863ms message: 'load-balancer-api-internal: tcp connection to abe54032370c34f799007317e76ed07f-acd64eb330580da5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:16:28Z" - latency: 8.159776ms message: 'load-balancer-api-internal: resolved host name abe54032370c34f799007317e76ed07f-acd64eb330580da5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T15:16:28Z" - latency: 5.059227ms message: 'load-balancer-api-internal: tcp connection to abe54032370c34f799007317e76ed07f-acd64eb330580da5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:15:28Z" - latency: 9.598516ms message: 'load-balancer-api-internal: resolved host name abe54032370c34f799007317e76ed07f-acd64eb330580da5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T15:15:28Z" - latency: 4.439872ms message: 'load-balancer-api-internal: tcp connection to abe54032370c34f799007317e76ed07f-acd64eb330580da5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:14:28Z" - latency: 8.848162ms message: 'load-balancer-api-internal: resolved host name abe54032370c34f799007317e76ed07f-acd64eb330580da5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T15:14:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T15:00:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-141-to-network-check-target-ip-10-0-130-141 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-141.ec2.internal uid: b5355411-3d25-476c-8284-1f9d93a4e001 resourceVersion: "21685" uid: 54907a41-c864-4b5e-b8ec-2d3afe8f50f7 spec: sourcePod: network-check-source-989f8b8dc-w4xx7 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-07T15:07:28Z" message: 'network-check-target-ip-10-0-130-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 950.88µs message: 'network-check-target-ip-10-0-130-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:21:28Z" - latency: 966.136µs message: 'network-check-target-ip-10-0-130-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:20:28Z" - latency: 1.085256ms message: 'network-check-target-ip-10-0-130-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:19:28Z" - latency: 1.081728ms message: 'network-check-target-ip-10-0-130-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:18:28Z" - latency: 952.765µs message: 'network-check-target-ip-10-0-130-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:17:28Z" - latency: 987.22µs message: 'network-check-target-ip-10-0-130-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:16:28Z" - latency: 1.429465ms message: 'network-check-target-ip-10-0-130-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:15:28Z" - latency: 1.017644ms message: 'network-check-target-ip-10-0-130-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:14:28Z" - latency: 1.332591ms message: 'network-check-target-ip-10-0-130-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:13:28Z" - latency: 770.369µs message: 'network-check-target-ip-10-0-130-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:12:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T15:00:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-141-to-network-check-target-ip-10-0-138-241 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-141.ec2.internal uid: b5355411-3d25-476c-8284-1f9d93a4e001 resourceVersion: "21688" uid: 296b58e7-a2e9-492c-9375-c14ff53bfa8f spec: sourcePod: network-check-source-989f8b8dc-w4xx7 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-07T15:07:28Z" message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.374946ms message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:21:28Z" - latency: 2.380778ms message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:20:28Z" - latency: 2.426059ms message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:19:28Z" - latency: 2.253556ms message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:18:28Z" - latency: 2.234988ms message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:17:28Z" - latency: 2.307544ms message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:16:28Z" - latency: 2.366303ms message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:15:28Z" - latency: 2.435455ms message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:14:28Z" - latency: 2.238724ms message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:13:28Z" - latency: 2.287572ms message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:12:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T15:00:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-141-to-network-check-target-ip-10-0-143-168 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-141.ec2.internal uid: b5355411-3d25-476c-8284-1f9d93a4e001 resourceVersion: "21687" uid: 4e575a86-0d0f-43dd-8154-e510e4e83ecd spec: sourcePod: network-check-source-989f8b8dc-w4xx7 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-07T15:07:28Z" message: 'network-check-target-ip-10-0-143-168: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.202941ms message: 'network-check-target-ip-10-0-143-168: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:21:28Z" - latency: 2.298235ms message: 'network-check-target-ip-10-0-143-168: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:20:28Z" - latency: 2.293982ms message: 'network-check-target-ip-10-0-143-168: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:19:28Z" - latency: 2.256588ms message: 'network-check-target-ip-10-0-143-168: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:18:28Z" - latency: 2.034679ms message: 'network-check-target-ip-10-0-143-168: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:17:28Z" - latency: 2.246713ms message: 'network-check-target-ip-10-0-143-168: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:16:28Z" - latency: 2.211249ms message: 'network-check-target-ip-10-0-143-168: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:15:28Z" - latency: 2.465978ms message: 'network-check-target-ip-10-0-143-168: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:14:28Z" - latency: 2.352168ms message: 'network-check-target-ip-10-0-143-168: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:13:28Z" - latency: 2.292206ms message: 'network-check-target-ip-10-0-143-168: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:12:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T15:00:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-141-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-141.ec2.internal uid: b5355411-3d25-476c-8284-1f9d93a4e001 resourceVersion: "20068" uid: 9b9cb7ed-51a1-4ba1-82d2-41ac6aba35e2 spec: sourcePod: network-check-source-989f8b8dc-w4xx7 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-07T15:06:28Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.33012ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:18:28Z" - latency: 1.905199ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T15:18:28Z" - latency: 1.24984ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:17:28Z" - latency: 1.939094ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T15:17:28Z" - latency: 1.28656ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:16:28Z" - latency: 1.844218ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T15:16:28Z" - latency: 874.991µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:15:28Z" - latency: 2.074252ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T15:15:28Z" - latency: 1.455034ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:14:28Z" - latency: 2.087903ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T15:14:28Z" kind: List metadata: resourceVersion: ""