Kubernetes Controller Fails to Create linkerd-test Namespace During Installation

[tanerjn]

Problem Description

I am attempting to install Linkerd for multi-cluster connectivity, but the initial installation process is failing. The linkerd-test namespace is not being created, which is preventing the Linkerd control plane from being deployed and initialized.

The linkerd check --pre command correctly identifies that the namespace does not exist but the Kubernetes controller itself appears unable to create it. All other control plane and worker nodes are healthy, and other pods are functioning correctly.

Steps to Reproduce
`linkerd check --pre --linkerd-namespace linkerd-test

Output:

kubernetes-api
--------------
√ can initialize the client
√ can query the Kubernetes API

kubernetes-version
------------------
√ is running the minimum Kubernetes API version

pre-kubernetes-setup
--------------------
√ control plane namespace does not already exist
√ can create non-namespaced resources
√ can create ServiceAccounts
√ can create Services
√ can create Deployments
√ can create CronJobs
√ can create ConfigMaps
√ can create Secrets
√ can read Secrets
√ can read extension-apiserver-authentication configmap
√ no clock skew detected

linkerd-version
---------------
√ can determine the latest version
√ cli is up-to-date

Output from linkerd check:

× 'linkerd-config' config map exists
    configmaps "linkerd-config" not found
    see https://linkerd.io/2/checks/#l5d-existence-linkerd-config for hints
`

No activity about linkerd on logs: kubectl get events -n kube-system

kubectl version:
Client Version: v1.34.0
Kustomize Version: v5.7.1
Server Version: v1.34.0

linkerd version:
Client version: edge-25.9.3
Server version: unavailable

Insalled CRD from: https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.2.1/standard-install.yaml

I have Cilium on one cluster and Calico on the other. Both clusters based on Ubuntu 24.04 CNIs are working fine. Appreciate any insight.