This will allow each cloud provider to be released on a different cadence to Kubernetes itself. The Kubernetes community is currently in the process of moving cloud vendor specific code into their own cloud provider repositories. OverviewĪfter a lot of searching which turned up little information, this blog post serves as an answer to anyone else needing or wanting to achieve the same thing. I thus needed to build, package, deploy & test Kubernetes for AWS from the Kubernetes Git repository – this blog records the travails and steps of what is required to do this. As long as these simulated masters resided somewhere in AWS, I would be able to accurately test the AWS integration. Instead I needed to run the masters myself and essentially simulate EKS. This meant I wasn’t able to use EKS directly to test the changes as the EKS master nodes are not able to be controlled or upgraded by users. This lies entwined with the kube-controller-manager which runs on the masters. The particular Kubernetes code in question is in the part of the repository responsible for communicating with the AWS EC2 APIs.
0 Comments
Leave a Reply. |