Source: medium.com
Using Helm with Amazon EKS without a kubeconfigCategory: Kubernetes
The current tool is a golang app which, given the path to a helm chart and kubeconfig, will deploy to all our production namespaces (in that cluster) at once using helm (will write a separate blog on this later). The current tool we use utilizes helm2 libraries from like..when Obama was still president.
In order for us to use helm we had to use the port forwarding method from Kubernetes to bind a local port to tiller’s service port (44134).
There were a plethora of new features, one of which is Tiller going away and helm will be directly interacting with the Kubernetes API.
The general flow to access your EKS cluster programmatically is to use a series of libraries and api calls to generate a token to create a K8s clientset to interact with your cluster.
In order for us to use helm we had to use the port forwarding method from Kubernetes to bind a local port to tiller’s service port (44134).
There were a plethora of new features, one of which is Tiller going away and helm will be directly interacting with the Kubernetes API.
The general flow to access your EKS cluster programmatically is to use a series of libraries and api calls to generate a token to create a K8s clientset to interact with your cluster.
Related Articles
Community Partners
DevOps Careers