sveltos-access-manager

packaged by Chainguard

Chainguard Container for sveltos-access-manager

Minimal Sveltos Access Manager image for managing tenant permissions and access credentials across Kubernetes clusters.

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/sveltos-access-manager: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 cgr.dev/ORGANIZATION/sveltos-access-manager image is comparable to the upstream projectsveltos/access-manager image. It preserves the /manager entrypoint, / working directory, UID and GID 65532:65532, and absence of default command arguments. The /manager compatibility symlink points to the packaged executable at /usr/bin/manager.

This image contains the Access Manager controller. The upstream projectsveltos Helm chart deploys other Sveltos components in separate containers. The minimal image does not include a shell or package manager.

Prerequisites

You need a Kubernetes cluster supported by the upstream chart, Helm, kubectl, and permission to install custom resource definitions and cluster RBAC. Configure the cluster to authenticate to Chainguard's registry and pull cgr.dev/ORGANIZATION/sveltos-access-manager. If you use an image pull Secret, add it to global.imagePullSecrets in the values file below.

Getting Started

Install Sveltos with its official Helm chart, overriding the Access Manager image. Replace ORGANIZATION with your organization's registry repository name. Leave the image tag unset so the chart selects the Access Manager release it ships:

helm repo add projectsveltos https://projectsveltos.github.io/helm-charts
helm repo update
cat > values.yaml <<'EOF'
global:
  useDigest: false
accessManager:
  enabled: true
  manager:
    image:
      registry: cgr.dev
      repository: ORGANIZATION/sveltos-access-manager
EOF
helm upgrade --install sveltos projectsveltos/projectsveltos \
  --namespace projectsveltos --create-namespace \
  --values values.yaml --wait --timeout 5m
kubectl rollout status deployment/access-manager \
  --namespace projectsveltos --timeout=180s

The chart creates the controller's service account, permissions, and CRDs, and sets the required NAMESPACE environment variable from the Pod's namespace. Keep global.useDigest at its default of false: when it is true, the chart uses accessManager.manager.image.digest, which defaults to the upstream image digest. The other Sveltos components retain their chart defaults.

Configuration

Access Manager uses RoleRequest resources to grant tenant service accounts permissions in registered clusters. The chart registers the management cluster as the mgmt SveltosCluster in the mgmt namespace. Label it so the example below selects it, or follow the cluster registration guide to register a managed cluster with the same label:

kubectl label sveltoscluster mgmt --namespace mgmt env=demo

The following example creates a tenant service account and a policy in the management cluster. The controller grants that tenant permission to read Pods in the matching managed clusters:

cat > tenant-access.yaml <<'EOF'
apiVersion: v1
kind: ServiceAccount
metadata:
  name: demo-reader
  namespace: default
---
apiVersion: v1
kind: ConfigMap
metadata:
  name: demo-pod-reader
  namespace: default
data:
  role.yaml: |
    apiVersion: rbac.authorization.k8s.io/v1
    kind: ClusterRole
    metadata:
      name: demo-pod-reader
    rules:
      - apiGroups: [""]
        resources: ["pods"]
        verbs: ["get", "list", "watch"]
---
apiVersion: lib.projectsveltos.io/v1beta1
kind: RoleRequest
metadata:
  name: demo-pod-reader
spec:
  serviceAccountName: demo-reader
  serviceAccountNamespace: default
  clusterSelector:
    matchLabels:
      env: demo
  roleRefs:
    - kind: ConfigMap
      name: demo-pod-reader
      namespace: default
EOF
kubectl apply -f tenant-access.yaml
kubectl wait rolerequest/demo-pod-reader \
  --for=jsonpath='{.status.clusterInfo[0].status}'=Provisioned --timeout=120s
kubectl get rolerequest demo-pod-reader -o yaml

Inspect status.matchingClusters for the selected clusters, status.clusterInfo[].status for deployment state, and status.clusterInfo[].failureMessage for reconciliation failures. See the upstream multi-tenancy guide for tenant onboarding and additional policy examples.

Documentation and Resources

• Access Manager source code
• Sveltos documentation
• Official Helm chart

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.