apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T14:34:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-108-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-108.ec2.internal uid: 821f9e5e-c349-4651-a63c-3efd0581014c resourceVersion: "48275" uid: e486c2ff-3cb1-493c-96d5-011e0896e3a1 spec: sourcePod: network-check-source-dbd9cf844-zk897 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-11T14:41:53Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.480779ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:09:53Z" - latency: 1.249502ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:08:53Z" - latency: 1.670355ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:07:53Z" - latency: 1.221646ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:06:53Z" - latency: 953.127µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:05:53Z" - latency: 1.068846ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:04:53Z" - latency: 1.029429ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:03:53Z" - latency: 1.1095ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:02:53Z" - latency: 864.632µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:01:53Z" - latency: 1.230312ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:00:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T14:34:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-108-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-108.ec2.internal uid: 821f9e5e-c349-4651-a63c-3efd0581014c resourceVersion: "43579" uid: 5547f7d9-0bb5-48d4-91d5-f95179980a79 spec: sourcePod: network-check-source-dbd9cf844-zk897 targetEndpoint: a394bde3fb98a43aa9eed18113679d65-fd07ef6d81c13e4f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T14:40:53Z" message: 'load-balancer-api-external: tcp connection to a394bde3fb98a43aa9eed18113679d65-fd07ef6d81c13e4f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.054648ms message: 'load-balancer-api-external: tcp connection to a394bde3fb98a43aa9eed18113679d65-fd07ef6d81c13e4f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:04:53Z" - latency: 9.890326ms message: 'load-balancer-api-external: resolved host name a394bde3fb98a43aa9eed18113679d65-fd07ef6d81c13e4f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:04:53Z" - latency: 4.075932ms message: 'load-balancer-api-external: tcp connection to a394bde3fb98a43aa9eed18113679d65-fd07ef6d81c13e4f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:03:53Z" - latency: 9.04061ms message: 'load-balancer-api-external: resolved host name a394bde3fb98a43aa9eed18113679d65-fd07ef6d81c13e4f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:03:53Z" - latency: 5.186496ms message: 'load-balancer-api-external: tcp connection to a394bde3fb98a43aa9eed18113679d65-fd07ef6d81c13e4f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:02:53Z" - latency: 10.026799ms message: 'load-balancer-api-external: resolved host name a394bde3fb98a43aa9eed18113679d65-fd07ef6d81c13e4f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:02:53Z" - latency: 4.303422ms message: 'load-balancer-api-external: tcp connection to a394bde3fb98a43aa9eed18113679d65-fd07ef6d81c13e4f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:01:53Z" - latency: 9.210098ms message: 'load-balancer-api-external: resolved host name a394bde3fb98a43aa9eed18113679d65-fd07ef6d81c13e4f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:01:53Z" - latency: 5.356898ms message: 'load-balancer-api-external: tcp connection to a394bde3fb98a43aa9eed18113679d65-fd07ef6d81c13e4f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:00:53Z" - latency: 9.920001ms message: 'load-balancer-api-external: resolved host name a394bde3fb98a43aa9eed18113679d65-fd07ef6d81c13e4f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:00:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T14:34:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-108-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-108.ec2.internal uid: 821f9e5e-c349-4651-a63c-3efd0581014c resourceVersion: "43578" uid: 04891eeb-b867-424c-8bb4-ff3a49c004b2 spec: sourcePod: network-check-source-dbd9cf844-zk897 targetEndpoint: a394bde3fb98a43aa9eed18113679d65-fd07ef6d81c13e4f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T14:40:53Z" message: 'load-balancer-api-internal: tcp connection to a394bde3fb98a43aa9eed18113679d65-fd07ef6d81c13e4f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.815127ms message: 'load-balancer-api-internal: tcp connection to a394bde3fb98a43aa9eed18113679d65-fd07ef6d81c13e4f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:04:53Z" - latency: 10.510671ms message: 'load-balancer-api-internal: resolved host name a394bde3fb98a43aa9eed18113679d65-fd07ef6d81c13e4f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:04:53Z" - latency: 4.083025ms message: 'load-balancer-api-internal: tcp connection to a394bde3fb98a43aa9eed18113679d65-fd07ef6d81c13e4f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:03:53Z" - latency: 8.785579ms message: 'load-balancer-api-internal: resolved host name a394bde3fb98a43aa9eed18113679d65-fd07ef6d81c13e4f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:03:53Z" - latency: 5.196081ms message: 'load-balancer-api-internal: tcp connection to a394bde3fb98a43aa9eed18113679d65-fd07ef6d81c13e4f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:02:53Z" - latency: 10.131916ms message: 'load-balancer-api-internal: resolved host name a394bde3fb98a43aa9eed18113679d65-fd07ef6d81c13e4f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:02:53Z" - latency: 4.765705ms message: 'load-balancer-api-internal: tcp connection to a394bde3fb98a43aa9eed18113679d65-fd07ef6d81c13e4f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:01:53Z" - latency: 9.170393ms message: 'load-balancer-api-internal: resolved host name a394bde3fb98a43aa9eed18113679d65-fd07ef6d81c13e4f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:01:53Z" - latency: 3.82995ms message: 'load-balancer-api-internal: tcp connection to a394bde3fb98a43aa9eed18113679d65-fd07ef6d81c13e4f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:00:53Z" - latency: 10.019598ms message: 'load-balancer-api-internal: resolved host name a394bde3fb98a43aa9eed18113679d65-fd07ef6d81c13e4f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:00:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T14:34:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-108-to-network-check-target-ip-10-0-128-209 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-108.ec2.internal uid: 821f9e5e-c349-4651-a63c-3efd0581014c resourceVersion: "48274" uid: 1a734b31-ca18-4e09-8796-cc6b8bbcfd35 spec: sourcePod: network-check-source-dbd9cf844-zk897 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-11T14:41:53Z" message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.609489ms message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:09:53Z" - latency: 2.8041ms message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:08:53Z" - latency: 2.80409ms message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:07:53Z" - latency: 2.593421ms message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:06:53Z" - latency: 2.300789ms message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:05:53Z" - latency: 2.7248ms message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:04:53Z" - latency: 2.629523ms message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:03:53Z" - latency: 2.158359ms message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:02:53Z" - latency: 2.370512ms message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:01:53Z" - latency: 2.653434ms message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:00:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T14:34:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-108-to-network-check-target-ip-10-0-135-108 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-108.ec2.internal uid: 821f9e5e-c349-4651-a63c-3efd0581014c resourceVersion: "48272" uid: 590b8fcb-8a35-4b9c-9712-0aa78a50266b spec: sourcePod: network-check-source-dbd9cf844-zk897 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-11T14:41:53Z" message: 'network-check-target-ip-10-0-135-108: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.439311ms message: 'network-check-target-ip-10-0-135-108: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:09:53Z" - latency: 1.479838ms message: 'network-check-target-ip-10-0-135-108: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:08:53Z" - latency: 836.431µs message: 'network-check-target-ip-10-0-135-108: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:07:53Z" - latency: 1.800203ms message: 'network-check-target-ip-10-0-135-108: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:06:53Z" - latency: 827.727µs message: 'network-check-target-ip-10-0-135-108: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:05:53Z" - latency: 2.38862ms message: 'network-check-target-ip-10-0-135-108: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:04:53Z" - latency: 1.649897ms message: 'network-check-target-ip-10-0-135-108: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:03:53Z" - latency: 1.843254ms message: 'network-check-target-ip-10-0-135-108: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:02:53Z" - latency: 1.096124ms message: 'network-check-target-ip-10-0-135-108: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:01:53Z" - latency: 1.638675ms message: 'network-check-target-ip-10-0-135-108: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:00:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T14:34:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-108-to-network-check-target-ip-10-0-140-206 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-108.ec2.internal uid: 821f9e5e-c349-4651-a63c-3efd0581014c resourceVersion: "48273" uid: 3a8fa7a6-542c-4ec7-851c-68d6288f8c98 spec: sourcePod: network-check-source-dbd9cf844-zk897 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-11T14:41:53Z" message: 'network-check-target-ip-10-0-140-206: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.333476ms message: 'network-check-target-ip-10-0-140-206: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:09:53Z" - latency: 3.056833ms message: 'network-check-target-ip-10-0-140-206: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:08:53Z" - latency: 2.64561ms message: 'network-check-target-ip-10-0-140-206: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:07:53Z" - latency: 2.678436ms message: 'network-check-target-ip-10-0-140-206: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:06:53Z" - latency: 2.701207ms message: 'network-check-target-ip-10-0-140-206: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:05:53Z" - latency: 2.619899ms message: 'network-check-target-ip-10-0-140-206: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:04:53Z" - latency: 2.314391ms message: 'network-check-target-ip-10-0-140-206: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:03:53Z" - latency: 2.264496ms message: 'network-check-target-ip-10-0-140-206: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:02:53Z" - latency: 2.43996ms message: 'network-check-target-ip-10-0-140-206: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:01:53Z" - latency: 2.597108ms message: 'network-check-target-ip-10-0-140-206: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:00:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T14:34:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-108-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-108.ec2.internal uid: 821f9e5e-c349-4651-a63c-3efd0581014c resourceVersion: "43577" uid: 8724d25f-c6d0-4b0e-8574-0894da2b3cb6 spec: sourcePod: network-check-source-dbd9cf844-zk897 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-11T14:40:53Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 716.642µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:04:53Z" - latency: 3.330784ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T15:04:53Z" - latency: 1.023859ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:03:53Z" - latency: 1.652751ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T15:03:53Z" - latency: 913.479µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:02:53Z" - latency: 1.906843ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T15:02:53Z" - latency: 975.987µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:01:53Z" - latency: 2.540223ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T15:01:53Z" - latency: 1.101494ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:00:53Z" - latency: 1.908963ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T15:00:53Z" kind: List metadata: resourceVersion: ""