You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 5, 2024. It is now read-only.
I don't understand how this line could have produced the result you showed. Where in that command does it attach the SA external-dns to the pod? I think you missed the following command line param:
kubectl run ... --serviceaccount external-dns ...
The text was updated successfully, but these errors were encountered:
Hi @qingvincentyin sorry I missed this issue, thanks though!
You don't need that since that is the default service account in the namespace is external-dns so you get that by default.
Hope that helps, thanks 👍
the default service account in the namespace is external-dns
The default SA in every namespace is named default. As far as I know, there's no way to change the name default to another name such as external-dns as you stated. So, in order to associate a non-default SA to a pod, the pod must explicitly reference it; hence, --serviceaccount external-dns is necessary for kubectl run as I stated above.
Put it another way, where in your code (elsewhere) did you manage to switch the default assignment of SA (again, I'm not aware of a way to do it.)
I don't understand how this line could have produced the result you showed. Where in that command does it attach the SA
external-dns
to the pod? I think you missed the following command line param:The text was updated successfully, but these errors were encountered: