apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T12:12:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-32-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-32.ec2.internal uid: 3813e4ae-2de8-4c15-a0dc-cc5034d0c2f2 resourceVersion: "45707" uid: f53d822f-f586-4a90-814b-750763dd7abb spec: sourcePod: network-check-source-dbd9cf844-tghq8 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-10T12:19:12Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.110251ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:40:12Z" - latency: 1.384608ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:39:12Z" - latency: 1.534614ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:38:12Z" - latency: 1.173677ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:37:12Z" - latency: 1.373623ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:36:12Z" - latency: 889.05µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:35:12Z" - latency: 962.114µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:34:12Z" - latency: 1.226747ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:33:12Z" - latency: 1.13233ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:32:12Z" - latency: 1.42245ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:31:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T12:12:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-32-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-32.ec2.internal uid: 3813e4ae-2de8-4c15-a0dc-cc5034d0c2f2 resourceVersion: "47678" uid: 88002a48-d8ef-4b4e-a07b-fc350d1978cd spec: sourcePod: network-check-source-dbd9cf844-tghq8 targetEndpoint: a608866f236454c5f922543b1b4850e8-91c06fa96c79e29e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-10T12:18:12Z" message: 'load-balancer-api-external: tcp connection to a608866f236454c5f922543b1b4850e8-91c06fa96c79e29e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.696534ms message: 'load-balancer-api-external: tcp connection to a608866f236454c5f922543b1b4850e8-91c06fa96c79e29e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:42:12Z" - latency: 6.958839ms message: 'load-balancer-api-external: resolved host name a608866f236454c5f922543b1b4850e8-91c06fa96c79e29e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T12:42:12Z" - latency: 4.667393ms message: 'load-balancer-api-external: tcp connection to a608866f236454c5f922543b1b4850e8-91c06fa96c79e29e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:41:12Z" - latency: 8.76059ms message: 'load-balancer-api-external: resolved host name a608866f236454c5f922543b1b4850e8-91c06fa96c79e29e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T12:41:12Z" - latency: 3.989471ms message: 'load-balancer-api-external: tcp connection to a608866f236454c5f922543b1b4850e8-91c06fa96c79e29e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:40:12Z" - latency: 7.598385ms message: 'load-balancer-api-external: resolved host name a608866f236454c5f922543b1b4850e8-91c06fa96c79e29e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T12:40:12Z" - latency: 4.744468ms message: 'load-balancer-api-external: tcp connection to a608866f236454c5f922543b1b4850e8-91c06fa96c79e29e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:39:12Z" - latency: 7.261108ms message: 'load-balancer-api-external: resolved host name a608866f236454c5f922543b1b4850e8-91c06fa96c79e29e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T12:39:12Z" - latency: 5.398672ms message: 'load-balancer-api-external: tcp connection to a608866f236454c5f922543b1b4850e8-91c06fa96c79e29e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:38:12Z" - latency: 6.185131ms message: 'load-balancer-api-external: resolved host name a608866f236454c5f922543b1b4850e8-91c06fa96c79e29e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T12:38:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T12:12:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-32-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-32.ec2.internal uid: 3813e4ae-2de8-4c15-a0dc-cc5034d0c2f2 resourceVersion: "47677" uid: 9963efb2-db1e-467e-b6c8-d1abe7f88451 spec: sourcePod: network-check-source-dbd9cf844-tghq8 targetEndpoint: a608866f236454c5f922543b1b4850e8-91c06fa96c79e29e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-10T12:18:12Z" message: 'load-balancer-api-internal: tcp connection to a608866f236454c5f922543b1b4850e8-91c06fa96c79e29e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.67535ms message: 'load-balancer-api-internal: tcp connection to a608866f236454c5f922543b1b4850e8-91c06fa96c79e29e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:42:12Z" - latency: 6.906205ms message: 'load-balancer-api-internal: resolved host name a608866f236454c5f922543b1b4850e8-91c06fa96c79e29e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T12:42:12Z" - latency: 4.659105ms message: 'load-balancer-api-internal: tcp connection to a608866f236454c5f922543b1b4850e8-91c06fa96c79e29e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:41:12Z" - latency: 8.72658ms message: 'load-balancer-api-internal: resolved host name a608866f236454c5f922543b1b4850e8-91c06fa96c79e29e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T12:41:12Z" - latency: 3.172841ms message: 'load-balancer-api-internal: tcp connection to a608866f236454c5f922543b1b4850e8-91c06fa96c79e29e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:40:12Z" - latency: 7.522662ms message: 'load-balancer-api-internal: resolved host name a608866f236454c5f922543b1b4850e8-91c06fa96c79e29e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T12:40:12Z" - latency: 4.768375ms message: 'load-balancer-api-internal: tcp connection to a608866f236454c5f922543b1b4850e8-91c06fa96c79e29e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:39:12Z" - latency: 7.198948ms message: 'load-balancer-api-internal: resolved host name a608866f236454c5f922543b1b4850e8-91c06fa96c79e29e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T12:39:12Z" - latency: 5.185005ms message: 'load-balancer-api-internal: tcp connection to a608866f236454c5f922543b1b4850e8-91c06fa96c79e29e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:38:12Z" - latency: 6.248996ms message: 'load-balancer-api-internal: resolved host name a608866f236454c5f922543b1b4850e8-91c06fa96c79e29e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T12:38:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T12:12:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-32-to-network-check-target-ip-10-0-130-187 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-32.ec2.internal uid: 3813e4ae-2de8-4c15-a0dc-cc5034d0c2f2 resourceVersion: "45705" uid: d802814b-48e7-49e9-98ed-9d06b050f374 spec: sourcePod: network-check-source-dbd9cf844-tghq8 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-10T12:19:12Z" message: 'network-check-target-ip-10-0-130-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.190066ms message: 'network-check-target-ip-10-0-130-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:40:12Z" - latency: 1.926768ms message: 'network-check-target-ip-10-0-130-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:39:12Z" - latency: 1.9511ms message: 'network-check-target-ip-10-0-130-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:38:12Z" - latency: 1.956392ms message: 'network-check-target-ip-10-0-130-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:37:12Z" - latency: 1.834964ms message: 'network-check-target-ip-10-0-130-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:36:12Z" - latency: 1.963968ms message: 'network-check-target-ip-10-0-130-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:35:12Z" - latency: 1.969576ms message: 'network-check-target-ip-10-0-130-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:34:12Z" - latency: 2.337907ms message: 'network-check-target-ip-10-0-130-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:33:12Z" - latency: 2.028854ms message: 'network-check-target-ip-10-0-130-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:32:12Z" - latency: 2.364136ms message: 'network-check-target-ip-10-0-130-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:31:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T12:12:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-32-to-network-check-target-ip-10-0-137-93 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-32.ec2.internal uid: 3813e4ae-2de8-4c15-a0dc-cc5034d0c2f2 resourceVersion: "45706" uid: 88975963-cd46-48dd-8532-60e84c82d311 spec: sourcePod: network-check-source-dbd9cf844-tghq8 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-10T12:19:12Z" message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.708581ms message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:40:12Z" - latency: 2.127921ms message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:39:12Z" - latency: 2.359062ms message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:38:12Z" - latency: 2.504813ms message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:37:12Z" - latency: 2.266727ms message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:36:12Z" - latency: 2.396923ms message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:35:12Z" - latency: 2.314296ms message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:34:12Z" - latency: 2.397769ms message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:33:12Z" - latency: 2.422988ms message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:32:12Z" - latency: 2.085937ms message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:31:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T12:12:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-32-to-network-check-target-ip-10-0-143-32 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-32.ec2.internal uid: 3813e4ae-2de8-4c15-a0dc-cc5034d0c2f2 resourceVersion: "45704" uid: 44e56883-1614-49de-bca7-54e44384f0f4 spec: sourcePod: network-check-source-dbd9cf844-tghq8 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-10T12:19:12Z" message: 'network-check-target-ip-10-0-143-32: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.443301ms message: 'network-check-target-ip-10-0-143-32: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:40:12Z" - latency: 1.155051ms message: 'network-check-target-ip-10-0-143-32: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:39:12Z" - latency: 1.066312ms message: 'network-check-target-ip-10-0-143-32: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:38:12Z" - latency: 760.035µs message: 'network-check-target-ip-10-0-143-32: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:37:12Z" - latency: 896.024µs message: 'network-check-target-ip-10-0-143-32: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:36:12Z" - latency: 1.007662ms message: 'network-check-target-ip-10-0-143-32: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:35:12Z" - latency: 859.238µs message: 'network-check-target-ip-10-0-143-32: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:34:12Z" - latency: 1.361751ms message: 'network-check-target-ip-10-0-143-32: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:33:12Z" - latency: 1.386582ms message: 'network-check-target-ip-10-0-143-32: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:32:12Z" - latency: 954.562µs message: 'network-check-target-ip-10-0-143-32: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:31:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T12:12:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-32-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-32.ec2.internal uid: 3813e4ae-2de8-4c15-a0dc-cc5034d0c2f2 resourceVersion: "47676" uid: 64f8eb01-476c-4f17-9c20-724d5ab6a418 spec: sourcePod: network-check-source-dbd9cf844-tghq8 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-10T12:18:12Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.054336ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:42:12Z" - latency: 1.877436ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T12:42:12Z" - latency: 947.773µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:41:12Z" - latency: 2.5826ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T12:41:12Z" - latency: 1.034242ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:40:12Z" - latency: 2.313823ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T12:40:12Z" - latency: 877.08µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:39:12Z" - latency: 2.315958ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T12:39:12Z" - latency: 1.031724ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:38:12Z" - latency: 1.955239ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T12:38:12Z" kind: List metadata: resourceVersion: ""