note: This article describes how to deploy GitHub secrets in Azure Kubernetes clusters using GitHub actions. It should be more or less applicable regardless of which code repository and CI/CD platform you use.

In part 1, I described the issues of managing environmental variables between software developers and traditional operations groups. You can read it here:
https://forrestkc.medium.com/deploying-configmaps-with-apps-to-kubernetes-b56224432824

In this article, I am going to talk about secrets, specifically creating K8s secrets from GitHub secrets. Credentials like database credentials and api keys should not be stored in the repo itself, but rather in a Github secret. …


One of the biggest pain points between developers and devops (or in the old days, operations) are environmental variables.

Prior to the Kubernetes revolution, environmental variables were typically stored in .env files on the servers the app was deployed to. For example, a web service that ran on 6 servers would have a .env file on each individual server that the operations group would typically manage. Those .env …

forrestkc

Outdoorsy DevOps Engineer.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store