Chainguard Container for cluster-api-aws-controller

Kubernetes Cluster API Provider AWS provides consistent deployment and day 2 operations of "self-managed" and EKS Kubernetes clusters on AWS

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/cluster-api-aws-controller:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

Chainguard's cluster-api-aws-controller image is compatible with the upstream Cluster API Provider AWS. This image contains only the minimum set of dependencies needed to run the AWS infrastructure provider components.

Getting Started

The Cluster API Provider for AWS enables you to create and manage Kubernetes clusters on Amazon Web Services using Cluster API. It provides declarative APIs for provisioning and managing AWS infrastructure resources including EC2 instances, VPCs, load balancers, and security groups.

Prerequisites

• A management cluster with Cluster API core components installed
• clusterctl CLI tool
• Amazon Web Services account with appropriate permissions
• AWS credentials configured (AWS CLI, IAM roles, or environment variables)

Installation

Initialize the AWS infrastructure provider using clusterctl:

clusterctl init --infrastructure aws

Or manually install using the Chainguard image by applying the InfrastructureProvider resource:

kubectl apply -f - <<EOF
apiVersion: operator.cluster.x-k8s.io/v1alpha2
kind: InfrastructureProvider
metadata:
  name: aws
  namespace: aws-infrastructure-system
spec:
  version: v2.8.4
  configSecret:
    name: aws-credentials
  deployment:
    containers:
    - name: manager
      imageUrl: cgr.dev/ORGANIZATION/cluster-api-aws-controller:latest
EOF

Usage Example

Create an AWS cluster using Cluster API resources:

apiVersion: infrastructure.cluster.x-k8s.io/v1beta2
kind: AWSCluster
metadata:
  name: my-aws-cluster
  namespace: default
spec:
  region: us-east-1
  network:
    vpc:
      id: ""
  controlPlaneEndpoint:
    host: "1.2.3.4"
    port: 6443
---
apiVersion: infrastructure.cluster.x-k8s.io/v1beta2
kind: AWSMachineTemplate
metadata:
  name: my-cluster-control-plane
  namespace: default
spec:
  template:
    spec:
      instanceType: t3.medium
      ami:
        id: ami-12345678
      publicIP: true
      rootVolume:
        size: 50
        type: gp3

Configuration

The controller requires AWS credentials with the following IAM permissions:

• EC2 Full Access or equivalent granular permissions
• ELB (Elastic Load Balancer) management permissions
• VPC and networking management permissions
• IAM permissions for service-linked roles

Create and configure the credentials secret:

kubectl create secret generic aws-credentials \
  --from-literal="AWS_B64ENCODED_CREDENTIALS=$(base64 -w0 < ./aws-credentials)" \
  --namespace aws-infrastructure-system

Where aws-credentials file contains:

[default]
aws_access_key_id = YOUR_ACCESS_KEY_ID
aws_secret_access_key = YOUR_SECRET_ACCESS_KEY

Documentation and Resources

• Cluster API Provider AWS GitHub Repository
• Cluster API Documentation
• Amazon Web Services Documentation

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.