apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-19T12:13:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-225-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-225.ec2.internal uid: 3e02a3c7-3bb8-4093-bfec-a13313d47c09 resourceVersion: "43055" uid: df52f85c-a9a0-4d93-bdee-9d83662bbaec spec: sourcePod: network-check-source-8894fc9bd-8dx5p targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-19T12:20:42Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 857.037µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:41:42Z" - latency: 1.153693ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:40:42Z" - latency: 1.186837ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:39:42Z" - latency: 935.666µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:38:42Z" - latency: 1.460738ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:37:42Z" - latency: 1.004812ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:36:42Z" - latency: 1.246516ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:35:42Z" - latency: 1.175867ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:34:42Z" - latency: 1.198093ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:33:42Z" - latency: 1.127319ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:32:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-19T12:13:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-225-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-225.ec2.internal uid: 3e02a3c7-3bb8-4093-bfec-a13313d47c09 resourceVersion: "45408" uid: 50f10c25-7106-4b10-a2de-1463819ab619 spec: sourcePod: network-check-source-8894fc9bd-8dx5p targetEndpoint: af517b4f1c8bf45b6846347cfdc75ea2-18ab6751faed5dfa.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-19T12:19:42Z" message: 'load-balancer-api-external: tcp connection to af517b4f1c8bf45b6846347cfdc75ea2-18ab6751faed5dfa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.576496ms message: 'load-balancer-api-external: tcp connection to af517b4f1c8bf45b6846347cfdc75ea2-18ab6751faed5dfa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:43:42Z" - latency: 8.4496ms message: 'load-balancer-api-external: resolved host name af517b4f1c8bf45b6846347cfdc75ea2-18ab6751faed5dfa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-19T12:43:42Z" - latency: 5.273063ms message: 'load-balancer-api-external: tcp connection to af517b4f1c8bf45b6846347cfdc75ea2-18ab6751faed5dfa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:42:42Z" - latency: 8.397589ms message: 'load-balancer-api-external: resolved host name af517b4f1c8bf45b6846347cfdc75ea2-18ab6751faed5dfa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-19T12:42:42Z" - latency: 4.185072ms message: 'load-balancer-api-external: tcp connection to af517b4f1c8bf45b6846347cfdc75ea2-18ab6751faed5dfa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:41:42Z" - latency: 9.624694ms message: 'load-balancer-api-external: resolved host name af517b4f1c8bf45b6846347cfdc75ea2-18ab6751faed5dfa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-19T12:41:42Z" - latency: 4.794408ms message: 'load-balancer-api-external: tcp connection to af517b4f1c8bf45b6846347cfdc75ea2-18ab6751faed5dfa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:40:42Z" - latency: 8.54347ms message: 'load-balancer-api-external: resolved host name af517b4f1c8bf45b6846347cfdc75ea2-18ab6751faed5dfa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-19T12:40:42Z" - latency: 4.459607ms message: 'load-balancer-api-external: tcp connection to af517b4f1c8bf45b6846347cfdc75ea2-18ab6751faed5dfa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:39:42Z" - latency: 8.609298ms message: 'load-balancer-api-external: resolved host name af517b4f1c8bf45b6846347cfdc75ea2-18ab6751faed5dfa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-19T12:39:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-19T12:13:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-225-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-225.ec2.internal uid: 3e02a3c7-3bb8-4093-bfec-a13313d47c09 resourceVersion: "45409" uid: 2c2ccfda-b569-4ac7-8e5f-3fca6f2a3b79 spec: sourcePod: network-check-source-8894fc9bd-8dx5p targetEndpoint: af517b4f1c8bf45b6846347cfdc75ea2-18ab6751faed5dfa.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-19T12:19:42Z" message: 'load-balancer-api-internal: tcp connection to af517b4f1c8bf45b6846347cfdc75ea2-18ab6751faed5dfa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.551385ms message: 'load-balancer-api-internal: tcp connection to af517b4f1c8bf45b6846347cfdc75ea2-18ab6751faed5dfa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:43:42Z" - latency: 8.398327ms message: 'load-balancer-api-internal: resolved host name af517b4f1c8bf45b6846347cfdc75ea2-18ab6751faed5dfa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-19T12:43:42Z" - latency: 5.26951ms message: 'load-balancer-api-internal: tcp connection to af517b4f1c8bf45b6846347cfdc75ea2-18ab6751faed5dfa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:42:42Z" - latency: 8.562078ms message: 'load-balancer-api-internal: resolved host name af517b4f1c8bf45b6846347cfdc75ea2-18ab6751faed5dfa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-19T12:42:42Z" - latency: 3.478514ms message: 'load-balancer-api-internal: tcp connection to af517b4f1c8bf45b6846347cfdc75ea2-18ab6751faed5dfa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:41:42Z" - latency: 9.599827ms message: 'load-balancer-api-internal: resolved host name af517b4f1c8bf45b6846347cfdc75ea2-18ab6751faed5dfa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-19T12:41:42Z" - latency: 4.786536ms message: 'load-balancer-api-internal: tcp connection to af517b4f1c8bf45b6846347cfdc75ea2-18ab6751faed5dfa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:40:42Z" - latency: 8.615518ms message: 'load-balancer-api-internal: resolved host name af517b4f1c8bf45b6846347cfdc75ea2-18ab6751faed5dfa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-19T12:40:42Z" - latency: 3.889621ms message: 'load-balancer-api-internal: tcp connection to af517b4f1c8bf45b6846347cfdc75ea2-18ab6751faed5dfa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:39:42Z" - latency: 8.705726ms message: 'load-balancer-api-internal: resolved host name af517b4f1c8bf45b6846347cfdc75ea2-18ab6751faed5dfa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-19T12:39:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-19T12:13:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-225-to-network-check-target-ip-10-0-131-150 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-225.ec2.internal uid: 3e02a3c7-3bb8-4093-bfec-a13313d47c09 resourceVersion: "43053" uid: cb89acf0-2cc2-4e10-8727-4ea6936079a8 spec: sourcePod: network-check-source-8894fc9bd-8dx5p targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-19T12:20:42Z" message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.756135ms message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:41:42Z" - latency: 1.806798ms message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:40:42Z" - latency: 1.902491ms message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:39:42Z" - latency: 1.851167ms message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:38:42Z" - latency: 2.549721ms message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:37:42Z" - latency: 2.082496ms message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:36:42Z" - latency: 2.320097ms message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:35:42Z" - latency: 1.837964ms message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:34:42Z" - latency: 2.084876ms message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:33:42Z" - latency: 1.962912ms message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:32:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-19T12:13:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-225-to-network-check-target-ip-10-0-140-225 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-225.ec2.internal uid: 3e02a3c7-3bb8-4093-bfec-a13313d47c09 resourceVersion: "43052" uid: bcfe2f41-5788-4037-90da-8b232a8bb0f3 spec: sourcePod: network-check-source-8894fc9bd-8dx5p targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-19T12:20:42Z" message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 778.28µs message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:41:42Z" - latency: 817.227µs message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:40:42Z" - latency: 931.187µs message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:39:42Z" - latency: 744.97µs message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:38:42Z" - latency: 916.582µs message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:37:42Z" - latency: 871.513µs message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:36:42Z" - latency: 712.961µs message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:35:42Z" - latency: 896.045µs message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:34:42Z" - latency: 989.952µs message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:33:42Z" - latency: 825.313µs message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:32:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-19T12:13:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-225-to-network-check-target-ip-10-0-140-237 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-225.ec2.internal uid: 3e02a3c7-3bb8-4093-bfec-a13313d47c09 resourceVersion: "43054" uid: 94d5eb89-79fc-4b54-82d6-93933e00fb64 spec: sourcePod: network-check-source-8894fc9bd-8dx5p targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-19T12:20:42Z" message: 'network-check-target-ip-10-0-140-237: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.072014ms message: 'network-check-target-ip-10-0-140-237: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:41:42Z" - latency: 1.927376ms message: 'network-check-target-ip-10-0-140-237: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:40:42Z" - latency: 1.97003ms message: 'network-check-target-ip-10-0-140-237: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:39:42Z" - latency: 2.227986ms message: 'network-check-target-ip-10-0-140-237: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:38:42Z" - latency: 2.114408ms message: 'network-check-target-ip-10-0-140-237: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:37:42Z" - latency: 2.159522ms message: 'network-check-target-ip-10-0-140-237: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:36:42Z" - latency: 1.897383ms message: 'network-check-target-ip-10-0-140-237: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:35:42Z" - latency: 2.446089ms message: 'network-check-target-ip-10-0-140-237: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:34:42Z" - latency: 2.078224ms message: 'network-check-target-ip-10-0-140-237: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:33:42Z" - latency: 2.069157ms message: 'network-check-target-ip-10-0-140-237: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:32:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-19T12:13:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-225-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-225.ec2.internal uid: 3e02a3c7-3bb8-4093-bfec-a13313d47c09 resourceVersion: "45407" uid: 4ac291a0-b6d1-4519-9901-79e00acf06ef spec: sourcePod: network-check-source-8894fc9bd-8dx5p targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-19T12:19:42Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 885.836µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:43:42Z" - latency: 2.45677ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-19T12:43:42Z" - latency: 1.202067ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:42:42Z" - latency: 1.904891ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-19T12:42:42Z" - latency: 827.426µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:41:42Z" - latency: 2.389503ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-19T12:41:42Z" - latency: 1.09794ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:40:42Z" - latency: 2.078056ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-19T12:40:42Z" - latency: 786.495µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-19T12:39:42Z" - latency: 1.941543ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-19T12:39:42Z" kind: List metadata: resourceVersion: ""