apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T03:00:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-129-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-129.ec2.internal uid: 00f42b16-5bce-40a9-9e45-bf13b48fbf5f resourceVersion: "14618" uid: 0e87d99f-0edf-4fc4-8208-4e7d075eedd6 spec: sourcePod: network-check-source-7cbc45fddc-qj94j targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-18T03:07:58Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 885.002µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:07:58Z" - latency: 834.576µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:06:58Z" - latency: 806.406µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:05:58Z" - latency: 1.208793ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:04:58Z" - latency: 874.566µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:03:58Z" - latency: 1.196198ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:02:58Z" - latency: 1.064454ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:01:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T03:00:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-129-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-129.ec2.internal uid: 00f42b16-5bce-40a9-9e45-bf13b48fbf5f resourceVersion: "14204" uid: 6d807272-a2ec-483e-b2ae-ae9c906e03bf spec: sourcePod: network-check-source-7cbc45fddc-qj94j targetEndpoint: a1776f1b1e0254f2587e8f9eaa9edcd6-0d75a6a54283be58.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-18T03:06:58Z" message: 'load-balancer-api-external: tcp connection to a1776f1b1e0254f2587e8f9eaa9edcd6-0d75a6a54283be58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.918447ms message: 'load-balancer-api-external: tcp connection to a1776f1b1e0254f2587e8f9eaa9edcd6-0d75a6a54283be58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:06:58Z" - latency: 9.185924ms message: 'load-balancer-api-external: resolved host name a1776f1b1e0254f2587e8f9eaa9edcd6-0d75a6a54283be58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T03:06:58Z" - latency: 4.970869ms message: 'load-balancer-api-external: tcp connection to a1776f1b1e0254f2587e8f9eaa9edcd6-0d75a6a54283be58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:05:58Z" - latency: 8.145711ms message: 'load-balancer-api-external: resolved host name a1776f1b1e0254f2587e8f9eaa9edcd6-0d75a6a54283be58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T03:05:58Z" - latency: 18.585123ms message: 'load-balancer-api-external: tcp connection to a1776f1b1e0254f2587e8f9eaa9edcd6-0d75a6a54283be58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:04:58Z" - latency: 7.142238ms message: 'load-balancer-api-external: resolved host name a1776f1b1e0254f2587e8f9eaa9edcd6-0d75a6a54283be58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T03:04:58Z" - latency: 12.32982ms message: 'load-balancer-api-external: tcp connection to a1776f1b1e0254f2587e8f9eaa9edcd6-0d75a6a54283be58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:03:58Z" - latency: 8.742804ms message: 'load-balancer-api-external: resolved host name a1776f1b1e0254f2587e8f9eaa9edcd6-0d75a6a54283be58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T03:03:58Z" - latency: 5.588775ms message: 'load-balancer-api-external: tcp connection to a1776f1b1e0254f2587e8f9eaa9edcd6-0d75a6a54283be58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:02:58Z" - latency: 9.15173ms message: 'load-balancer-api-external: resolved host name a1776f1b1e0254f2587e8f9eaa9edcd6-0d75a6a54283be58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T03:02:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T03:00:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-129-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-129.ec2.internal uid: 00f42b16-5bce-40a9-9e45-bf13b48fbf5f resourceVersion: "14205" uid: ac3e22b2-e499-4c3f-9ca1-3b15779a4255 spec: sourcePod: network-check-source-7cbc45fddc-qj94j targetEndpoint: a1776f1b1e0254f2587e8f9eaa9edcd6-0d75a6a54283be58.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-18T03:06:58Z" message: 'load-balancer-api-internal: tcp connection to a1776f1b1e0254f2587e8f9eaa9edcd6-0d75a6a54283be58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.943862ms message: 'load-balancer-api-internal: tcp connection to a1776f1b1e0254f2587e8f9eaa9edcd6-0d75a6a54283be58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:06:58Z" - latency: 9.144628ms message: 'load-balancer-api-internal: resolved host name a1776f1b1e0254f2587e8f9eaa9edcd6-0d75a6a54283be58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T03:06:58Z" - latency: 4.043077ms message: 'load-balancer-api-internal: tcp connection to a1776f1b1e0254f2587e8f9eaa9edcd6-0d75a6a54283be58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:05:58Z" - latency: 8.112477ms message: 'load-balancer-api-internal: resolved host name a1776f1b1e0254f2587e8f9eaa9edcd6-0d75a6a54283be58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T03:05:58Z" - latency: 6.825822ms message: 'load-balancer-api-internal: tcp connection to a1776f1b1e0254f2587e8f9eaa9edcd6-0d75a6a54283be58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:04:58Z" - latency: 7.09409ms message: 'load-balancer-api-internal: resolved host name a1776f1b1e0254f2587e8f9eaa9edcd6-0d75a6a54283be58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T03:04:58Z" - latency: 8.086276ms message: 'load-balancer-api-internal: tcp connection to a1776f1b1e0254f2587e8f9eaa9edcd6-0d75a6a54283be58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:03:58Z" - latency: 8.707848ms message: 'load-balancer-api-internal: resolved host name a1776f1b1e0254f2587e8f9eaa9edcd6-0d75a6a54283be58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T03:03:58Z" - latency: 5.549617ms message: 'load-balancer-api-internal: tcp connection to a1776f1b1e0254f2587e8f9eaa9edcd6-0d75a6a54283be58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:02:58Z" - latency: 9.117802ms message: 'load-balancer-api-internal: resolved host name a1776f1b1e0254f2587e8f9eaa9edcd6-0d75a6a54283be58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T03:02:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T03:00:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-129-to-network-check-target-ip-10-0-134-116 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-129.ec2.internal uid: 00f42b16-5bce-40a9-9e45-bf13b48fbf5f resourceVersion: "14617" uid: 841be97e-6ae9-4403-af41-daaa3c33e7ee spec: sourcePod: network-check-source-7cbc45fddc-qj94j targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-18T03:07:58Z" message: 'network-check-target-ip-10-0-134-116: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.107207ms message: 'network-check-target-ip-10-0-134-116: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:07:58Z" - latency: 2.297985ms message: 'network-check-target-ip-10-0-134-116: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:06:58Z" - latency: 1.810123ms message: 'network-check-target-ip-10-0-134-116: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:05:58Z" - latency: 2.148698ms message: 'network-check-target-ip-10-0-134-116: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:04:58Z" - latency: 2.027685ms message: 'network-check-target-ip-10-0-134-116: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:03:58Z" - latency: 2.048935ms message: 'network-check-target-ip-10-0-134-116: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:02:58Z" - latency: 2.269256ms message: 'network-check-target-ip-10-0-134-116: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:01:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T03:00:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-129-to-network-check-target-ip-10-0-134-53 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-129.ec2.internal uid: 00f42b16-5bce-40a9-9e45-bf13b48fbf5f resourceVersion: "14616" uid: 1104f268-1faf-487a-adb1-b5d494ce30f5 spec: sourcePod: network-check-source-7cbc45fddc-qj94j targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-18T03:07:58Z" message: 'network-check-target-ip-10-0-134-53: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.044286ms message: 'network-check-target-ip-10-0-134-53: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:07:58Z" - latency: 1.920687ms message: 'network-check-target-ip-10-0-134-53: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:06:58Z" - latency: 1.520866ms message: 'network-check-target-ip-10-0-134-53: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:05:58Z" - latency: 1.614322ms message: 'network-check-target-ip-10-0-134-53: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:04:58Z" - latency: 2.401919ms message: 'network-check-target-ip-10-0-134-53: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:03:58Z" - latency: 1.575999ms message: 'network-check-target-ip-10-0-134-53: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:02:58Z" - latency: 1.774413ms message: 'network-check-target-ip-10-0-134-53: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:01:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T03:00:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-129-to-network-check-target-ip-10-0-138-129 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-129.ec2.internal uid: 00f42b16-5bce-40a9-9e45-bf13b48fbf5f resourceVersion: "14615" uid: 6ab61630-6746-488c-83d5-999c85597c60 spec: sourcePod: network-check-source-7cbc45fddc-qj94j targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-18T03:07:58Z" message: 'network-check-target-ip-10-0-138-129: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 920.586µs message: 'network-check-target-ip-10-0-138-129: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:07:58Z" - latency: 1.50235ms message: 'network-check-target-ip-10-0-138-129: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:06:58Z" - latency: 956.777µs message: 'network-check-target-ip-10-0-138-129: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:05:58Z" - latency: 949.275µs message: 'network-check-target-ip-10-0-138-129: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:04:58Z" - latency: 941.775µs message: 'network-check-target-ip-10-0-138-129: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:03:58Z" - latency: 881.715µs message: 'network-check-target-ip-10-0-138-129: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:02:58Z" - latency: 1.864182ms message: 'network-check-target-ip-10-0-138-129: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:01:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T03:00:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-129-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-129.ec2.internal uid: 00f42b16-5bce-40a9-9e45-bf13b48fbf5f resourceVersion: "14203" uid: da8d42ae-7280-4265-afc7-6e7bad47d47a spec: sourcePod: network-check-source-7cbc45fddc-qj94j targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-18T03:06:58Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 965.855µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:06:58Z" - latency: 2.31066ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-18T03:06:58Z" - latency: 772.547µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:05:58Z" - latency: 1.876324ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-18T03:05:58Z" - latency: 5.673078ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:04:58Z" - latency: 1.783033ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-18T03:04:58Z" - latency: 979.514µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:03:58Z" - latency: 1.819469ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-18T03:03:58Z" - latency: 1.145157ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-18T03:02:58Z" - latency: 1.898749ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-18T03:02:58Z" kind: List metadata: resourceVersion: ""