apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T19:43:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-103-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-103.ec2.internal uid: 565e6330-fb30-4a3a-b20d-747e477c99fd resourceVersion: "45263" uid: 85210e6c-5fd9-4ba0-8395-c510525e5f6b spec: sourcePod: network-check-source-56d84b9f44-9prxw targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-02T19:50:21Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.070421ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:11:21Z" - latency: 930.52µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:10:21Z" - latency: 1.053747ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:09:21Z" - latency: 1.023618ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:08:21Z" - latency: 1.277288ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:07:21Z" - latency: 1.243797ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:06:21Z" - latency: 823.026µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:05:21Z" - latency: 1.174078ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:04:21Z" - latency: 805.514µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:03:21Z" - latency: 807.552µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:02:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T19:43:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-103-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-103.ec2.internal uid: 565e6330-fb30-4a3a-b20d-747e477c99fd resourceVersion: "47367" uid: 9d06d231-d4db-4718-90cc-424776fd6099 spec: sourcePod: network-check-source-56d84b9f44-9prxw targetEndpoint: a102071a9b7ef44d6978e07c7a0f74ea-2033df6c2b7fa237.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-02T19:49:21Z" message: 'load-balancer-api-external: tcp connection to a102071a9b7ef44d6978e07c7a0f74ea-2033df6c2b7fa237.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.228013ms message: 'load-balancer-api-external: tcp connection to a102071a9b7ef44d6978e07c7a0f74ea-2033df6c2b7fa237.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:13:21Z" - latency: 10.376655ms message: 'load-balancer-api-external: resolved host name a102071a9b7ef44d6978e07c7a0f74ea-2033df6c2b7fa237.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T20:13:21Z" - latency: 4.563323ms message: 'load-balancer-api-external: tcp connection to a102071a9b7ef44d6978e07c7a0f74ea-2033df6c2b7fa237.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:12:21Z" - latency: 10.174221ms message: 'load-balancer-api-external: resolved host name a102071a9b7ef44d6978e07c7a0f74ea-2033df6c2b7fa237.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T20:12:21Z" - latency: 4.427744ms message: 'load-balancer-api-external: tcp connection to a102071a9b7ef44d6978e07c7a0f74ea-2033df6c2b7fa237.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:11:21Z" - latency: 15.688931ms message: 'load-balancer-api-external: resolved host name a102071a9b7ef44d6978e07c7a0f74ea-2033df6c2b7fa237.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T20:11:21Z" - latency: 4.83248ms message: 'load-balancer-api-external: tcp connection to a102071a9b7ef44d6978e07c7a0f74ea-2033df6c2b7fa237.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:10:21Z" - latency: 7.756344ms message: 'load-balancer-api-external: resolved host name a102071a9b7ef44d6978e07c7a0f74ea-2033df6c2b7fa237.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T20:10:21Z" - latency: 4.447113ms message: 'load-balancer-api-external: tcp connection to a102071a9b7ef44d6978e07c7a0f74ea-2033df6c2b7fa237.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:09:21Z" - latency: 12.80884ms message: 'load-balancer-api-external: resolved host name a102071a9b7ef44d6978e07c7a0f74ea-2033df6c2b7fa237.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T20:09:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T19:43:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-103-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-103.ec2.internal uid: 565e6330-fb30-4a3a-b20d-747e477c99fd resourceVersion: "47368" uid: dea32ffc-d75c-4ad4-afa5-4da731c08437 spec: sourcePod: network-check-source-56d84b9f44-9prxw targetEndpoint: a102071a9b7ef44d6978e07c7a0f74ea-2033df6c2b7fa237.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-02T19:49:21Z" message: 'load-balancer-api-internal: tcp connection to a102071a9b7ef44d6978e07c7a0f74ea-2033df6c2b7fa237.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.385289ms message: 'load-balancer-api-internal: tcp connection to a102071a9b7ef44d6978e07c7a0f74ea-2033df6c2b7fa237.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:13:21Z" - latency: 10.34506ms message: 'load-balancer-api-internal: resolved host name a102071a9b7ef44d6978e07c7a0f74ea-2033df6c2b7fa237.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T20:13:21Z" - latency: 4.62164ms message: 'load-balancer-api-internal: tcp connection to a102071a9b7ef44d6978e07c7a0f74ea-2033df6c2b7fa237.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:12:21Z" - latency: 10.130218ms message: 'load-balancer-api-internal: resolved host name a102071a9b7ef44d6978e07c7a0f74ea-2033df6c2b7fa237.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T20:12:21Z" - latency: 3.859948ms message: 'load-balancer-api-internal: tcp connection to a102071a9b7ef44d6978e07c7a0f74ea-2033df6c2b7fa237.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:11:21Z" - latency: 15.740121ms message: 'load-balancer-api-internal: resolved host name a102071a9b7ef44d6978e07c7a0f74ea-2033df6c2b7fa237.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T20:11:21Z" - latency: 4.224117ms message: 'load-balancer-api-internal: tcp connection to a102071a9b7ef44d6978e07c7a0f74ea-2033df6c2b7fa237.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:10:21Z" - latency: 7.802585ms message: 'load-balancer-api-internal: resolved host name a102071a9b7ef44d6978e07c7a0f74ea-2033df6c2b7fa237.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T20:10:21Z" - latency: 3.9107ms message: 'load-balancer-api-internal: tcp connection to a102071a9b7ef44d6978e07c7a0f74ea-2033df6c2b7fa237.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:09:21Z" - latency: 12.841454ms message: 'load-balancer-api-internal: resolved host name a102071a9b7ef44d6978e07c7a0f74ea-2033df6c2b7fa237.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T20:09:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T19:43:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-103-to-network-check-target-ip-10-0-130-103 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-103.ec2.internal uid: 565e6330-fb30-4a3a-b20d-747e477c99fd resourceVersion: "45260" uid: 936e0cca-5b68-407e-8f31-3d3add6a952f spec: sourcePod: network-check-source-56d84b9f44-9prxw targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-02T19:50:21Z" message: 'network-check-target-ip-10-0-130-103: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 944.955µs message: 'network-check-target-ip-10-0-130-103: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:11:21Z" - latency: 841.768µs message: 'network-check-target-ip-10-0-130-103: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:10:21Z" - latency: 768.63µs message: 'network-check-target-ip-10-0-130-103: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:09:21Z" - latency: 800.487µs message: 'network-check-target-ip-10-0-130-103: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:08:21Z" - latency: 950.089µs message: 'network-check-target-ip-10-0-130-103: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:07:21Z" - latency: 1.386523ms message: 'network-check-target-ip-10-0-130-103: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:06:21Z" - latency: 672.724µs message: 'network-check-target-ip-10-0-130-103: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:05:21Z" - latency: 827.883µs message: 'network-check-target-ip-10-0-130-103: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:04:21Z" - latency: 852.914µs message: 'network-check-target-ip-10-0-130-103: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:03:21Z" - latency: 840.852µs message: 'network-check-target-ip-10-0-130-103: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:02:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T19:43:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-103-to-network-check-target-ip-10-0-137-56 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-103.ec2.internal uid: 565e6330-fb30-4a3a-b20d-747e477c99fd resourceVersion: "45261" uid: 0f1ac03d-6026-4e39-828c-97a66b03d37f spec: sourcePod: network-check-source-56d84b9f44-9prxw targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-02T19:50:21Z" message: 'network-check-target-ip-10-0-137-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.968879ms message: 'network-check-target-ip-10-0-137-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:11:21Z" - latency: 2.223231ms message: 'network-check-target-ip-10-0-137-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:10:21Z" - latency: 1.965584ms message: 'network-check-target-ip-10-0-137-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:09:21Z" - latency: 2.237223ms message: 'network-check-target-ip-10-0-137-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:08:21Z" - latency: 2.344921ms message: 'network-check-target-ip-10-0-137-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:07:21Z" - latency: 2.77553ms message: 'network-check-target-ip-10-0-137-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:06:21Z" - latency: 1.712602ms message: 'network-check-target-ip-10-0-137-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:05:21Z" - latency: 2.373844ms message: 'network-check-target-ip-10-0-137-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:04:21Z" - latency: 2.188774ms message: 'network-check-target-ip-10-0-137-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:03:21Z" - latency: 2.176148ms message: 'network-check-target-ip-10-0-137-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:02:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T19:43:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-103-to-network-check-target-ip-10-0-142-203 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-103.ec2.internal uid: 565e6330-fb30-4a3a-b20d-747e477c99fd resourceVersion: "45262" uid: 8d24b1c8-54d4-4dcb-b06b-80127987bf55 spec: sourcePod: network-check-source-56d84b9f44-9prxw targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-02T19:50:21Z" message: 'network-check-target-ip-10-0-142-203: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.251441ms message: 'network-check-target-ip-10-0-142-203: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:11:21Z" - latency: 2.301296ms message: 'network-check-target-ip-10-0-142-203: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:10:21Z" - latency: 2.393856ms message: 'network-check-target-ip-10-0-142-203: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:09:21Z" - latency: 2.140448ms message: 'network-check-target-ip-10-0-142-203: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:08:21Z" - latency: 2.287484ms message: 'network-check-target-ip-10-0-142-203: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:07:21Z" - latency: 2.155914ms message: 'network-check-target-ip-10-0-142-203: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:06:21Z" - latency: 1.951299ms message: 'network-check-target-ip-10-0-142-203: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:05:21Z" - latency: 2.202976ms message: 'network-check-target-ip-10-0-142-203: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:04:21Z" - latency: 2.135699ms message: 'network-check-target-ip-10-0-142-203: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:03:21Z" - latency: 2.283985ms message: 'network-check-target-ip-10-0-142-203: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:02:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T19:43:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-103-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-103.ec2.internal uid: 565e6330-fb30-4a3a-b20d-747e477c99fd resourceVersion: "47366" uid: 01c63437-da86-43cc-93b3-60c7fe6f60d5 spec: sourcePod: network-check-source-56d84b9f44-9prxw targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-02T19:49:21Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.070885ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:13:21Z" - latency: 1.625188ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T20:13:21Z" - latency: 647.781µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:12:21Z" - latency: 1.480008ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T20:12:21Z" - latency: 808.567µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:11:21Z" - latency: 1.902601ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T20:11:21Z" - latency: 950.764µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:10:21Z" - latency: 1.7665ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T20:10:21Z" - latency: 1.116465ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:09:21Z" - latency: 1.885973ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T20:09:21Z" kind: List metadata: resourceVersion: ""