apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T05:29:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-218-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-218.ec2.internal uid: 1aeae7cc-4282-48f1-bd0b-31ed8d9da769 resourceVersion: "39757" uid: 139d9bd7-dbbd-4f10-8827-508dd38e2c20 spec: sourcePod: network-check-source-56d84b9f44-r6cjl targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-02T05:36:20Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 855.595µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:57:20Z" - latency: 842.313µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:56:20Z" - latency: 1.064442ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:55:20Z" - latency: 1.195866ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:54:20Z" - latency: 1.026572ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:53:20Z" - latency: 1.378467ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:52:20Z" - latency: 750.072µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:51:20Z" - latency: 1.116256ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:50:20Z" - latency: 1.033957ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:49:20Z" - latency: 1.041274ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:48:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T05:29:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-218-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-218.ec2.internal uid: 1aeae7cc-4282-48f1-bd0b-31ed8d9da769 resourceVersion: "41860" uid: 256e4cc1-8318-4870-83fc-bbf8fe03e140 spec: sourcePod: network-check-source-56d84b9f44-r6cjl targetEndpoint: ad4eecad1c0a644b6abd062bf2ef73f7-a78ba50805dad300.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-02T05:35:20Z" message: 'load-balancer-api-external: tcp connection to ad4eecad1c0a644b6abd062bf2ef73f7-a78ba50805dad300.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.926175ms message: 'load-balancer-api-external: tcp connection to ad4eecad1c0a644b6abd062bf2ef73f7-a78ba50805dad300.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:59:20Z" - latency: 6.97761ms message: 'load-balancer-api-external: resolved host name ad4eecad1c0a644b6abd062bf2ef73f7-a78ba50805dad300.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T05:59:20Z" - latency: 3.475283ms message: 'load-balancer-api-external: tcp connection to ad4eecad1c0a644b6abd062bf2ef73f7-a78ba50805dad300.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:58:20Z" - latency: 10.807747ms message: 'load-balancer-api-external: resolved host name ad4eecad1c0a644b6abd062bf2ef73f7-a78ba50805dad300.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T05:58:20Z" - latency: 5.270377ms message: 'load-balancer-api-external: tcp connection to ad4eecad1c0a644b6abd062bf2ef73f7-a78ba50805dad300.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:57:20Z" - latency: 8.658156ms message: 'load-balancer-api-external: resolved host name ad4eecad1c0a644b6abd062bf2ef73f7-a78ba50805dad300.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T05:57:20Z" - latency: 3.460502ms message: 'load-balancer-api-external: tcp connection to ad4eecad1c0a644b6abd062bf2ef73f7-a78ba50805dad300.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:56:20Z" - latency: 8.059215ms message: 'load-balancer-api-external: resolved host name ad4eecad1c0a644b6abd062bf2ef73f7-a78ba50805dad300.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T05:56:20Z" - latency: 4.693672ms message: 'load-balancer-api-external: tcp connection to ad4eecad1c0a644b6abd062bf2ef73f7-a78ba50805dad300.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:55:20Z" - latency: 8.60459ms message: 'load-balancer-api-external: resolved host name ad4eecad1c0a644b6abd062bf2ef73f7-a78ba50805dad300.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T05:55:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T05:29:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-218-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-218.ec2.internal uid: 1aeae7cc-4282-48f1-bd0b-31ed8d9da769 resourceVersion: "41861" uid: 27667040-2d03-440a-a1e4-f4fac59be2c6 spec: sourcePod: network-check-source-56d84b9f44-r6cjl targetEndpoint: ad4eecad1c0a644b6abd062bf2ef73f7-a78ba50805dad300.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-02T05:35:20Z" message: 'load-balancer-api-internal: tcp connection to ad4eecad1c0a644b6abd062bf2ef73f7-a78ba50805dad300.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.913914ms message: 'load-balancer-api-internal: tcp connection to ad4eecad1c0a644b6abd062bf2ef73f7-a78ba50805dad300.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:59:20Z" - latency: 7.049535ms message: 'load-balancer-api-internal: resolved host name ad4eecad1c0a644b6abd062bf2ef73f7-a78ba50805dad300.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T05:59:20Z" - latency: 3.720122ms message: 'load-balancer-api-internal: tcp connection to ad4eecad1c0a644b6abd062bf2ef73f7-a78ba50805dad300.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:58:20Z" - latency: 10.891054ms message: 'load-balancer-api-internal: resolved host name ad4eecad1c0a644b6abd062bf2ef73f7-a78ba50805dad300.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T05:58:20Z" - latency: 5.267044ms message: 'load-balancer-api-internal: tcp connection to ad4eecad1c0a644b6abd062bf2ef73f7-a78ba50805dad300.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:57:20Z" - latency: 8.730238ms message: 'load-balancer-api-internal: resolved host name ad4eecad1c0a644b6abd062bf2ef73f7-a78ba50805dad300.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T05:57:20Z" - latency: 4.31769ms message: 'load-balancer-api-internal: tcp connection to ad4eecad1c0a644b6abd062bf2ef73f7-a78ba50805dad300.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:56:20Z" - latency: 8.025593ms message: 'load-balancer-api-internal: resolved host name ad4eecad1c0a644b6abd062bf2ef73f7-a78ba50805dad300.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T05:56:20Z" - latency: 4.697228ms message: 'load-balancer-api-internal: tcp connection to ad4eecad1c0a644b6abd062bf2ef73f7-a78ba50805dad300.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:55:20Z" - latency: 8.640485ms message: 'load-balancer-api-internal: resolved host name ad4eecad1c0a644b6abd062bf2ef73f7-a78ba50805dad300.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T05:55:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T05:29:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-218-to-network-check-target-ip-10-0-139-218 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-218.ec2.internal uid: 1aeae7cc-4282-48f1-bd0b-31ed8d9da769 resourceVersion: "39754" uid: 7aa8f1a9-df7d-4cfb-94e8-951a20c86db8 spec: sourcePod: network-check-source-56d84b9f44-r6cjl targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-02T05:36:20Z" message: 'network-check-target-ip-10-0-139-218: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 798.495µs message: 'network-check-target-ip-10-0-139-218: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:57:20Z" - latency: 870.369µs message: 'network-check-target-ip-10-0-139-218: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:56:20Z" - latency: 879.786µs message: 'network-check-target-ip-10-0-139-218: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:55:20Z" - latency: 819.823µs message: 'network-check-target-ip-10-0-139-218: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:54:20Z" - latency: 774.062µs message: 'network-check-target-ip-10-0-139-218: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:53:20Z" - latency: 1.309501ms message: 'network-check-target-ip-10-0-139-218: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:52:20Z" - latency: 769.379µs message: 'network-check-target-ip-10-0-139-218: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:51:20Z" - latency: 1.430684ms message: 'network-check-target-ip-10-0-139-218: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:50:20Z" - latency: 795.654µs message: 'network-check-target-ip-10-0-139-218: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:49:20Z" - latency: 892.757µs message: 'network-check-target-ip-10-0-139-218: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:48:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T05:29:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-218-to-network-check-target-ip-10-0-141-22 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-218.ec2.internal uid: 1aeae7cc-4282-48f1-bd0b-31ed8d9da769 resourceVersion: "39756" uid: 1b018651-80ac-4916-bad9-19bb3bec7e64 spec: sourcePod: network-check-source-56d84b9f44-r6cjl targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-02T05:36:20Z" message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.100913ms message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:57:20Z" - latency: 2.179278ms message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:56:20Z" - latency: 2.360319ms message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:55:20Z" - latency: 2.838585ms message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:54:20Z" - latency: 2.198049ms message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:53:20Z" - latency: 2.322645ms message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:52:20Z" - latency: 2.3476ms message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:51:20Z" - latency: 2.176575ms message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:50:20Z" - latency: 2.270343ms message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:49:20Z" - latency: 2.286053ms message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:48:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T05:29:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-218-to-network-check-target-ip-10-0-143-122 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-218.ec2.internal uid: 1aeae7cc-4282-48f1-bd0b-31ed8d9da769 resourceVersion: "39755" uid: 3ee28239-ce98-4a98-b06c-4314d0b12db1 spec: sourcePod: network-check-source-56d84b9f44-r6cjl targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-02T05:36:20Z" message: 'network-check-target-ip-10-0-143-122: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.886107ms message: 'network-check-target-ip-10-0-143-122: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:57:20Z" - latency: 2.300205ms message: 'network-check-target-ip-10-0-143-122: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:56:20Z" - latency: 2.3999ms message: 'network-check-target-ip-10-0-143-122: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:55:20Z" - latency: 2.962587ms message: 'network-check-target-ip-10-0-143-122: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:54:20Z" - latency: 2.336784ms message: 'network-check-target-ip-10-0-143-122: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:53:20Z" - latency: 2.063992ms message: 'network-check-target-ip-10-0-143-122: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:52:20Z" - latency: 2.044381ms message: 'network-check-target-ip-10-0-143-122: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:51:20Z" - latency: 2.224025ms message: 'network-check-target-ip-10-0-143-122: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:50:20Z" - latency: 2.251634ms message: 'network-check-target-ip-10-0-143-122: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:49:20Z" - latency: 2.228633ms message: 'network-check-target-ip-10-0-143-122: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:48:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T05:29:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-218-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-218.ec2.internal uid: 1aeae7cc-4282-48f1-bd0b-31ed8d9da769 resourceVersion: "41859" uid: 0df8581a-95b3-4821-8ae3-9de6edbefd11 spec: sourcePod: network-check-source-56d84b9f44-r6cjl targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-02T05:35:20Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 867.155µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:59:20Z" - latency: 1.587266ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T05:59:20Z" - latency: 1.090256ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:58:20Z" - latency: 1.68078ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T05:58:20Z" - latency: 1.183725ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:57:20Z" - latency: 1.650487ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T05:57:20Z" - latency: 834.863µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:56:20Z" - latency: 1.476882ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T05:56:20Z" - latency: 995.258µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:55:20Z" - latency: 1.662127ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T05:55:20Z" kind: List metadata: resourceVersion: ""