apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T17:28:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-33-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-33.ec2.internal uid: 47c13b4a-c0fa-4405-9098-ad2203ddbe1a resourceVersion: "32131" uid: ec08f55b-de10-46df-9d6b-e05c80f906dc spec: sourcePod: network-check-source-8894fc9bd-gbxth targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-17T17:35:19Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.111551ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:10:19Z" - latency: 1.08682ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:09:19Z" - latency: 1.039266ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:08:19Z" - latency: 860.835µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:07:19Z" - latency: 1.018303ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:06:19Z" - latency: 838.189µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:05:19Z" - latency: 1.544655ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:04:19Z" - latency: 1.204671ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:03:19Z" - latency: 1.225734ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:02:19Z" - latency: 1.505351ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:01:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T17:28:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-33-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-33.ec2.internal uid: 47c13b4a-c0fa-4405-9098-ad2203ddbe1a resourceVersion: "32132" uid: 96d0e986-881b-41a2-811d-ef9012f25c18 spec: sourcePod: network-check-source-8894fc9bd-gbxth targetEndpoint: a9dfb5aa8b82f4eabbf5a28ef7c0977d-5ca589ec8d662dce.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-17T17:34:19Z" message: 'load-balancer-api-external: tcp connection to a9dfb5aa8b82f4eabbf5a28ef7c0977d-5ca589ec8d662dce.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.672549ms message: 'load-balancer-api-external: tcp connection to a9dfb5aa8b82f4eabbf5a28ef7c0977d-5ca589ec8d662dce.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:10:19Z" - latency: 6.700216ms message: 'load-balancer-api-external: resolved host name a9dfb5aa8b82f4eabbf5a28ef7c0977d-5ca589ec8d662dce.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T18:10:19Z" - latency: 5.103835ms message: 'load-balancer-api-external: tcp connection to a9dfb5aa8b82f4eabbf5a28ef7c0977d-5ca589ec8d662dce.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:09:19Z" - latency: 7.923607ms message: 'load-balancer-api-external: resolved host name a9dfb5aa8b82f4eabbf5a28ef7c0977d-5ca589ec8d662dce.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T18:09:19Z" - latency: 5.253114ms message: 'load-balancer-api-external: tcp connection to a9dfb5aa8b82f4eabbf5a28ef7c0977d-5ca589ec8d662dce.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:08:19Z" - latency: 8.005751ms message: 'load-balancer-api-external: resolved host name a9dfb5aa8b82f4eabbf5a28ef7c0977d-5ca589ec8d662dce.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T18:08:19Z" - latency: 4.685273ms message: 'load-balancer-api-external: tcp connection to a9dfb5aa8b82f4eabbf5a28ef7c0977d-5ca589ec8d662dce.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:07:19Z" - latency: 5.981555ms message: 'load-balancer-api-external: resolved host name a9dfb5aa8b82f4eabbf5a28ef7c0977d-5ca589ec8d662dce.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T18:07:19Z" - latency: 5.023914ms message: 'load-balancer-api-external: tcp connection to a9dfb5aa8b82f4eabbf5a28ef7c0977d-5ca589ec8d662dce.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:06:19Z" - latency: 8.185442ms message: 'load-balancer-api-external: resolved host name a9dfb5aa8b82f4eabbf5a28ef7c0977d-5ca589ec8d662dce.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T18:06:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T17:28:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-33-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-33.ec2.internal uid: 47c13b4a-c0fa-4405-9098-ad2203ddbe1a resourceVersion: "32133" uid: c3f38e20-1170-4f7c-bf73-80caf05c1dcb spec: sourcePod: network-check-source-8894fc9bd-gbxth targetEndpoint: a9dfb5aa8b82f4eabbf5a28ef7c0977d-5ca589ec8d662dce.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-17T17:34:19Z" message: 'load-balancer-api-internal: tcp connection to a9dfb5aa8b82f4eabbf5a28ef7c0977d-5ca589ec8d662dce.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.687401ms message: 'load-balancer-api-internal: tcp connection to a9dfb5aa8b82f4eabbf5a28ef7c0977d-5ca589ec8d662dce.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:10:19Z" - latency: 6.6162ms message: 'load-balancer-api-internal: resolved host name a9dfb5aa8b82f4eabbf5a28ef7c0977d-5ca589ec8d662dce.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T18:10:19Z" - latency: 4.860534ms message: 'load-balancer-api-internal: tcp connection to a9dfb5aa8b82f4eabbf5a28ef7c0977d-5ca589ec8d662dce.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:09:19Z" - latency: 8.016242ms message: 'load-balancer-api-internal: resolved host name a9dfb5aa8b82f4eabbf5a28ef7c0977d-5ca589ec8d662dce.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T18:09:19Z" - latency: 5.286324ms message: 'load-balancer-api-internal: tcp connection to a9dfb5aa8b82f4eabbf5a28ef7c0977d-5ca589ec8d662dce.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:08:19Z" - latency: 7.965238ms message: 'load-balancer-api-internal: resolved host name a9dfb5aa8b82f4eabbf5a28ef7c0977d-5ca589ec8d662dce.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T18:08:19Z" - latency: 4.271122ms message: 'load-balancer-api-internal: tcp connection to a9dfb5aa8b82f4eabbf5a28ef7c0977d-5ca589ec8d662dce.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:07:19Z" - latency: 6.06433ms message: 'load-balancer-api-internal: resolved host name a9dfb5aa8b82f4eabbf5a28ef7c0977d-5ca589ec8d662dce.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T18:07:19Z" - latency: 5.002062ms message: 'load-balancer-api-internal: tcp connection to a9dfb5aa8b82f4eabbf5a28ef7c0977d-5ca589ec8d662dce.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:06:19Z" - latency: 8.233562ms message: 'load-balancer-api-internal: resolved host name a9dfb5aa8b82f4eabbf5a28ef7c0977d-5ca589ec8d662dce.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T18:06:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T17:28:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-33-to-network-check-target-ip-10-0-130-19 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-33.ec2.internal uid: 47c13b4a-c0fa-4405-9098-ad2203ddbe1a resourceVersion: "32128" uid: ae01b36a-62f8-4d45-8676-be5a31a1999a spec: sourcePod: network-check-source-8894fc9bd-gbxth targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-17T17:35:19Z" message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.219185ms message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:10:19Z" - latency: 2.265359ms message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:09:19Z" - latency: 1.969316ms message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:08:19Z" - latency: 1.904094ms message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:07:19Z" - latency: 1.992305ms message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:06:19Z" - latency: 2.211081ms message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:05:19Z" - latency: 2.289754ms message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:04:19Z" - latency: 2.075409ms message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:03:19Z" - latency: 2.070185ms message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:02:19Z" - latency: 2.044409ms message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:01:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T17:28:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-33-to-network-check-target-ip-10-0-136-202 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-33.ec2.internal uid: 47c13b4a-c0fa-4405-9098-ad2203ddbe1a resourceVersion: "32129" uid: d4244bc5-db28-4ee0-8a3d-e4034d48619d spec: sourcePod: network-check-source-8894fc9bd-gbxth targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-17T17:35:19Z" message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.730149ms message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:10:19Z" - latency: 1.753942ms message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:09:19Z" - latency: 1.672494ms message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:08:19Z" - latency: 1.559564ms message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:07:19Z" - latency: 1.755322ms message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:06:19Z" - latency: 1.985078ms message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:05:19Z" - latency: 1.928773ms message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:04:19Z" - latency: 2.211264ms message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:03:19Z" - latency: 1.735489ms message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:02:19Z" - latency: 1.697515ms message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:01:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T17:28:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-33-to-network-check-target-ip-10-0-140-33 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-33.ec2.internal uid: 47c13b4a-c0fa-4405-9098-ad2203ddbe1a resourceVersion: "32127" uid: e5f62158-6a2a-400b-8843-bd819a457749 spec: sourcePod: network-check-source-8894fc9bd-gbxth targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-17T17:35:19Z" message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 846.77µs message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:10:19Z" - latency: 1.202155ms message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:09:19Z" - latency: 865.814µs message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:08:19Z" - latency: 784.053µs message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:07:19Z" - latency: 1.378971ms message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:06:19Z" - latency: 1.116749ms message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:05:19Z" - latency: 1.362016ms message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:04:19Z" - latency: 1.311568ms message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:03:19Z" - latency: 1.062989ms message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:02:19Z" - latency: 1.727296ms message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:01:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T17:28:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-33-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-33.ec2.internal uid: 47c13b4a-c0fa-4405-9098-ad2203ddbe1a resourceVersion: "32130" uid: d01ba4cc-07c6-4a83-a97f-d226c8d0d44f spec: sourcePod: network-check-source-8894fc9bd-gbxth targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-17T17:34:19Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 735.763µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:10:19Z" - latency: 1.552539ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T18:10:19Z" - latency: 1.028199ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:09:19Z" - latency: 1.471311ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T18:09:19Z" - latency: 866.388µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:08:19Z" - latency: 2.016772ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T18:08:19Z" - latency: 808.428µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:07:19Z" - latency: 1.558411ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T18:07:19Z" - latency: 849.332µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:06:19Z" - latency: 1.685327ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T18:06:19Z" kind: List metadata: resourceVersion: ""