apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T20:07:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-118-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-118.ec2.internal uid: d3b49909-26f0-41c4-921c-2f636a31def1 resourceVersion: "46090" uid: 3c49451e-5816-42d1-b5cb-8f7f53b5b3b4 spec: sourcePod: network-check-source-56d84b9f44-smjxr targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-02T20:14:54Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 802.606µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:35:54Z" - latency: 1.091546ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:34:54Z" - latency: 1.508976ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:33:54Z" - latency: 847.434µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:32:54Z" - latency: 903.207µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:31:54Z" - latency: 1.003988ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:30:54Z" - latency: 1.106381ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:29:54Z" - latency: 1.754512ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:28:54Z" - latency: 1.377714ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:27:54Z" - latency: 675.722µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:26:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T20:07:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-118-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-118.ec2.internal uid: d3b49909-26f0-41c4-921c-2f636a31def1 resourceVersion: "48226" uid: 8767dbdb-e6af-49a1-b52b-0469c5eab3b0 spec: sourcePod: network-check-source-56d84b9f44-smjxr targetEndpoint: af5597669a0ff4ee889c283f78c94f5b-5fc33a70d14b866a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-02T20:13:54Z" message: 'load-balancer-api-external: tcp connection to af5597669a0ff4ee889c283f78c94f5b-5fc33a70d14b866a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.985349ms message: 'load-balancer-api-external: tcp connection to af5597669a0ff4ee889c283f78c94f5b-5fc33a70d14b866a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:37:54Z" - latency: 8.308057ms message: 'load-balancer-api-external: resolved host name af5597669a0ff4ee889c283f78c94f5b-5fc33a70d14b866a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T20:37:54Z" - latency: 6.743779ms message: 'load-balancer-api-external: tcp connection to af5597669a0ff4ee889c283f78c94f5b-5fc33a70d14b866a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:36:54Z" - latency: 8.26007ms message: 'load-balancer-api-external: resolved host name af5597669a0ff4ee889c283f78c94f5b-5fc33a70d14b866a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T20:36:54Z" - latency: 7.267165ms message: 'load-balancer-api-external: tcp connection to af5597669a0ff4ee889c283f78c94f5b-5fc33a70d14b866a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:35:54Z" - latency: 8.519054ms message: 'load-balancer-api-external: resolved host name af5597669a0ff4ee889c283f78c94f5b-5fc33a70d14b866a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T20:35:54Z" - latency: 3.907103ms message: 'load-balancer-api-external: tcp connection to af5597669a0ff4ee889c283f78c94f5b-5fc33a70d14b866a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:34:54Z" - latency: 7.371376ms message: 'load-balancer-api-external: resolved host name af5597669a0ff4ee889c283f78c94f5b-5fc33a70d14b866a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T20:34:54Z" - latency: 4.275889ms message: 'load-balancer-api-external: tcp connection to af5597669a0ff4ee889c283f78c94f5b-5fc33a70d14b866a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:33:54Z" - latency: 8.088955ms message: 'load-balancer-api-external: resolved host name af5597669a0ff4ee889c283f78c94f5b-5fc33a70d14b866a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T20:33:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T20:07:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-118-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-118.ec2.internal uid: d3b49909-26f0-41c4-921c-2f636a31def1 resourceVersion: "48227" uid: 55b7de00-7f12-4591-a256-a38eb42fbedb spec: sourcePod: network-check-source-56d84b9f44-smjxr targetEndpoint: af5597669a0ff4ee889c283f78c94f5b-5fc33a70d14b866a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-02T20:13:54Z" message: 'load-balancer-api-internal: tcp connection to af5597669a0ff4ee889c283f78c94f5b-5fc33a70d14b866a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.536108ms message: 'load-balancer-api-internal: tcp connection to af5597669a0ff4ee889c283f78c94f5b-5fc33a70d14b866a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:37:54Z" - latency: 8.190233ms message: 'load-balancer-api-internal: resolved host name af5597669a0ff4ee889c283f78c94f5b-5fc33a70d14b866a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T20:37:54Z" - latency: 4.928253ms message: 'load-balancer-api-internal: tcp connection to af5597669a0ff4ee889c283f78c94f5b-5fc33a70d14b866a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:36:54Z" - latency: 8.19714ms message: 'load-balancer-api-internal: resolved host name af5597669a0ff4ee889c283f78c94f5b-5fc33a70d14b866a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T20:36:54Z" - latency: 5.55692ms message: 'load-balancer-api-internal: tcp connection to af5597669a0ff4ee889c283f78c94f5b-5fc33a70d14b866a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:35:54Z" - latency: 8.439034ms message: 'load-balancer-api-internal: resolved host name af5597669a0ff4ee889c283f78c94f5b-5fc33a70d14b866a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T20:35:54Z" - latency: 4.467757ms message: 'load-balancer-api-internal: tcp connection to af5597669a0ff4ee889c283f78c94f5b-5fc33a70d14b866a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:34:54Z" - latency: 7.398597ms message: 'load-balancer-api-internal: resolved host name af5597669a0ff4ee889c283f78c94f5b-5fc33a70d14b866a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T20:34:54Z" - latency: 4.267666ms message: 'load-balancer-api-internal: tcp connection to af5597669a0ff4ee889c283f78c94f5b-5fc33a70d14b866a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:33:54Z" - latency: 8.023788ms message: 'load-balancer-api-internal: resolved host name af5597669a0ff4ee889c283f78c94f5b-5fc33a70d14b866a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T20:33:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T20:07:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-118-to-network-check-target-ip-10-0-132-46 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-118.ec2.internal uid: d3b49909-26f0-41c4-921c-2f636a31def1 resourceVersion: "46089" uid: 5bd3ceb4-ce6a-442d-a384-08518a78efd7 spec: sourcePod: network-check-source-56d84b9f44-smjxr targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-02T20:14:54Z" message: 'network-check-target-ip-10-0-132-46: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.300711ms message: 'network-check-target-ip-10-0-132-46: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:35:54Z" - latency: 2.204282ms message: 'network-check-target-ip-10-0-132-46: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:34:54Z" - latency: 2.50245ms message: 'network-check-target-ip-10-0-132-46: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:33:54Z" - latency: 2.399896ms message: 'network-check-target-ip-10-0-132-46: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:32:54Z" - latency: 2.546134ms message: 'network-check-target-ip-10-0-132-46: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:31:54Z" - latency: 2.256528ms message: 'network-check-target-ip-10-0-132-46: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:30:54Z" - latency: 2.524441ms message: 'network-check-target-ip-10-0-132-46: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:29:54Z" - latency: 2.741858ms message: 'network-check-target-ip-10-0-132-46: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:28:54Z" - latency: 2.307883ms message: 'network-check-target-ip-10-0-132-46: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:27:54Z" - latency: 2.432726ms message: 'network-check-target-ip-10-0-132-46: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:26:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T20:07:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-118-to-network-check-target-ip-10-0-134-118 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-118.ec2.internal uid: d3b49909-26f0-41c4-921c-2f636a31def1 resourceVersion: "46087" uid: eadd3aad-758b-4677-80a9-5ed870462dd1 spec: sourcePod: network-check-source-56d84b9f44-smjxr targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-02T20:14:54Z" message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 732.651µs message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:35:54Z" - latency: 1.163063ms message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:34:54Z" - latency: 1.175644ms message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:33:54Z" - latency: 730.015µs message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:32:54Z" - latency: 835.486µs message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:31:54Z" - latency: 888.486µs message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:30:54Z" - latency: 838.868µs message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:29:54Z" - latency: 725.706µs message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:28:54Z" - latency: 836.318µs message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:27:54Z" - latency: 1.006584ms message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:26:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T20:07:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-118-to-network-check-target-ip-10-0-137-123 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-118.ec2.internal uid: d3b49909-26f0-41c4-921c-2f636a31def1 resourceVersion: "46088" uid: 774e524d-81e3-4a4c-ab4e-aa5597c258f4 spec: sourcePod: network-check-source-56d84b9f44-smjxr targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-02T20:14:54Z" message: 'network-check-target-ip-10-0-137-123: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.035639ms message: 'network-check-target-ip-10-0-137-123: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:35:54Z" - latency: 2.386338ms message: 'network-check-target-ip-10-0-137-123: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:34:54Z" - latency: 2.133433ms message: 'network-check-target-ip-10-0-137-123: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:33:54Z" - latency: 2.315062ms message: 'network-check-target-ip-10-0-137-123: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:32:54Z" - latency: 2.11592ms message: 'network-check-target-ip-10-0-137-123: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:31:54Z" - latency: 2.240734ms message: 'network-check-target-ip-10-0-137-123: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:30:54Z" - latency: 2.201288ms message: 'network-check-target-ip-10-0-137-123: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:29:54Z" - latency: 1.990233ms message: 'network-check-target-ip-10-0-137-123: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:28:54Z" - latency: 2.163794ms message: 'network-check-target-ip-10-0-137-123: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:27:54Z" - latency: 2.188399ms message: 'network-check-target-ip-10-0-137-123: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:26:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T20:07:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-118-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-118.ec2.internal uid: d3b49909-26f0-41c4-921c-2f636a31def1 resourceVersion: "48225" uid: f1b5571f-f98f-4c67-a22a-5fd4582eb53b spec: sourcePod: network-check-source-56d84b9f44-smjxr targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-02T20:13:54Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 772.821µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:37:54Z" - latency: 1.755383ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T20:37:54Z" - latency: 961.856µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:36:54Z" - latency: 2.388694ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T20:36:54Z" - latency: 987.156µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:35:54Z" - latency: 1.717958ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T20:35:54Z" - latency: 852.163µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:34:54Z" - latency: 1.972515ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T20:34:54Z" - latency: 1.080678ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:33:54Z" - latency: 1.623194ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T20:33:54Z" kind: List metadata: resourceVersion: ""