apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T20:11:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-11-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-11.ec2.internal uid: b073a4d4-d7cb-434b-a22d-25d570af8600 resourceVersion: "55593" uid: a55a6db1-658a-4c95-bf7e-48e3c8b136d7 spec: sourcePod: network-check-source-869dcfcdcd-ffknd targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-10T20:18:25Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.215364ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:46:25Z" - latency: 1.143292ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:45:25Z" - latency: 1.171801ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:44:25Z" - latency: 1.025903ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:43:25Z" - latency: 1.173883ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:42:25Z" - latency: 7.334285ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:41:25Z" - latency: 2.310737ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:40:25Z" - latency: 2.629444ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:39:25Z" - latency: 1.016862ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:38:25Z" - latency: 1.510507ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:37:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T20:11:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-11-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-11.ec2.internal uid: b073a4d4-d7cb-434b-a22d-25d570af8600 resourceVersion: "56808" uid: f7cb824c-a12a-4437-884a-870e5786e210 spec: sourcePod: network-check-source-869dcfcdcd-ffknd targetEndpoint: a5e2a5c85f0f04f89ad7b610e181e92b-a3c5db16bda3d035.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T20:17:25Z" message: 'load-balancer-api-external: tcp connection to a5e2a5c85f0f04f89ad7b610e181e92b-a3c5db16bda3d035.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.954314ms message: 'load-balancer-api-external: tcp connection to a5e2a5c85f0f04f89ad7b610e181e92b-a3c5db16bda3d035.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:47:25Z" - latency: 6.905367ms message: 'load-balancer-api-external: resolved host name a5e2a5c85f0f04f89ad7b610e181e92b-a3c5db16bda3d035.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T20:47:25Z" - latency: 4.943331ms message: 'load-balancer-api-external: tcp connection to a5e2a5c85f0f04f89ad7b610e181e92b-a3c5db16bda3d035.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:46:25Z" - latency: 7.385301ms message: 'load-balancer-api-external: resolved host name a5e2a5c85f0f04f89ad7b610e181e92b-a3c5db16bda3d035.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T20:46:25Z" - latency: 3.698481ms message: 'load-balancer-api-external: tcp connection to a5e2a5c85f0f04f89ad7b610e181e92b-a3c5db16bda3d035.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:45:25Z" - latency: 6.791292ms message: 'load-balancer-api-external: resolved host name a5e2a5c85f0f04f89ad7b610e181e92b-a3c5db16bda3d035.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T20:45:25Z" - latency: 4.677733ms message: 'load-balancer-api-external: tcp connection to a5e2a5c85f0f04f89ad7b610e181e92b-a3c5db16bda3d035.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:44:25Z" - latency: 11.809598ms message: 'load-balancer-api-external: resolved host name a5e2a5c85f0f04f89ad7b610e181e92b-a3c5db16bda3d035.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T20:44:25Z" - latency: 5.42898ms message: 'load-balancer-api-external: tcp connection to a5e2a5c85f0f04f89ad7b610e181e92b-a3c5db16bda3d035.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:43:25Z" - latency: 6.438826ms message: 'load-balancer-api-external: resolved host name a5e2a5c85f0f04f89ad7b610e181e92b-a3c5db16bda3d035.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T20:43:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T20:11:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-11-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-11.ec2.internal uid: b073a4d4-d7cb-434b-a22d-25d570af8600 resourceVersion: "56807" uid: 0dad29c4-8a32-4b00-afe5-e1e54fcd1d81 spec: sourcePod: network-check-source-869dcfcdcd-ffknd targetEndpoint: a5e2a5c85f0f04f89ad7b610e181e92b-a3c5db16bda3d035.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T20:17:25Z" message: 'load-balancer-api-internal: tcp connection to a5e2a5c85f0f04f89ad7b610e181e92b-a3c5db16bda3d035.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.967638ms message: 'load-balancer-api-internal: tcp connection to a5e2a5c85f0f04f89ad7b610e181e92b-a3c5db16bda3d035.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:47:25Z" - latency: 6.868858ms message: 'load-balancer-api-internal: resolved host name a5e2a5c85f0f04f89ad7b610e181e92b-a3c5db16bda3d035.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T20:47:25Z" - latency: 4.937919ms message: 'load-balancer-api-internal: tcp connection to a5e2a5c85f0f04f89ad7b610e181e92b-a3c5db16bda3d035.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:46:25Z" - latency: 7.308024ms message: 'load-balancer-api-internal: resolved host name a5e2a5c85f0f04f89ad7b610e181e92b-a3c5db16bda3d035.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T20:46:25Z" - latency: 3.704886ms message: 'load-balancer-api-internal: tcp connection to a5e2a5c85f0f04f89ad7b610e181e92b-a3c5db16bda3d035.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:45:25Z" - latency: 6.690849ms message: 'load-balancer-api-internal: resolved host name a5e2a5c85f0f04f89ad7b610e181e92b-a3c5db16bda3d035.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T20:45:25Z" - latency: 4.672273ms message: 'load-balancer-api-internal: tcp connection to a5e2a5c85f0f04f89ad7b610e181e92b-a3c5db16bda3d035.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:44:25Z" - latency: 11.876406ms message: 'load-balancer-api-internal: resolved host name a5e2a5c85f0f04f89ad7b610e181e92b-a3c5db16bda3d035.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T20:44:25Z" - latency: 5.407619ms message: 'load-balancer-api-internal: tcp connection to a5e2a5c85f0f04f89ad7b610e181e92b-a3c5db16bda3d035.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:43:25Z" - latency: 6.378499ms message: 'load-balancer-api-internal: resolved host name a5e2a5c85f0f04f89ad7b610e181e92b-a3c5db16bda3d035.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T20:43:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T20:11:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-11-to-network-check-target-ip-10-0-132-11 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-11.ec2.internal uid: b073a4d4-d7cb-434b-a22d-25d570af8600 resourceVersion: "55590" uid: c6f3cdf5-cd60-46d8-bc3e-23ef69179264 spec: sourcePod: network-check-source-869dcfcdcd-ffknd targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-10T20:18:25Z" message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.233708ms message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:46:25Z" - latency: 1.491407ms message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:45:25Z" - latency: 973.012µs message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:44:25Z" - latency: 1.006987ms message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:43:25Z" - latency: 992.942µs message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:42:25Z" - latency: 6.871218ms message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:41:25Z" - latency: 1.505094ms message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:40:25Z" - latency: 2.985893ms message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:39:25Z" - latency: 1.239341ms message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:38:25Z" - latency: 1.000916ms message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:37:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T20:11:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-11-to-network-check-target-ip-10-0-133-106 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-11.ec2.internal uid: b073a4d4-d7cb-434b-a22d-25d570af8600 resourceVersion: "55592" uid: d1ac9775-9b5b-420f-ae86-ba96e95697d6 spec: sourcePod: network-check-source-869dcfcdcd-ffknd targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-10T20:18:25Z" message: 'network-check-target-ip-10-0-133-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.359404ms message: 'network-check-target-ip-10-0-133-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:46:25Z" - latency: 2.108743ms message: 'network-check-target-ip-10-0-133-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:45:25Z" - latency: 2.662046ms message: 'network-check-target-ip-10-0-133-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:44:25Z" - latency: 2.178994ms message: 'network-check-target-ip-10-0-133-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:43:25Z" - latency: 2.642967ms message: 'network-check-target-ip-10-0-133-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:42:25Z" - latency: 7.563235ms message: 'network-check-target-ip-10-0-133-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:41:25Z" - latency: 2.632828ms message: 'network-check-target-ip-10-0-133-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:40:25Z" - latency: 4.758253ms message: 'network-check-target-ip-10-0-133-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:39:25Z" - latency: 2.538193ms message: 'network-check-target-ip-10-0-133-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:38:25Z" - latency: 2.451344ms message: 'network-check-target-ip-10-0-133-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:37:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T20:11:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-11-to-network-check-target-ip-10-0-143-108 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-11.ec2.internal uid: b073a4d4-d7cb-434b-a22d-25d570af8600 resourceVersion: "55591" uid: bb037493-b140-42f2-bcdc-4a243dba8ba1 spec: sourcePod: network-check-source-869dcfcdcd-ffknd targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-10T20:18:25Z" message: 'network-check-target-ip-10-0-143-108: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.474847ms message: 'network-check-target-ip-10-0-143-108: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:46:25Z" - latency: 2.631485ms message: 'network-check-target-ip-10-0-143-108: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:45:25Z" - latency: 2.2339ms message: 'network-check-target-ip-10-0-143-108: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:44:25Z" - latency: 2.373091ms message: 'network-check-target-ip-10-0-143-108: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:43:25Z" - latency: 2.544153ms message: 'network-check-target-ip-10-0-143-108: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:42:25Z" - latency: 8.222927ms message: 'network-check-target-ip-10-0-143-108: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:41:25Z" - latency: 2.577252ms message: 'network-check-target-ip-10-0-143-108: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:40:25Z" - latency: 4.854874ms message: 'network-check-target-ip-10-0-143-108: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:39:25Z" - latency: 2.26822ms message: 'network-check-target-ip-10-0-143-108: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:38:25Z" - latency: 2.354929ms message: 'network-check-target-ip-10-0-143-108: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:37:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T20:11:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-11-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-11.ec2.internal uid: b073a4d4-d7cb-434b-a22d-25d570af8600 resourceVersion: "56806" uid: d137e855-808f-4c87-91df-3d6503495439 spec: sourcePod: network-check-source-869dcfcdcd-ffknd targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-10T20:17:25Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.350271ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:47:25Z" - latency: 1.770333ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T20:47:25Z" - latency: 1.175233ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:46:25Z" - latency: 2.193582ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T20:46:25Z" - latency: 894.426µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:45:25Z" - latency: 2.110459ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T20:45:25Z" - latency: 804.649µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:44:25Z" - latency: 2.175591ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T20:44:25Z" - latency: 844.655µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T20:43:25Z" - latency: 1.787564ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T20:43:25Z" kind: List metadata: resourceVersion: ""