Source: thenewstack.io
Access AWS Services Through a Kubernetes Dual-Stack ClusterCategory: Kubernetes, Ubuntu, github, yaml
https://github.com/Lakers817' This article series will focus on connecting a Kubernetes dual IPv4/IPv6 stack with https://aws.amazon.com/?utm_content=inline-mention‘ service APIs, using AWS-cloud-controller-manager (I’ll refer AWS-Cloud-Controller-Manager as “AWS-ccm” and Kubernetes as K8s throughout the article). I will not go into the details of how to set up an AWS cluster on Kubernetes, instead will focus specifically on aws-cloud-controller-manager in detail.
Before 1.20, AWS-ccm was part of the core Kubernetes API and we use it to enable the flag–cloud-provider=aws in API server, controller-manager and kubelet service file to connect to the AWS resources — but not anymore.
First, I had created https://cloud-provider-aws.sigs.k8s.io/prerequisites/ for EC2 instances for the AWS-ccm to be able to communicate to AWS’ APIs.
The aggregation layer configuration enables the Kubernetes API server to be extended with additional APIs that are not part of the Kubernetes API core.
Before 1.20, AWS-ccm was part of the core Kubernetes API and we use it to enable the flag–cloud-provider=aws in API server, controller-manager and kubelet service file to connect to the AWS resources — but not anymore.
First, I had created https://cloud-provider-aws.sigs.k8s.io/prerequisites/ for EC2 instances for the AWS-ccm to be able to communicate to AWS’ APIs.
The aggregation layer configuration enables the Kubernetes API server to be extended with additional APIs that are not part of the Kubernetes API core.
Related Articles
Community Partners
DevOps Careers