Kubernetes image_pull_secrets only uses secret from same namespace, is there other way so the secret doesn't need to be created to all namespaces?

7/16/2021

I'm coming from the following thread and bump up the question in the comment

https://stackoverflow.com/a/40997561/2641128

The only difference is that I actually WANT the secret to be in the default namespace as I don't want to create it for all namespaces. Is there a way to reference to a secret the default namespace while the ingress is created inside a namespace?

Any solution for this issue in 2021?

-- e-j5

kubernetes

1 Answer

7/17/2021

Nothing changed and secret is still a namespace defendant object...

Secret restrictions

Secret resources reside in a namespace. Secrets can only be referenced by Pods in that same namespace.

-- Vit

Source: StackOverflow

K
Q

Kubernetes image_pull_secrets only uses secret from same namespace, is there other way so the secret doesn't need to be created to all namespaces?

Similar Questions

1 Answer

KQ

Kubernetes image_pull_secrets only uses secret from same namespace, is there other way so the secret doesn&#39;t need to be created to all namespaces?

Similar Questions

1 Answer

K
Q

Kubernetes image_pull_secrets only uses secret from same namespace, is there other way so the secret doesn't need to be created to all namespaces?