Config Maps and Secrets

• Refer Here for official docs of config maps
• Refer Here for the changes done to read the values from config maps into pods
• Config maps gives us flexibility to separate configuration from Pod
• The sensitive information is still in plain text, To solve this Secrets for k8s gives an base64encoding based approach to store sensitive information
• Refer Here for official docs of secrets
• Refer Here for changes done to use secrets
• The production approach for storing sensitive information will be
  • Use an external secrets manager like azure key vault, aws secrets manager, gcp secrets manager or hashicorp vault
  • Use secrets CSI Driver of a vendor to get the sensitive information into k8s as storage

Health Checks or Probes in Kubernetes

• In K8s we have 3 types of Probes
  • Liveness Probe:
    • Determines if the container is running or not
    • If Probe fails the container is restarted
  • Readiness Probe
    • Determines if the application is running or not
    • If probe fails, this container will not recieve requests from service
  • Startup Probe
    • Determines if the container starup is complete or not
    • If this probe fails no further probes are executed
• Refer Here for official docs
• Configuring probes Refer Here
• Refer Here for the changes.