apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:25:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-117-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-117.ec2.internal uid: 0c897caa-591e-4b36-a432-bd179cc11910 resourceVersion: "40471" uid: 15da0f0f-9cef-45d7-8303-b055124fb199 spec: sourcePod: network-check-source-7b678d77c7-hzrtb targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-16T18:32:23Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 878.062µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:21:23Z" - latency: 868.06µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:20:23Z" - latency: 793.961µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:19:23Z" - latency: 832.649µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:18:23Z" - latency: 745.879µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:17:23Z" - latency: 774.146µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:16:23Z" - latency: 918.874µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:15:23Z" - latency: 1.10081ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:14:23Z" - latency: 1.169986ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:13:23Z" - latency: 795.367µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:12:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:25:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-117-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-117.ec2.internal uid: 0c897caa-591e-4b36-a432-bd179cc11910 resourceVersion: "39430" uid: a247f6bc-a7b1-412b-8ae9-23d181fc3815 spec: sourcePod: network-check-source-7b678d77c7-hzrtb targetEndpoint: a828ab01043b04e79bf357d88fdd6f11-5f45fccf699dda7d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T18:31:23Z" message: 'load-balancer-api-external: tcp connection to a828ab01043b04e79bf357d88fdd6f11-5f45fccf699dda7d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.283687ms message: 'load-balancer-api-external: tcp connection to a828ab01043b04e79bf357d88fdd6f11-5f45fccf699dda7d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:19:23Z" - latency: 8.850388ms message: 'load-balancer-api-external: resolved host name a828ab01043b04e79bf357d88fdd6f11-5f45fccf699dda7d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:19:23Z" - latency: 4.955635ms message: 'load-balancer-api-external: tcp connection to a828ab01043b04e79bf357d88fdd6f11-5f45fccf699dda7d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:18:23Z" - latency: 8.586562ms message: 'load-balancer-api-external: resolved host name a828ab01043b04e79bf357d88fdd6f11-5f45fccf699dda7d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:18:23Z" - latency: 5.598545ms message: 'load-balancer-api-external: tcp connection to a828ab01043b04e79bf357d88fdd6f11-5f45fccf699dda7d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:17:23Z" - latency: 6.656568ms message: 'load-balancer-api-external: resolved host name a828ab01043b04e79bf357d88fdd6f11-5f45fccf699dda7d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:17:23Z" - latency: 4.720365ms message: 'load-balancer-api-external: tcp connection to a828ab01043b04e79bf357d88fdd6f11-5f45fccf699dda7d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:16:23Z" - latency: 6.72048ms message: 'load-balancer-api-external: resolved host name a828ab01043b04e79bf357d88fdd6f11-5f45fccf699dda7d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:16:23Z" - latency: 3.445436ms message: 'load-balancer-api-external: tcp connection to a828ab01043b04e79bf357d88fdd6f11-5f45fccf699dda7d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:15:23Z" - latency: 6.487239ms message: 'load-balancer-api-external: resolved host name a828ab01043b04e79bf357d88fdd6f11-5f45fccf699dda7d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:15:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:25:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-117-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-117.ec2.internal uid: 0c897caa-591e-4b36-a432-bd179cc11910 resourceVersion: "39431" uid: a3818d51-afd9-4079-ad73-b48dd86eb147 spec: sourcePod: network-check-source-7b678d77c7-hzrtb targetEndpoint: a828ab01043b04e79bf357d88fdd6f11-5f45fccf699dda7d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T18:31:23Z" message: 'load-balancer-api-internal: tcp connection to a828ab01043b04e79bf357d88fdd6f11-5f45fccf699dda7d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.305317ms message: 'load-balancer-api-internal: tcp connection to a828ab01043b04e79bf357d88fdd6f11-5f45fccf699dda7d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:19:23Z" - latency: 8.941541ms message: 'load-balancer-api-internal: resolved host name a828ab01043b04e79bf357d88fdd6f11-5f45fccf699dda7d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:19:23Z" - latency: 3.77963ms message: 'load-balancer-api-internal: tcp connection to a828ab01043b04e79bf357d88fdd6f11-5f45fccf699dda7d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:18:23Z" - latency: 8.613275ms message: 'load-balancer-api-internal: resolved host name a828ab01043b04e79bf357d88fdd6f11-5f45fccf699dda7d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:18:23Z" - latency: 5.555178ms message: 'load-balancer-api-internal: tcp connection to a828ab01043b04e79bf357d88fdd6f11-5f45fccf699dda7d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:17:23Z" - latency: 6.686118ms message: 'load-balancer-api-internal: resolved host name a828ab01043b04e79bf357d88fdd6f11-5f45fccf699dda7d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:17:23Z" - latency: 4.754369ms message: 'load-balancer-api-internal: tcp connection to a828ab01043b04e79bf357d88fdd6f11-5f45fccf699dda7d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:16:23Z" - latency: 6.78996ms message: 'load-balancer-api-internal: resolved host name a828ab01043b04e79bf357d88fdd6f11-5f45fccf699dda7d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:16:23Z" - latency: 3.392159ms message: 'load-balancer-api-internal: tcp connection to a828ab01043b04e79bf357d88fdd6f11-5f45fccf699dda7d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:15:23Z" - latency: 6.591273ms message: 'load-balancer-api-internal: resolved host name a828ab01043b04e79bf357d88fdd6f11-5f45fccf699dda7d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:15:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:25:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-117-to-network-check-target-ip-10-0-136-226 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-117.ec2.internal uid: 0c897caa-591e-4b36-a432-bd179cc11910 resourceVersion: "40467" uid: 7c8e81ba-7843-40e1-b375-d7b6267adef6 spec: sourcePod: network-check-source-7b678d77c7-hzrtb targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-16T18:32:23Z" message: 'network-check-target-ip-10-0-136-226: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.608398ms message: 'network-check-target-ip-10-0-136-226: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:21:23Z" - latency: 1.745326ms message: 'network-check-target-ip-10-0-136-226: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:20:23Z" - latency: 1.622512ms message: 'network-check-target-ip-10-0-136-226: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:19:23Z" - latency: 1.952604ms message: 'network-check-target-ip-10-0-136-226: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:18:23Z" - latency: 1.821961ms message: 'network-check-target-ip-10-0-136-226: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:17:23Z" - latency: 1.618211ms message: 'network-check-target-ip-10-0-136-226: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:16:23Z" - latency: 1.673638ms message: 'network-check-target-ip-10-0-136-226: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:15:23Z" - latency: 1.826379ms message: 'network-check-target-ip-10-0-136-226: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:14:23Z" - latency: 1.807676ms message: 'network-check-target-ip-10-0-136-226: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:13:23Z" - latency: 1.742809ms message: 'network-check-target-ip-10-0-136-226: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:12:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:25:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-117-to-network-check-target-ip-10-0-138-175 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-117.ec2.internal uid: 0c897caa-591e-4b36-a432-bd179cc11910 resourceVersion: "40468" uid: f79e3ece-3cfa-457c-9e6d-ae350c08d04a spec: sourcePod: network-check-source-7b678d77c7-hzrtb targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T18:32:23Z" message: 'network-check-target-ip-10-0-138-175: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.361385ms message: 'network-check-target-ip-10-0-138-175: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:21:23Z" - latency: 2.035276ms message: 'network-check-target-ip-10-0-138-175: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:20:23Z" - latency: 1.988917ms message: 'network-check-target-ip-10-0-138-175: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:19:23Z" - latency: 1.810071ms message: 'network-check-target-ip-10-0-138-175: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:18:23Z" - latency: 2.01614ms message: 'network-check-target-ip-10-0-138-175: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:17:23Z" - latency: 1.923466ms message: 'network-check-target-ip-10-0-138-175: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:16:23Z" - latency: 1.719902ms message: 'network-check-target-ip-10-0-138-175: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:15:23Z" - latency: 1.737666ms message: 'network-check-target-ip-10-0-138-175: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:14:23Z" - latency: 1.90062ms message: 'network-check-target-ip-10-0-138-175: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:13:23Z" - latency: 2.156154ms message: 'network-check-target-ip-10-0-138-175: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:12:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:25:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-117-to-network-check-target-ip-10-0-139-117 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-117.ec2.internal uid: 0c897caa-591e-4b36-a432-bd179cc11910 resourceVersion: "40466" uid: 03139292-3004-4072-ae7f-4df86246ba20 spec: sourcePod: network-check-source-7b678d77c7-hzrtb targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-16T18:32:23Z" message: 'network-check-target-ip-10-0-139-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.447272ms message: 'network-check-target-ip-10-0-139-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:21:23Z" - latency: 773.498µs message: 'network-check-target-ip-10-0-139-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:20:23Z" - latency: 1.302694ms message: 'network-check-target-ip-10-0-139-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:19:23Z" - latency: 862.732µs message: 'network-check-target-ip-10-0-139-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:18:23Z" - latency: 804.767µs message: 'network-check-target-ip-10-0-139-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:17:23Z" - latency: 893.737µs message: 'network-check-target-ip-10-0-139-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:16:23Z" - latency: 764.612µs message: 'network-check-target-ip-10-0-139-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:15:23Z" - latency: 791.593µs message: 'network-check-target-ip-10-0-139-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:14:23Z" - latency: 1.051066ms message: 'network-check-target-ip-10-0-139-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:13:23Z" - latency: 825.034µs message: 'network-check-target-ip-10-0-139-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:12:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:25:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-117-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-117.ec2.internal uid: 0c897caa-591e-4b36-a432-bd179cc11910 resourceVersion: "39429" uid: 8b1bb7f6-09e1-42fe-b209-72fbb57cb89c spec: sourcePod: network-check-source-7b678d77c7-hzrtb targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-16T18:31:23Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 776.626µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:19:23Z" - latency: 2.390442ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T19:19:23Z" - latency: 1.005354ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:18:23Z" - latency: 1.577742ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T19:18:23Z" - latency: 929.083µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:17:23Z" - latency: 1.700507ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T19:17:23Z" - latency: 802.079µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:16:23Z" - latency: 1.624379ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T19:16:23Z" - latency: 817.402µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:15:23Z" - latency: 1.708763ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T19:15:23Z" kind: List metadata: resourceVersion: ""