Should You Keep Your Private Container Registry Name a Secret?

0
3
Asked By CuriousCat42 On

Is the name of a private container registry, such as an Azure Container Registry used for Kubernetes deployments, considered confidential? When using Helm to set the `image` attribute for Pods, should the registry name be included in the values files stored in Git, or is it better to inject this information during CI/CD processes?

5 Answers

Answered By DevDiva On

In a company setting, I'm not sure why you'd want to hide the registry name. Could you elaborate on your setup? It seems a bit overkill to keep it under wraps.

Answered By SecuritySteve On

Nope, not a secret! Just like I wouldn’t hide an internal DNS name, you don’t want to broadcast it to the world, but it won't compromise anything if it gets out.

Answered By TechieTommy On

I don't see the registry name as a secret. It's more like an identifier, so losing it or sharing it shouldn’t impact things negatively. It’s similar to how people can find out your name without risking your safety at home.

Answered By CloudGuru88 On

I consider it just an identifier. The real sensitive info would be your access keys. Hiding the registry name adds unnecessary complexity without much security benefit.

Answered By QueryKween On

Using it as a secret can have its place, especially for disaster recovery reasons. However, you should weigh the trade-offs carefully.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.