Description
What is the issue?
I'm currently deploying linkerd2-cni helm chart through ArgoCD on AWS EKS 1.32 (self-managed-node) as follow:
kind: Application
metadata:
name: linkerd-cni
namespace: argocd
annotations:
argocd.argoproj.io/sync-wave: "-1"
spec:
project: default
destination:
namespace: linkerd-cni
server: {{ .Values.destination.cluster }}
source:
chart: linkerd2-cni
repoURL: https://helm.linkerd.io/edge
targetRevision: 2025.1.2
helm:
values: |
# https://linkerd.io/2-edge/features/ipv6/
# Enable IPv6 Support
disableIPv6: false
syncPolicy:
automated:
prune: true # Specifies if resources should be pruned during auto-syncing ( false by default ).
selfHeal: true # Specifies if partial app sync should be executed when resources are changed only in target Kubernetes cluster and no git change detected ( false by default ).
syncOptions: # Sync options which modifies sync behavior
- Validate=false # disables resource validation (equivalent to 'kubectl apply --validate=true')
This works fine for the first time deployment. However, as soon as I delete this application or uninstall this helm chart then redeploy it again against the same EKS Cluster, it throws the following error message:
Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "4f6f0517034f255f3b4831091540a8f2cdcfae02944353350c9eee14828cbbef": plugin type="linkerd-cni" name="linkerd-cni" failed (add): Unauthorized
How can it be reproduced?
Deploy the linkerd2-cni helm chart for first time then delete this helm chart after that re-install it again and it will throw the error message below.
Logs, error output, etc
Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "4f6f0517034f255f3b4831091540a8f2cdcfae02944353350c9eee14828cbbef": plugin type="linkerd-cni" name="linkerd-cni" failed (add): Unauthorized
output of linkerd check -o short
-----------------
× 'linkerd-config' config map exists
configmaps "linkerd-config" not found
see https://linkerd.io/2.14/checks/#l5d-existence-linkerd-config for hints
Environment
- Kubernetes: 1.32
- Cluster Environment: EKS
- Host OS: AL2
- Linkerd Version: edge-25-1-2 same as the latest version 25-3-1
Possible solution
No response
Additional context
No response
Would you like to work on fixing this bug?
None