apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T14:17:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-39-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-39.ec2.internal uid: 33d202eb-0594-4f84-86d3-09d97381e1f8 resourceVersion: "50336" uid: 8170b644-e169-4b1c-b6f2-927a3bf482bf spec: sourcePod: network-check-source-dbd9cf844-p8q67 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-05T14:24:48Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.175687ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:59:48Z" - latency: 1.1282ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:58:48Z" - latency: 1.392878ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:57:48Z" - latency: 884.559µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:56:48Z" - latency: 1.26081ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:55:48Z" - latency: 1.199554ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:54:48Z" - latency: 974.891µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:53:48Z" - latency: 952.285µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:52:48Z" - latency: 1.174551ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:51:48Z" - latency: 1.02791ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:50:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T14:17:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-39-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-39.ec2.internal uid: 33d202eb-0594-4f84-86d3-09d97381e1f8 resourceVersion: "50338" uid: 5eadd65f-7a18-4cca-9b90-8b26c2be9113 spec: sourcePod: network-check-source-dbd9cf844-p8q67 targetEndpoint: afb17678d8ee54aeaa6ca7daf76a9d93-6459ae7e75202f67.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-05T14:23:48Z" message: 'load-balancer-api-external: tcp connection to afb17678d8ee54aeaa6ca7daf76a9d93-6459ae7e75202f67.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.211189ms message: 'load-balancer-api-external: tcp connection to afb17678d8ee54aeaa6ca7daf76a9d93-6459ae7e75202f67.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:59:48Z" - latency: 8.716898ms message: 'load-balancer-api-external: resolved host name afb17678d8ee54aeaa6ca7daf76a9d93-6459ae7e75202f67.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T14:59:48Z" - latency: 4.59861ms message: 'load-balancer-api-external: tcp connection to afb17678d8ee54aeaa6ca7daf76a9d93-6459ae7e75202f67.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:58:48Z" - latency: 10.261565ms message: 'load-balancer-api-external: resolved host name afb17678d8ee54aeaa6ca7daf76a9d93-6459ae7e75202f67.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T14:58:48Z" - latency: 4.551682ms message: 'load-balancer-api-external: tcp connection to afb17678d8ee54aeaa6ca7daf76a9d93-6459ae7e75202f67.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:57:48Z" - latency: 8.608167ms message: 'load-balancer-api-external: resolved host name afb17678d8ee54aeaa6ca7daf76a9d93-6459ae7e75202f67.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T14:57:48Z" - latency: 5.605217ms message: 'load-balancer-api-external: tcp connection to afb17678d8ee54aeaa6ca7daf76a9d93-6459ae7e75202f67.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:56:48Z" - latency: 8.67505ms message: 'load-balancer-api-external: resolved host name afb17678d8ee54aeaa6ca7daf76a9d93-6459ae7e75202f67.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T14:56:48Z" - latency: 3.977888ms message: 'load-balancer-api-external: tcp connection to afb17678d8ee54aeaa6ca7daf76a9d93-6459ae7e75202f67.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:55:48Z" - latency: 7.050662ms message: 'load-balancer-api-external: resolved host name afb17678d8ee54aeaa6ca7daf76a9d93-6459ae7e75202f67.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T14:55:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T14:17:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-39-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-39.ec2.internal uid: 33d202eb-0594-4f84-86d3-09d97381e1f8 resourceVersion: "50337" uid: 69811c1f-b7d1-4116-b45a-5d04a8aa8806 spec: sourcePod: network-check-source-dbd9cf844-p8q67 targetEndpoint: afb17678d8ee54aeaa6ca7daf76a9d93-6459ae7e75202f67.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-05T14:23:48Z" message: 'load-balancer-api-internal: tcp connection to afb17678d8ee54aeaa6ca7daf76a9d93-6459ae7e75202f67.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.209537ms message: 'load-balancer-api-internal: tcp connection to afb17678d8ee54aeaa6ca7daf76a9d93-6459ae7e75202f67.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:59:48Z" - latency: 8.662948ms message: 'load-balancer-api-internal: resolved host name afb17678d8ee54aeaa6ca7daf76a9d93-6459ae7e75202f67.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T14:59:48Z" - latency: 4.568456ms message: 'load-balancer-api-internal: tcp connection to afb17678d8ee54aeaa6ca7daf76a9d93-6459ae7e75202f67.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:58:48Z" - latency: 10.278658ms message: 'load-balancer-api-internal: resolved host name afb17678d8ee54aeaa6ca7daf76a9d93-6459ae7e75202f67.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T14:58:48Z" - latency: 4.602758ms message: 'load-balancer-api-internal: tcp connection to afb17678d8ee54aeaa6ca7daf76a9d93-6459ae7e75202f67.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:57:48Z" - latency: 8.572409ms message: 'load-balancer-api-internal: resolved host name afb17678d8ee54aeaa6ca7daf76a9d93-6459ae7e75202f67.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T14:57:48Z" - latency: 5.648753ms message: 'load-balancer-api-internal: tcp connection to afb17678d8ee54aeaa6ca7daf76a9d93-6459ae7e75202f67.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:56:48Z" - latency: 8.74979ms message: 'load-balancer-api-internal: resolved host name afb17678d8ee54aeaa6ca7daf76a9d93-6459ae7e75202f67.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T14:56:48Z" - latency: 4.02375ms message: 'load-balancer-api-internal: tcp connection to afb17678d8ee54aeaa6ca7daf76a9d93-6459ae7e75202f67.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:55:48Z" - latency: 6.918544ms message: 'load-balancer-api-internal: resolved host name afb17678d8ee54aeaa6ca7daf76a9d93-6459ae7e75202f67.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T14:55:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T14:17:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-39-to-network-check-target-ip-10-0-132-39 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-39.ec2.internal uid: 33d202eb-0594-4f84-86d3-09d97381e1f8 resourceVersion: "50334" uid: 9778c62a-204f-4fbc-ad03-53898cacb8c1 spec: sourcePod: network-check-source-dbd9cf844-p8q67 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-05T14:24:48Z" message: 'network-check-target-ip-10-0-132-39: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.439567ms message: 'network-check-target-ip-10-0-132-39: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:59:48Z" - latency: 2.284894ms message: 'network-check-target-ip-10-0-132-39: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:58:48Z" - latency: 2.314754ms message: 'network-check-target-ip-10-0-132-39: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:57:48Z" - latency: 2.008193ms message: 'network-check-target-ip-10-0-132-39: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:56:48Z" - latency: 2.313072ms message: 'network-check-target-ip-10-0-132-39: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:55:48Z" - latency: 2.327211ms message: 'network-check-target-ip-10-0-132-39: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:54:48Z" - latency: 2.531429ms message: 'network-check-target-ip-10-0-132-39: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:53:48Z" - latency: 2.158426ms message: 'network-check-target-ip-10-0-132-39: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:52:48Z" - latency: 2.275246ms message: 'network-check-target-ip-10-0-132-39: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:51:48Z" - latency: 2.643451ms message: 'network-check-target-ip-10-0-132-39: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:50:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T14:17:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-39-to-network-check-target-ip-10-0-134-47 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-39.ec2.internal uid: 33d202eb-0594-4f84-86d3-09d97381e1f8 resourceVersion: "50333" uid: 8f9b1fec-e562-454d-9d35-13b2b1e1f741 spec: sourcePod: network-check-source-dbd9cf844-p8q67 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-05T14:24:48Z" message: 'network-check-target-ip-10-0-134-47: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.161189ms message: 'network-check-target-ip-10-0-134-47: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:59:48Z" - latency: 2.797861ms message: 'network-check-target-ip-10-0-134-47: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:58:48Z" - latency: 2.362842ms message: 'network-check-target-ip-10-0-134-47: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:57:48Z" - latency: 2.045951ms message: 'network-check-target-ip-10-0-134-47: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:56:48Z" - latency: 2.431009ms message: 'network-check-target-ip-10-0-134-47: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:55:48Z" - latency: 2.580569ms message: 'network-check-target-ip-10-0-134-47: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:54:48Z" - latency: 2.232167ms message: 'network-check-target-ip-10-0-134-47: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:53:48Z" - latency: 2.447121ms message: 'network-check-target-ip-10-0-134-47: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:52:48Z" - latency: 2.498448ms message: 'network-check-target-ip-10-0-134-47: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:51:48Z" - latency: 2.615872ms message: 'network-check-target-ip-10-0-134-47: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:50:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T14:17:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-39-to-network-check-target-ip-10-0-141-39 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-39.ec2.internal uid: 33d202eb-0594-4f84-86d3-09d97381e1f8 resourceVersion: "50332" uid: fba7db54-bc84-45f2-8484-83f5c735bda8 spec: sourcePod: network-check-source-dbd9cf844-p8q67 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-05T14:24:48Z" message: 'network-check-target-ip-10-0-141-39: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 929.493µs message: 'network-check-target-ip-10-0-141-39: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:59:48Z" - latency: 964.431µs message: 'network-check-target-ip-10-0-141-39: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:58:48Z" - latency: 930.285µs message: 'network-check-target-ip-10-0-141-39: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:57:48Z" - latency: 842.64µs message: 'network-check-target-ip-10-0-141-39: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:56:48Z" - latency: 879.213µs message: 'network-check-target-ip-10-0-141-39: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:55:48Z" - latency: 1.182878ms message: 'network-check-target-ip-10-0-141-39: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:54:48Z" - latency: 918.85µs message: 'network-check-target-ip-10-0-141-39: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:53:48Z" - latency: 1.835174ms message: 'network-check-target-ip-10-0-141-39: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:52:48Z" - latency: 1.012484ms message: 'network-check-target-ip-10-0-141-39: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:51:48Z" - latency: 1.662514ms message: 'network-check-target-ip-10-0-141-39: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:50:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T14:17:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-39-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-39.ec2.internal uid: 33d202eb-0594-4f84-86d3-09d97381e1f8 resourceVersion: "50335" uid: bcbd2cb1-bb34-43fb-ada7-5ea3a62f3fc0 spec: sourcePod: network-check-source-dbd9cf844-p8q67 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-05T14:23:48Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.006884ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:59:48Z" - latency: 1.729611ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T14:59:48Z" - latency: 854.823µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:58:48Z" - latency: 2.048028ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T14:58:48Z" - latency: 1.03626ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:57:48Z" - latency: 1.758687ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T14:57:48Z" - latency: 1.005432ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:56:48Z" - latency: 2.105717ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T14:56:48Z" - latency: 1.253929ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:55:48Z" - latency: 1.664079ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T14:55:48Z" kind: List metadata: resourceVersion: ""