apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T20:01:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-61-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-61.ec2.internal uid: e9e3c331-5f49-49ec-b711-6c446d9a4694 resourceVersion: "39658" uid: dfb6895a-a1ea-47f9-a291-7114ccc9ae37 spec: sourcePod: network-check-source-8894fc9bd-5jcmz targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-22T20:08:58Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.081918ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:57:58Z" - latency: 790.292µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:56:58Z" - latency: 879.893µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:55:58Z" - latency: 876.853µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:54:58Z" - latency: 1.561136ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:53:58Z" - latency: 1.122652ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:52:58Z" - latency: 895.317µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:51:58Z" - latency: 942.898µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:50:58Z" - latency: 1.009541ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:49:58Z" - latency: 1.709774ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:48:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T20:01:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-61-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-61.ec2.internal uid: e9e3c331-5f49-49ec-b711-6c446d9a4694 resourceVersion: "38467" uid: 9dbfa9d8-8153-4607-a016-98c1d9863c67 spec: sourcePod: network-check-source-8894fc9bd-5jcmz targetEndpoint: a7c5286fbc4184a269bb86308d461e5c-7c592a77e6ae2319.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T20:07:58Z" message: 'load-balancer-api-external: tcp connection to a7c5286fbc4184a269bb86308d461e5c-7c592a77e6ae2319.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.319559ms message: 'load-balancer-api-external: tcp connection to a7c5286fbc4184a269bb86308d461e5c-7c592a77e6ae2319.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:55:58Z" - latency: 6.630395ms message: 'load-balancer-api-external: resolved host name a7c5286fbc4184a269bb86308d461e5c-7c592a77e6ae2319.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:55:58Z" - latency: 4.599621ms message: 'load-balancer-api-external: tcp connection to a7c5286fbc4184a269bb86308d461e5c-7c592a77e6ae2319.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:54:58Z" - latency: 6.643788ms message: 'load-balancer-api-external: resolved host name a7c5286fbc4184a269bb86308d461e5c-7c592a77e6ae2319.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:54:58Z" - latency: 4.077314ms message: 'load-balancer-api-external: tcp connection to a7c5286fbc4184a269bb86308d461e5c-7c592a77e6ae2319.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:53:58Z" - latency: 7.448147ms message: 'load-balancer-api-external: resolved host name a7c5286fbc4184a269bb86308d461e5c-7c592a77e6ae2319.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:53:58Z" - latency: 3.867441ms message: 'load-balancer-api-external: tcp connection to a7c5286fbc4184a269bb86308d461e5c-7c592a77e6ae2319.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:52:58Z" - latency: 6.897564ms message: 'load-balancer-api-external: resolved host name a7c5286fbc4184a269bb86308d461e5c-7c592a77e6ae2319.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:52:58Z" - latency: 4.088194ms message: 'load-balancer-api-external: tcp connection to a7c5286fbc4184a269bb86308d461e5c-7c592a77e6ae2319.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:51:58Z" - latency: 6.546686ms message: 'load-balancer-api-external: resolved host name a7c5286fbc4184a269bb86308d461e5c-7c592a77e6ae2319.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:51:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T20:01:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-61-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-61.ec2.internal uid: e9e3c331-5f49-49ec-b711-6c446d9a4694 resourceVersion: "38468" uid: 1850e513-0e74-4c63-8e3f-e85f45cb0256 spec: sourcePod: network-check-source-8894fc9bd-5jcmz targetEndpoint: a7c5286fbc4184a269bb86308d461e5c-7c592a77e6ae2319.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T20:07:58Z" message: 'load-balancer-api-internal: tcp connection to a7c5286fbc4184a269bb86308d461e5c-7c592a77e6ae2319.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.723515ms message: 'load-balancer-api-internal: tcp connection to a7c5286fbc4184a269bb86308d461e5c-7c592a77e6ae2319.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:55:58Z" - latency: 6.725029ms message: 'load-balancer-api-internal: resolved host name a7c5286fbc4184a269bb86308d461e5c-7c592a77e6ae2319.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:55:58Z" - latency: 4.601529ms message: 'load-balancer-api-internal: tcp connection to a7c5286fbc4184a269bb86308d461e5c-7c592a77e6ae2319.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:54:58Z" - latency: 6.713696ms message: 'load-balancer-api-internal: resolved host name a7c5286fbc4184a269bb86308d461e5c-7c592a77e6ae2319.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:54:58Z" - latency: 4.101833ms message: 'load-balancer-api-internal: tcp connection to a7c5286fbc4184a269bb86308d461e5c-7c592a77e6ae2319.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:53:58Z" - latency: 7.574867ms message: 'load-balancer-api-internal: resolved host name a7c5286fbc4184a269bb86308d461e5c-7c592a77e6ae2319.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:53:58Z" - latency: 3.88727ms message: 'load-balancer-api-internal: tcp connection to a7c5286fbc4184a269bb86308d461e5c-7c592a77e6ae2319.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:52:58Z" - latency: 6.955304ms message: 'load-balancer-api-internal: resolved host name a7c5286fbc4184a269bb86308d461e5c-7c592a77e6ae2319.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:52:58Z" - latency: 4.183897ms message: 'load-balancer-api-internal: tcp connection to a7c5286fbc4184a269bb86308d461e5c-7c592a77e6ae2319.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:51:58Z" - latency: 6.616782ms message: 'load-balancer-api-internal: resolved host name a7c5286fbc4184a269bb86308d461e5c-7c592a77e6ae2319.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:51:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T20:01:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-61-to-network-check-target-ip-10-0-128-61 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-61.ec2.internal uid: e9e3c331-5f49-49ec-b711-6c446d9a4694 resourceVersion: "39655" uid: b85c2ec7-9804-4d73-bca9-400f52eb45a4 spec: sourcePod: network-check-source-8894fc9bd-5jcmz targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-22T20:08:58Z" message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 911.766µs message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:57:58Z" - latency: 1.558416ms message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:56:58Z" - latency: 890.094µs message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:55:58Z" - latency: 1.535398ms message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:54:58Z" - latency: 1.331683ms message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:53:58Z" - latency: 887.01µs message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:52:58Z" - latency: 798.275µs message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:51:58Z" - latency: 1.265778ms message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:50:58Z" - latency: 749.623µs message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:49:58Z" - latency: 1.501017ms message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:48:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T20:01:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-61-to-network-check-target-ip-10-0-135-221 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-61.ec2.internal uid: e9e3c331-5f49-49ec-b711-6c446d9a4694 resourceVersion: "39657" uid: 86234c0e-e111-4969-8778-9007dbb6701b spec: sourcePod: network-check-source-8894fc9bd-5jcmz targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-22T20:08:58Z" message: 'network-check-target-ip-10-0-135-221: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.532052ms message: 'network-check-target-ip-10-0-135-221: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:57:58Z" - latency: 2.318072ms message: 'network-check-target-ip-10-0-135-221: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:56:58Z" - latency: 2.236688ms message: 'network-check-target-ip-10-0-135-221: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:55:58Z" - latency: 2.404285ms message: 'network-check-target-ip-10-0-135-221: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:54:58Z" - latency: 2.128681ms message: 'network-check-target-ip-10-0-135-221: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:53:58Z" - latency: 2.586427ms message: 'network-check-target-ip-10-0-135-221: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:52:58Z" - latency: 2.157001ms message: 'network-check-target-ip-10-0-135-221: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:51:58Z" - latency: 2.13557ms message: 'network-check-target-ip-10-0-135-221: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:50:58Z" - latency: 2.708113ms message: 'network-check-target-ip-10-0-135-221: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:49:58Z" - latency: 2.418932ms message: 'network-check-target-ip-10-0-135-221: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:48:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T20:01:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-61-to-network-check-target-ip-10-0-141-46 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-61.ec2.internal uid: e9e3c331-5f49-49ec-b711-6c446d9a4694 resourceVersion: "39656" uid: 32a8dc95-e8ed-457e-918d-09b9a943655c spec: sourcePod: network-check-source-8894fc9bd-5jcmz targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-22T20:08:58Z" message: 'network-check-target-ip-10-0-141-46: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.156394ms message: 'network-check-target-ip-10-0-141-46: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:57:58Z" - latency: 2.023024ms message: 'network-check-target-ip-10-0-141-46: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:56:58Z" - latency: 2.000102ms message: 'network-check-target-ip-10-0-141-46: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:55:58Z" - latency: 2.427501ms message: 'network-check-target-ip-10-0-141-46: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:54:58Z" - latency: 2.127682ms message: 'network-check-target-ip-10-0-141-46: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:53:58Z" - latency: 2.018542ms message: 'network-check-target-ip-10-0-141-46: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:52:58Z" - latency: 2.01306ms message: 'network-check-target-ip-10-0-141-46: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:51:58Z" - latency: 2.099668ms message: 'network-check-target-ip-10-0-141-46: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:50:58Z" - latency: 2.063956ms message: 'network-check-target-ip-10-0-141-46: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:49:58Z" - latency: 2.234712ms message: 'network-check-target-ip-10-0-141-46: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:48:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T20:01:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-61-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-61.ec2.internal uid: e9e3c331-5f49-49ec-b711-6c446d9a4694 resourceVersion: "38466" uid: b44959a2-35bd-4b40-8ce4-bf5c0e0ea0ec spec: sourcePod: network-check-source-8894fc9bd-5jcmz targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-22T20:07:58Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 759.186µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:55:58Z" - latency: 1.542746ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T20:55:58Z" - latency: 770.207µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:54:58Z" - latency: 1.949443ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T20:54:58Z" - latency: 871.333µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:53:58Z" - latency: 2.52921ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T20:53:58Z" - latency: 871.559µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:52:58Z" - latency: 1.846212ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T20:52:58Z" - latency: 1.364231ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:51:58Z" - latency: 1.649735ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T20:51:58Z" kind: List metadata: resourceVersion: ""