apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T13:06:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-1-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-1.ec2.internal uid: 8f4b881c-82f7-41b7-ad45-b7fd003bb87c resourceVersion: "29060" uid: 0bd8ffad-c6e5-4156-a235-728feb14fd46 spec: sourcePod: network-check-source-dbd9cf844-lcw7q targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-05T13:13:59Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 846.36µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:20:59Z" - latency: 1.099369ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:19:59Z" - latency: 842.454µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:18:59Z" - latency: 955.821µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:17:59Z" - latency: 1.573275ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:16:59Z" - latency: 1.047208ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:15:59Z" - latency: 1.1164ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:14:59Z" - latency: 1.740921ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:13:59Z" - latency: 922.283µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:12:59Z" - latency: 870.407µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:11:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T13:06:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-1-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-1.ec2.internal uid: 8f4b881c-82f7-41b7-ad45-b7fd003bb87c resourceVersion: "27615" uid: e84d5987-db7b-411c-8095-fcc96c9b3b8e spec: sourcePod: network-check-source-dbd9cf844-lcw7q targetEndpoint: a94d2ef6f173940cea0ce5ec3f9e88b9-cc6824ddee02a47e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-05T13:12:59Z" message: 'load-balancer-api-external: tcp connection to a94d2ef6f173940cea0ce5ec3f9e88b9-cc6824ddee02a47e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.783941ms message: 'load-balancer-api-external: tcp connection to a94d2ef6f173940cea0ce5ec3f9e88b9-cc6824ddee02a47e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:18:59Z" - latency: 8.993583ms message: 'load-balancer-api-external: resolved host name a94d2ef6f173940cea0ce5ec3f9e88b9-cc6824ddee02a47e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T13:18:59Z" - latency: 5.915404ms message: 'load-balancer-api-external: tcp connection to a94d2ef6f173940cea0ce5ec3f9e88b9-cc6824ddee02a47e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:17:59Z" - latency: 10.547243ms message: 'load-balancer-api-external: resolved host name a94d2ef6f173940cea0ce5ec3f9e88b9-cc6824ddee02a47e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T13:17:59Z" - latency: 6.079489ms message: 'load-balancer-api-external: tcp connection to a94d2ef6f173940cea0ce5ec3f9e88b9-cc6824ddee02a47e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:16:59Z" - latency: 8.663754ms message: 'load-balancer-api-external: resolved host name a94d2ef6f173940cea0ce5ec3f9e88b9-cc6824ddee02a47e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T13:16:59Z" - latency: 5.304295ms message: 'load-balancer-api-external: tcp connection to a94d2ef6f173940cea0ce5ec3f9e88b9-cc6824ddee02a47e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:15:59Z" - latency: 8.13116ms message: 'load-balancer-api-external: resolved host name a94d2ef6f173940cea0ce5ec3f9e88b9-cc6824ddee02a47e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T13:15:59Z" - latency: 5.511476ms message: 'load-balancer-api-external: tcp connection to a94d2ef6f173940cea0ce5ec3f9e88b9-cc6824ddee02a47e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:14:59Z" - latency: 8.218972ms message: 'load-balancer-api-external: resolved host name a94d2ef6f173940cea0ce5ec3f9e88b9-cc6824ddee02a47e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T13:14:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T13:06:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-1-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-1.ec2.internal uid: 8f4b881c-82f7-41b7-ad45-b7fd003bb87c resourceVersion: "27616" uid: fdbd2f65-a939-431d-a768-0108647fb87f spec: sourcePod: network-check-source-dbd9cf844-lcw7q targetEndpoint: a94d2ef6f173940cea0ce5ec3f9e88b9-cc6824ddee02a47e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-05T13:12:59Z" message: 'load-balancer-api-internal: tcp connection to a94d2ef6f173940cea0ce5ec3f9e88b9-cc6824ddee02a47e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.759782ms message: 'load-balancer-api-internal: tcp connection to a94d2ef6f173940cea0ce5ec3f9e88b9-cc6824ddee02a47e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:18:59Z" - latency: 9.070473ms message: 'load-balancer-api-internal: resolved host name a94d2ef6f173940cea0ce5ec3f9e88b9-cc6824ddee02a47e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T13:18:59Z" - latency: 5.865336ms message: 'load-balancer-api-internal: tcp connection to a94d2ef6f173940cea0ce5ec3f9e88b9-cc6824ddee02a47e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:17:59Z" - latency: 10.49245ms message: 'load-balancer-api-internal: resolved host name a94d2ef6f173940cea0ce5ec3f9e88b9-cc6824ddee02a47e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T13:17:59Z" - latency: 6.091053ms message: 'load-balancer-api-internal: tcp connection to a94d2ef6f173940cea0ce5ec3f9e88b9-cc6824ddee02a47e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:16:59Z" - latency: 8.574743ms message: 'load-balancer-api-internal: resolved host name a94d2ef6f173940cea0ce5ec3f9e88b9-cc6824ddee02a47e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T13:16:59Z" - latency: 5.329402ms message: 'load-balancer-api-internal: tcp connection to a94d2ef6f173940cea0ce5ec3f9e88b9-cc6824ddee02a47e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:15:59Z" - latency: 8.044865ms message: 'load-balancer-api-internal: resolved host name a94d2ef6f173940cea0ce5ec3f9e88b9-cc6824ddee02a47e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T13:15:59Z" - latency: 5.175125ms message: 'load-balancer-api-internal: tcp connection to a94d2ef6f173940cea0ce5ec3f9e88b9-cc6824ddee02a47e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:14:59Z" - latency: 8.213463ms message: 'load-balancer-api-internal: resolved host name a94d2ef6f173940cea0ce5ec3f9e88b9-cc6824ddee02a47e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T13:14:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T13:06:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-1-to-network-check-target-ip-10-0-129-41 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-1.ec2.internal uid: 8f4b881c-82f7-41b7-ad45-b7fd003bb87c resourceVersion: "29059" uid: af0eef34-5057-46f0-a3b0-66ce9c7e7179 spec: sourcePod: network-check-source-dbd9cf844-lcw7q targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-05T13:13:59Z" message: 'network-check-target-ip-10-0-129-41: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.520043ms message: 'network-check-target-ip-10-0-129-41: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:20:59Z" - latency: 2.267267ms message: 'network-check-target-ip-10-0-129-41: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:19:59Z" - latency: 2.368519ms message: 'network-check-target-ip-10-0-129-41: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:18:59Z" - latency: 2.410308ms message: 'network-check-target-ip-10-0-129-41: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:17:59Z" - latency: 2.2626ms message: 'network-check-target-ip-10-0-129-41: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:16:59Z" - latency: 2.642737ms message: 'network-check-target-ip-10-0-129-41: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:15:59Z" - latency: 2.352283ms message: 'network-check-target-ip-10-0-129-41: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:14:59Z" - latency: 2.314323ms message: 'network-check-target-ip-10-0-129-41: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:13:59Z" - latency: 2.417617ms message: 'network-check-target-ip-10-0-129-41: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:12:59Z" - latency: 2.443097ms message: 'network-check-target-ip-10-0-129-41: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:11:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T13:06:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-1-to-network-check-target-ip-10-0-132-1 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-1.ec2.internal uid: 8f4b881c-82f7-41b7-ad45-b7fd003bb87c resourceVersion: "29056" uid: fa6c21f5-ba81-4ec1-874f-9e4067f19cee spec: sourcePod: network-check-source-dbd9cf844-lcw7q targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-05T13:13:59Z" message: 'network-check-target-ip-10-0-132-1: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 898.327µs message: 'network-check-target-ip-10-0-132-1: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:20:59Z" - latency: 899.304µs message: 'network-check-target-ip-10-0-132-1: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:19:59Z" - latency: 1.034412ms message: 'network-check-target-ip-10-0-132-1: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:18:59Z" - latency: 911.508µs message: 'network-check-target-ip-10-0-132-1: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:17:59Z" - latency: 950.75µs message: 'network-check-target-ip-10-0-132-1: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:16:59Z" - latency: 930.76µs message: 'network-check-target-ip-10-0-132-1: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:15:59Z" - latency: 997.513µs message: 'network-check-target-ip-10-0-132-1: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:14:59Z" - latency: 967.006µs message: 'network-check-target-ip-10-0-132-1: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:13:59Z" - latency: 944.225µs message: 'network-check-target-ip-10-0-132-1: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:12:59Z" - latency: 1.18839ms message: 'network-check-target-ip-10-0-132-1: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:11:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T13:06:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-1-to-network-check-target-ip-10-0-132-150 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-1.ec2.internal uid: 8f4b881c-82f7-41b7-ad45-b7fd003bb87c resourceVersion: "29058" uid: 8d6a4a45-c30d-4266-b635-942d0b5b6057 spec: sourcePod: network-check-source-dbd9cf844-lcw7q targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-05T13:13:59Z" message: 'network-check-target-ip-10-0-132-150: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.517769ms message: 'network-check-target-ip-10-0-132-150: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:20:59Z" - latency: 2.187278ms message: 'network-check-target-ip-10-0-132-150: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:19:59Z" - latency: 2.398836ms message: 'network-check-target-ip-10-0-132-150: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:18:59Z" - latency: 2.487889ms message: 'network-check-target-ip-10-0-132-150: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:17:59Z" - latency: 2.920573ms message: 'network-check-target-ip-10-0-132-150: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:16:59Z" - latency: 2.403342ms message: 'network-check-target-ip-10-0-132-150: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:15:59Z" - latency: 2.332817ms message: 'network-check-target-ip-10-0-132-150: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:14:59Z" - latency: 2.420963ms message: 'network-check-target-ip-10-0-132-150: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:13:59Z" - latency: 2.488915ms message: 'network-check-target-ip-10-0-132-150: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:12:59Z" - latency: 2.311651ms message: 'network-check-target-ip-10-0-132-150: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:11:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T13:06:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-1-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-1.ec2.internal uid: 8f4b881c-82f7-41b7-ad45-b7fd003bb87c resourceVersion: "27613" uid: 62c431ff-aacc-41b7-ac0f-0022ec74dcb4 spec: sourcePod: network-check-source-dbd9cf844-lcw7q targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-05T13:12:59Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.007214ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:18:59Z" - latency: 2.550525ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T13:18:59Z" - latency: 944.051µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:17:59Z" - latency: 1.991825ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T13:17:59Z" - latency: 725.121µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:16:59Z" - latency: 1.727535ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T13:16:59Z" - latency: 951.033µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:15:59Z" - latency: 1.928723ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T13:15:59Z" - latency: 921.08µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:14:59Z" - latency: 1.62982ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T13:14:59Z" kind: List metadata: resourceVersion: ""