Jump to content

Featured Replies

Posted

Let’s Begin With What You Might Know

In traditional apps — whether Node.js, Python, Java, or others — you’ve probably done this before:

DB_USERNAME=admin  
DB_PASSWORD=1234  
APP_ENV=production
  • .env files

  • Docker run commands

  • Cloud config panels

And sometimes… you (accidentally or lazily) hardcode passwords into the code itself. 😬

But in Kubernetes, there’s a better and safer way to do this.

Enter: ConfigMaps and Secrets ...

View the full article

Day 6: ConfigMaps & Secrets — Managing App Settings and Sensitive Data in Kubernetes

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...