crossplane-azuread

packaged by Chainguard

Chainguard Container for crossplane-azuread

Crossplane provider for managing Microsoft Entra ID (Azure Active Directory) resources in Kubernetes.

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/crossplane-azuread: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 Crossplane AzureAD provider is comparable to the upstream AzureAD provider, with the following differences:

• AzureAD is a standalone provider. It is not part of the Azure (ARM) provider family. It needs no family provider, and it ships its own ProviderConfig controllers and CRDs.
• The image is minimal. Unlike the upstream Alpine-based image, it doesn't include a shell or package manager.
• The provider binary is installed at /usr/bin/provider-azuread. A compatibility symlink at /usr/local/bin/provider keeps the upstream provider entrypoint working. The Crossplane package metadata is shipped at /package.yaml.
• The image runs as UID 65532 with primary GID 0 by default, the same as upstream.

Prerequisites

You need a Kubernetes cluster with Crossplane installed, for example with the crossplane Helm chart from https://charts.crossplane.io/stable. Crossplane's chart only installs Crossplane itself. You install the AzureAD provider separately with a Provider resource.

Getting Started

Install the AzureAD provider directly. No family provider is required:

apiVersion: pkg.crossplane.io/v1
kind: Provider
metadata:
  name: provider-azuread
spec:
  package: cgr.dev/ORGANIZATION/crossplane-azuread:latest

Wait for the provider to become installed and healthy:

kubectl wait provider.pkg.crossplane.io/provider-azuread \
  --for=condition=Healthy --timeout=5m

Configuration

The provider authenticates to Microsoft Entra ID with an application (service principal). Store its credentials as JSON in a Kubernetes secret, then reference that secret from a ProviderConfig in the azuread.upbound.io API group:

cat <<EOF | kubectl apply -f -
apiVersion: v1
kind: Secret
metadata:
  name: azuread-secret
  namespace: crossplane-system
type: Opaque
stringData:
  credentials: |
    {
      "clientId": "${AZURE_CLIENT_ID}",
      "clientSecret": "${AZURE_CLIENT_SECRET}",
      "tenantId": "${AZURE_TENANT_ID}"
    }
EOF

cat <<EOF | kubectl apply -f -
apiVersion: azuread.upbound.io/v1beta1
kind: ProviderConfig
metadata:
  name: default
spec:
  credentials:
    source: Secret
    secretRef:
      namespace: crossplane-system
      name: azuread-secret
      key: credentials
EOF

Creating a ProviderConfig doesn't confirm that authentication works. The provider reads the credentials when it reconciles a managed resource. The application also needs the Microsoft Graph permissions that each resource type requires. For example, managing groups needs Group.ReadWrite.All. For each resource's permissions, see the upstream examples and the Terraform AzureAD provider documentation.

The provider serves metrics on port 8080.

Documentation and Resources

• Crossplane AzureAD Provider
• AzureAD Provider Examples
• Crossplane Providers 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.