apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T01:21:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-161-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-161.ec2.internal uid: a938069a-68e8-4384-8515-6ba4d05cbceb resourceVersion: "45414" uid: 3190bd48-b9e4-41ae-ba2d-9ce33626f1c6 spec: sourcePod: network-check-source-dbd9cf844-ngl8x targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-09T01:28:09Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.249824ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:49:09Z" - latency: 1.060994ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:48:09Z" - latency: 931.62µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:47:09Z" - latency: 1.182599ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:46:09Z" - latency: 1.294122ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:45:09Z" - latency: 824.252µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:44:09Z" - latency: 1.156326ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:43:09Z" - latency: 1.327769ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:42:09Z" - latency: 1.346708ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:41:09Z" - latency: 819.14µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:40:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T01:21:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-161-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-161.ec2.internal uid: a938069a-68e8-4384-8515-6ba4d05cbceb resourceVersion: "47395" uid: 17bfa9cb-5e7a-4cc3-b6b3-9e243e2e6f68 spec: sourcePod: network-check-source-dbd9cf844-ngl8x targetEndpoint: ab9388bdc25b1422d98ec8e0a74ae4c6-d03cd4a512b59850.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T01:27:09Z" message: 'load-balancer-api-external: tcp connection to ab9388bdc25b1422d98ec8e0a74ae4c6-d03cd4a512b59850.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.088772ms message: 'load-balancer-api-external: tcp connection to ab9388bdc25b1422d98ec8e0a74ae4c6-d03cd4a512b59850.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:51:09Z" - latency: 10.656903ms message: 'load-balancer-api-external: resolved host name ab9388bdc25b1422d98ec8e0a74ae4c6-d03cd4a512b59850.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T01:51:09Z" - latency: 3.92ms message: 'load-balancer-api-external: tcp connection to ab9388bdc25b1422d98ec8e0a74ae4c6-d03cd4a512b59850.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:50:09Z" - latency: 8.505408ms message: 'load-balancer-api-external: resolved host name ab9388bdc25b1422d98ec8e0a74ae4c6-d03cd4a512b59850.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T01:50:09Z" - latency: 5.030431ms message: 'load-balancer-api-external: tcp connection to ab9388bdc25b1422d98ec8e0a74ae4c6-d03cd4a512b59850.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:49:09Z" - latency: 7.71639ms message: 'load-balancer-api-external: resolved host name ab9388bdc25b1422d98ec8e0a74ae4c6-d03cd4a512b59850.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T01:49:09Z" - latency: 5.425156ms message: 'load-balancer-api-external: tcp connection to ab9388bdc25b1422d98ec8e0a74ae4c6-d03cd4a512b59850.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:48:09Z" - latency: 9.615241ms message: 'load-balancer-api-external: resolved host name ab9388bdc25b1422d98ec8e0a74ae4c6-d03cd4a512b59850.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T01:48:09Z" - latency: 5.917236ms message: 'load-balancer-api-external: tcp connection to ab9388bdc25b1422d98ec8e0a74ae4c6-d03cd4a512b59850.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:47:09Z" - latency: 6.776137ms message: 'load-balancer-api-external: resolved host name ab9388bdc25b1422d98ec8e0a74ae4c6-d03cd4a512b59850.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T01:47:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T01:21:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-161-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-161.ec2.internal uid: a938069a-68e8-4384-8515-6ba4d05cbceb resourceVersion: "47396" uid: f04a2994-44fe-43bc-9a27-7457c1b9ab2a spec: sourcePod: network-check-source-dbd9cf844-ngl8x targetEndpoint: ab9388bdc25b1422d98ec8e0a74ae4c6-d03cd4a512b59850.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T01:27:09Z" message: 'load-balancer-api-internal: tcp connection to ab9388bdc25b1422d98ec8e0a74ae4c6-d03cd4a512b59850.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.828896ms message: 'load-balancer-api-internal: tcp connection to ab9388bdc25b1422d98ec8e0a74ae4c6-d03cd4a512b59850.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:51:09Z" - latency: 10.576612ms message: 'load-balancer-api-internal: resolved host name ab9388bdc25b1422d98ec8e0a74ae4c6-d03cd4a512b59850.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T01:51:09Z" - latency: 4.436602ms message: 'load-balancer-api-internal: tcp connection to ab9388bdc25b1422d98ec8e0a74ae4c6-d03cd4a512b59850.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:50:09Z" - latency: 8.420914ms message: 'load-balancer-api-internal: resolved host name ab9388bdc25b1422d98ec8e0a74ae4c6-d03cd4a512b59850.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T01:50:09Z" - latency: 4.992865ms message: 'load-balancer-api-internal: tcp connection to ab9388bdc25b1422d98ec8e0a74ae4c6-d03cd4a512b59850.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:49:09Z" - latency: 7.657273ms message: 'load-balancer-api-internal: resolved host name ab9388bdc25b1422d98ec8e0a74ae4c6-d03cd4a512b59850.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T01:49:09Z" - latency: 5.685294ms message: 'load-balancer-api-internal: tcp connection to ab9388bdc25b1422d98ec8e0a74ae4c6-d03cd4a512b59850.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:48:09Z" - latency: 9.548532ms message: 'load-balancer-api-internal: resolved host name ab9388bdc25b1422d98ec8e0a74ae4c6-d03cd4a512b59850.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T01:48:09Z" - latency: 5.851339ms message: 'load-balancer-api-internal: tcp connection to ab9388bdc25b1422d98ec8e0a74ae4c6-d03cd4a512b59850.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:47:09Z" - latency: 6.729853ms message: 'load-balancer-api-internal: resolved host name ab9388bdc25b1422d98ec8e0a74ae4c6-d03cd4a512b59850.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T01:47:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T01:21:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-161-to-network-check-target-ip-10-0-129-196 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-161.ec2.internal uid: a938069a-68e8-4384-8515-6ba4d05cbceb resourceVersion: "45413" uid: 3fad6411-e728-4365-92dc-a73aaf9ac427 spec: sourcePod: network-check-source-dbd9cf844-ngl8x targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-09T01:28:09Z" message: 'network-check-target-ip-10-0-129-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.444797ms message: 'network-check-target-ip-10-0-129-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:49:09Z" - latency: 2.171147ms message: 'network-check-target-ip-10-0-129-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:48:09Z" - latency: 2.494464ms message: 'network-check-target-ip-10-0-129-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:47:09Z" - latency: 2.070919ms message: 'network-check-target-ip-10-0-129-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:46:09Z" - latency: 2.212589ms message: 'network-check-target-ip-10-0-129-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:45:09Z" - latency: 2.13209ms message: 'network-check-target-ip-10-0-129-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:44:09Z" - latency: 1.919463ms message: 'network-check-target-ip-10-0-129-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:43:09Z" - latency: 1.862802ms message: 'network-check-target-ip-10-0-129-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:42:09Z" - latency: 2.192472ms message: 'network-check-target-ip-10-0-129-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:41:09Z" - latency: 1.874897ms message: 'network-check-target-ip-10-0-129-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:40:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T01:21:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-161-to-network-check-target-ip-10-0-137-100 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-161.ec2.internal uid: a938069a-68e8-4384-8515-6ba4d05cbceb resourceVersion: "45412" uid: 197aed15-12df-472d-b45a-32d64c10cd59 spec: sourcePod: network-check-source-dbd9cf844-ngl8x targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-09T01:28:09Z" message: 'network-check-target-ip-10-0-137-100: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.900818ms message: 'network-check-target-ip-10-0-137-100: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:49:09Z" - latency: 2.052569ms message: 'network-check-target-ip-10-0-137-100: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:48:09Z" - latency: 2.031843ms message: 'network-check-target-ip-10-0-137-100: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:47:09Z" - latency: 1.899799ms message: 'network-check-target-ip-10-0-137-100: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:46:09Z" - latency: 1.963588ms message: 'network-check-target-ip-10-0-137-100: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:45:09Z" - latency: 1.531348ms message: 'network-check-target-ip-10-0-137-100: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:44:09Z" - latency: 1.974049ms message: 'network-check-target-ip-10-0-137-100: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:43:09Z" - latency: 1.870518ms message: 'network-check-target-ip-10-0-137-100: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:42:09Z" - latency: 1.860166ms message: 'network-check-target-ip-10-0-137-100: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:41:09Z" - latency: 1.551528ms message: 'network-check-target-ip-10-0-137-100: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:40:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T01:21:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-161-to-network-check-target-ip-10-0-143-161 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-161.ec2.internal uid: a938069a-68e8-4384-8515-6ba4d05cbceb resourceVersion: "45411" uid: dbe6fc73-1ed6-495d-b698-995f16d46ca9 spec: sourcePod: network-check-source-dbd9cf844-ngl8x targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-09T01:28:09Z" message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.69228ms message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:49:09Z" - latency: 961.718µs message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:48:09Z" - latency: 936.291µs message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:47:09Z" - latency: 856.382µs message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:46:09Z" - latency: 956.788µs message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:45:09Z" - latency: 975.069µs message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:44:09Z" - latency: 1.36857ms message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:43:09Z" - latency: 980.403µs message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:42:09Z" - latency: 960.374µs message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:41:09Z" - latency: 1.069237ms message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:40:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T01:21:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-161-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-161.ec2.internal uid: a938069a-68e8-4384-8515-6ba4d05cbceb resourceVersion: "47394" uid: 68ea1960-2312-48b6-8e3c-e39c52ccb970 spec: sourcePod: network-check-source-dbd9cf844-ngl8x targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-09T01:27:09Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.122732ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:51:09Z" - latency: 2.798184ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T01:51:09Z" - latency: 1.028142ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:50:09Z" - latency: 1.847121ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T01:50:09Z" - latency: 944.336µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:49:09Z" - latency: 2.033474ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T01:49:09Z" - latency: 1.044078ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:48:09Z" - latency: 1.831886ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T01:48:09Z" - latency: 790.358µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T01:47:09Z" - latency: 1.723093ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T01:47:09Z" kind: List metadata: resourceVersion: ""