Chainguard Container for kube-vip-cloud-provider

A general purpose cloud provider for kube-vip

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/kube-vip-cloud-provider: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 kube-vip-cloud-provider image contains only the minimum set of tools and dependencies needed to function. It is comparable to the official kube-vip-cloud-provider image from kube-vip.

Getting Started

You can install Chainguard's kube-vip-cloud-provider image using the kube-vip Helm chart:

Create a values.yaml file for helm installation.

cat > values.yaml <<EOF
image:
repository: cgr.dev/ORGANIZATION/kube-vip-cloud-provider
tag: <tag>
EOF

Make sure to replace ORGANIZATION with the name of your Chainguard organization. Additionally, replace <tag> with your desired container image tag.

Install the Chainguard's kube-vip-cloud-provider image using helm chart:

helm repo add kube-vip https://kube-vip.github.io/helm-charts

helm install kube-vip-cloud-provider kube-vip/kube-vip-cloud-provider \
--namespace kube-system --create-namespace \
--values values.yaml --wait

Next, define address pools in a ConfigMap:

kubectl -n kube-system create configmap kube-vip-cloud-provider \
--from-literal=cidr-global=<GLOBAL_POOL_CIDR> \
--from-literal=cidr-development=<DEV_POOL_CIDR>

Be sure to replace GLOBAL_POOL_CIDR and DEV_POOL_CIDR with your desired address pools.

Then create an nginx service which will be watched by the cloud provider:

cat <<EOF | kubectl apply -n lb-test -f -
apiVersion: apps/v1
kind: Deployment
metadata: { name: nginx }
spec:
replicas: 1
selector: { matchLabels: { app: nginx } }
template:
    metadata: { labels: { app: nginx } }
    spec:
    containers:
    - name: nginx
        image: nginx:1.25.4
        ports: [{ containerPort: 80 }]
---
apiVersion: v1
kind: Service
metadata: { name: nginx }
spec:
type: LoadBalancer
selector: { app: nginx }
ports: [{ port: 80 }]
EOF

Finally, verify the address assignment:

kubectl -n lb-test get svc nginx \
-o jsonpath='{.metadata.annotations.kube-vip\.io/loadbalancerIPs}'

The resulting address should be in between the address pools you defined.

Documentation and Resources

For more information, refer to the kube-vip-cloud-provider usage 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.