Chainguard Container for linkerd-extension-init

A utility for initializing Linkerd extension namespaces after installation

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/linkerd-extension-init:latest

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

Compatibility Notes

The Chainguard linkerd-extension-init Image is comparable to the linkerd-extension-init image. However, the Chainguard image contains only the minimum set of tools and dependencies needed to function; for example, it does not include a package manager.

Getting Started

To get started with Chainguard's linkerd-extension-init Image, you need to deploy linkerd:

kubectl apply -f https://github.com/kubernetes-sigs/gateway-api/releases/latest/download/standard-install.yaml
linkerd install --crds | kubectl apply -f -
linkerd install | kubectl apply -f -
linkerd check

Deploy with Helm Chart

There are 3 different linkerd Helm Charts that consumes this image:

• linkerd-viz
• linkerd-jaeger
• linkerd-multicluster

Override namespaceMetadata field in the values.yaml file:

cat <<EOF > values.yaml
namespaceMetadata:
  image:
    registry: "cgr.dev/ORGANIZATION"
    name: linkerd-extension-init
    tag: latest
EOF

Add the Linkerd Edge Helm repository:

helm repo add linkerd-edge https://helm.linkerd.io/edge
helm repo update

Install the CRDs:

helm install linkerd-crds linkerd-edge/linkerd-crds \
  -n linkerd \
  --create-namespace

Install the one of the Helm Charts:

helm search repo linkerd
# Let's install the linkerd-viz for example
helm install linkerd-viz linkerd-edge/linkerd-viz \
  -n linkerd-viz \
  --create-namespace \
  -f values.yaml

Now ensure that the Pod is completed successfully and namespace is labeled with linkerd.io/extension: viz:

kubectl get ns linkerd-viz -L linkerd.io/extension

Documentation and Resources

For more information, please refer to the linkered-extension-init GitHub repository. To install Linkerd with Helm, please refer to the Installing Linkerd with Helm documentation.

What are Chainguard Containers?

Chainguard Containers are minimal container images that are secure by default.

In many cases, the Chainguard Containers tagged as :latest contain only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager. Chainguard Containers are built with Wolfi, our Linux undistro 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 -dev variant.

Although the -dev container image variants have similar security features as their more minimal versions, they feature additional software that is typically not necessary in production environments. We recommend using multi-stage builds to leverage the -dev variants, copying application artifacts into a final minimal container that offers a reduced attack surface that won’t allow package installations or logins.

Learn More

To better understand how to work with Chainguard Containers, please visit Chainguard Academy and Chainguard Courses.

In addition to Containers, Chainguard offers VMs and Libraries. Contact Chainguard to access additional products.

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.