-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Closed
Description
What is the issue?
Running kubectl get ns <namespace> -o yaml | linkerd inject - shows namespace "<namespace>" skipped on stderr. However, it does appear that the annotation gets applied and spit out as YAML as expected.
The linkerd docs note that you can apply the linkerd.io/inject: enabled annotation to a Namespace. (Yes, I realize this could be done using kubectl annotate, but the linkerd inject route seems more stable and explicit.)
Is linkerd inject meant to be used on Namespace YAML, or only directly on Deployment/StatefulSet/Pod resources?
How can it be reproduced?
kubectl get ns <namespace> -o yaml | linkerd inject -
Logs, error output, etc
$ kubectl get ns airflow -o yaml | linkerd inject -
...
namespace "airflow" skipped
output of linkerd check -o short
$ linkerd check -o short
Status check results are √
Environment
- Amazon EKS 1.24
Possible solution
No response
Additional context
No response
Would you like to work on fixing this bug?
no
Reactions are currently unavailable