apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T15:06:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-102-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-102.ec2.internal uid: 40ad9a55-4e4a-49c8-848e-f650b22c73fc resourceVersion: "30610" uid: 3d1bc46f-d566-4f5a-bdac-91dce158398b spec: sourcePod: network-check-source-dbd9cf844-v29gc targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-09T15:13:42Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.109652ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:20:42Z" - latency: 1.375317ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:19:42Z" - latency: 1.596245ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:18:42Z" - latency: 906.964µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:17:42Z" - latency: 930.615µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:16:42Z" - latency: 1.149175ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:15:42Z" - latency: 936.189µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:14:42Z" - latency: 1.067317ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:13:42Z" - latency: 1.145872ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:12:42Z" - latency: 1.270309ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:11:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T15:06:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-102-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-102.ec2.internal uid: 40ad9a55-4e4a-49c8-848e-f650b22c73fc resourceVersion: "28836" uid: 7e28adea-6341-4922-9338-0a325f112af4 spec: sourcePod: network-check-source-dbd9cf844-v29gc targetEndpoint: a76c1c794258b4668b3efd9cd47730eb-d19e2666a5841eb9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T15:12:42Z" message: 'load-balancer-api-external: tcp connection to a76c1c794258b4668b3efd9cd47730eb-d19e2666a5841eb9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.901735ms message: 'load-balancer-api-external: tcp connection to a76c1c794258b4668b3efd9cd47730eb-d19e2666a5841eb9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:18:42Z" - latency: 13.088509ms message: 'load-balancer-api-external: resolved host name a76c1c794258b4668b3efd9cd47730eb-d19e2666a5841eb9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T15:18:42Z" - latency: 4.568537ms message: 'load-balancer-api-external: tcp connection to a76c1c794258b4668b3efd9cd47730eb-d19e2666a5841eb9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:17:42Z" - latency: 8.022046ms message: 'load-balancer-api-external: resolved host name a76c1c794258b4668b3efd9cd47730eb-d19e2666a5841eb9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T15:17:42Z" - latency: 4.950155ms message: 'load-balancer-api-external: tcp connection to a76c1c794258b4668b3efd9cd47730eb-d19e2666a5841eb9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:16:42Z" - latency: 13.611768ms message: 'load-balancer-api-external: resolved host name a76c1c794258b4668b3efd9cd47730eb-d19e2666a5841eb9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T15:16:42Z" - latency: 4.857451ms message: 'load-balancer-api-external: tcp connection to a76c1c794258b4668b3efd9cd47730eb-d19e2666a5841eb9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:15:42Z" - latency: 9.025925ms message: 'load-balancer-api-external: resolved host name a76c1c794258b4668b3efd9cd47730eb-d19e2666a5841eb9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T15:15:42Z" - latency: 5.899818ms message: 'load-balancer-api-external: tcp connection to a76c1c794258b4668b3efd9cd47730eb-d19e2666a5841eb9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:14:42Z" - latency: 13.196311ms message: 'load-balancer-api-external: resolved host name a76c1c794258b4668b3efd9cd47730eb-d19e2666a5841eb9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T15:14:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T15:06:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-102-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-102.ec2.internal uid: 40ad9a55-4e4a-49c8-848e-f650b22c73fc resourceVersion: "28837" uid: 97dfb913-6593-436a-bb41-eaa0d0c9f740 spec: sourcePod: network-check-source-dbd9cf844-v29gc targetEndpoint: a76c1c794258b4668b3efd9cd47730eb-d19e2666a5841eb9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T15:12:42Z" message: 'load-balancer-api-internal: tcp connection to a76c1c794258b4668b3efd9cd47730eb-d19e2666a5841eb9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.844842ms message: 'load-balancer-api-internal: tcp connection to a76c1c794258b4668b3efd9cd47730eb-d19e2666a5841eb9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:18:42Z" - latency: 13.133735ms message: 'load-balancer-api-internal: resolved host name a76c1c794258b4668b3efd9cd47730eb-d19e2666a5841eb9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T15:18:42Z" - latency: 4.532949ms message: 'load-balancer-api-internal: tcp connection to a76c1c794258b4668b3efd9cd47730eb-d19e2666a5841eb9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:17:42Z" - latency: 8.058854ms message: 'load-balancer-api-internal: resolved host name a76c1c794258b4668b3efd9cd47730eb-d19e2666a5841eb9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T15:17:42Z" - latency: 4.938946ms message: 'load-balancer-api-internal: tcp connection to a76c1c794258b4668b3efd9cd47730eb-d19e2666a5841eb9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:16:42Z" - latency: 13.642263ms message: 'load-balancer-api-internal: resolved host name a76c1c794258b4668b3efd9cd47730eb-d19e2666a5841eb9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T15:16:42Z" - latency: 4.844355ms message: 'load-balancer-api-internal: tcp connection to a76c1c794258b4668b3efd9cd47730eb-d19e2666a5841eb9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:15:42Z" - latency: 9.06506ms message: 'load-balancer-api-internal: resolved host name a76c1c794258b4668b3efd9cd47730eb-d19e2666a5841eb9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T15:15:42Z" - latency: 5.911105ms message: 'load-balancer-api-internal: tcp connection to a76c1c794258b4668b3efd9cd47730eb-d19e2666a5841eb9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:14:42Z" - latency: 13.307084ms message: 'load-balancer-api-internal: resolved host name a76c1c794258b4668b3efd9cd47730eb-d19e2666a5841eb9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T15:14:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T15:06:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-102-to-network-check-target-ip-10-0-133-102 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-102.ec2.internal uid: 40ad9a55-4e4a-49c8-848e-f650b22c73fc resourceVersion: "30607" uid: 660566a6-2f5a-4cc1-abce-842c46de9d87 spec: sourcePod: network-check-source-dbd9cf844-v29gc targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-09T15:13:42Z" message: 'network-check-target-ip-10-0-133-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.10934ms message: 'network-check-target-ip-10-0-133-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:20:42Z" - latency: 842.329µs message: 'network-check-target-ip-10-0-133-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:19:42Z" - latency: 1.259389ms message: 'network-check-target-ip-10-0-133-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:18:42Z" - latency: 1.040926ms message: 'network-check-target-ip-10-0-133-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:17:42Z" - latency: 1.159999ms message: 'network-check-target-ip-10-0-133-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:16:42Z" - latency: 1.318544ms message: 'network-check-target-ip-10-0-133-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:15:42Z" - latency: 899.492µs message: 'network-check-target-ip-10-0-133-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:14:42Z" - latency: 861.642µs message: 'network-check-target-ip-10-0-133-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:13:42Z" - latency: 1.282082ms message: 'network-check-target-ip-10-0-133-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:12:42Z" - latency: 1.317288ms message: 'network-check-target-ip-10-0-133-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:11:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T15:06:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-102-to-network-check-target-ip-10-0-133-239 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-102.ec2.internal uid: 40ad9a55-4e4a-49c8-848e-f650b22c73fc resourceVersion: "30609" uid: e6cb3f56-1fdd-40ee-8539-83301ba321a5 spec: sourcePod: network-check-source-dbd9cf844-v29gc targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-09T15:13:42Z" message: 'network-check-target-ip-10-0-133-239: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.380101ms message: 'network-check-target-ip-10-0-133-239: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:20:42Z" - latency: 2.349396ms message: 'network-check-target-ip-10-0-133-239: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:19:42Z" - latency: 2.201617ms message: 'network-check-target-ip-10-0-133-239: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:18:42Z" - latency: 2.418079ms message: 'network-check-target-ip-10-0-133-239: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:17:42Z" - latency: 2.219865ms message: 'network-check-target-ip-10-0-133-239: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:16:42Z" - latency: 2.471973ms message: 'network-check-target-ip-10-0-133-239: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:15:42Z" - latency: 2.425142ms message: 'network-check-target-ip-10-0-133-239: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:14:42Z" - latency: 2.346175ms message: 'network-check-target-ip-10-0-133-239: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:13:42Z" - latency: 2.375323ms message: 'network-check-target-ip-10-0-133-239: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:12:42Z" - latency: 2.113072ms message: 'network-check-target-ip-10-0-133-239: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:11:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T15:06:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-102-to-network-check-target-ip-10-0-143-92 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-102.ec2.internal uid: 40ad9a55-4e4a-49c8-848e-f650b22c73fc resourceVersion: "30608" uid: 9043cb63-e065-46bc-a792-1933eac137d4 spec: sourcePod: network-check-source-dbd9cf844-v29gc targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-09T15:13:42Z" message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.546954ms message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:20:42Z" - latency: 2.377062ms message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:19:42Z" - latency: 2.861812ms message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:18:42Z" - latency: 2.459505ms message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:17:42Z" - latency: 2.199398ms message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:16:42Z" - latency: 2.572525ms message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:15:42Z" - latency: 2.135865ms message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:14:42Z" - latency: 2.410771ms message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:13:42Z" - latency: 2.281186ms message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:12:42Z" - latency: 2.330034ms message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:11:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T15:06:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-102-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-102.ec2.internal uid: 40ad9a55-4e4a-49c8-848e-f650b22c73fc resourceVersion: "28835" uid: e3e01d11-95f9-4bfd-b657-72cd0522dbff spec: sourcePod: network-check-source-dbd9cf844-v29gc targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-09T15:12:42Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 890.505µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:18:42Z" - latency: 1.999193ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T15:18:42Z" - latency: 806.486µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:17:42Z" - latency: 1.655251ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T15:17:42Z" - latency: 1.196912ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:16:42Z" - latency: 1.806261ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T15:16:42Z" - latency: 955.188µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:15:42Z" - latency: 1.683613ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T15:15:42Z" - latency: 1.085561ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:14:42Z" - latency: 1.903857ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T15:14:42Z" kind: List metadata: resourceVersion: ""