Skip to main content
Easily extend your clusters with powerful integrations, tools, and automation using Ankra Add-ons.

What is an Add-on?

An add-on is a packaged application or tool that extends the functionality of your Kubernetes cluster. Add-ons are typically distributed as Helm charts and can include anything from monitoring tools and ingress controllers to security solutions and custom integrations. An add-on could even be your own application, integrated into the Ankra ecosystem for easy deployment and management. By using add-ons, you can quickly enhance your clusters with new features and automate the deployment of common services.

Manage Add-on Sources

An add-on source in Ankra is either a Helm repository URL or an OCI (Open Container Initiative) registry URL. These sources contain the Helm charts you want to use for deploying add-ons to your clusters. Helm charts are a standard way to package Kubernetes applications, making it easy to manage dependencies and versioning for complex workloads. By connecting both public and private Helm repositories or OCI registries, you can access a wide range of Kubernetes add-ons. This lets you integrate open-source tools, vendor solutions, or your own custom charts-all from a single interface. Managing sources centrally ensures your team always has access to the latest and most secure versions of your preferred add-ons. How to Add a Source:
  1. Go to the Charts page in the main navigation.
  2. Click the Manage Registries button.
  3. Click Add and enter the Helm repository or OCI registry URL you want to use.
Once you add a source, Ankra will begin indexing the available charts. You’ll see a Last Synced timestamp update when indexing is complete. After that, your add-ons will be available for installation. Learn more about Helm Registries →

Stacks

To deploy an add-on onto your cluster, add it to a stack. You can add multiple add-ons and manifests to build a Stack, which is a repeatable, reusable set of components for your Kubernetes environments. Stacks let you bundle everything your application or platform needs, from monitoring and logging to ingress controllers and security policies. You can version stacks, share them with your team, and deploy them to any cluster with a single action. This approach speeds up onboarding, reduces errors, and helps make sure every environment is production-ready. Learn more about Stacks →

Install Add-ons

Add-ons in Ankra are installed through Stacks. This ensures your add-ons are bundled with their dependencies and can be managed as a cohesive unit.
1

Navigate to Stacks

Go to the Stacks section in your cluster and click Create Stack (or edit an existing stack).
2

Add an Add-on

In the Stack Builder, click Add and select Add-on. Browse or search for charts from your connected registries.
3

Configure Values

Select the chart version and configure the values. You can use the AI Assistant (⌘+J) to help customize the configuration.
4

Deploy

Save your stack and deploy it to install the add-on on your cluster.
Ankra handles versioning, dependency management, and cluster targeting for you. This makes it easy to standardize tooling and services across all your environments, ensuring consistency and reducing operational overhead. Want to upload your own add-on? Add your registry to the Ankra Platform. Read more here.

Encrypting Sensitive Values with SOPS

When your add-on configuration contains sensitive data like passwords, API keys, or webhook URLs, use SOPS to encrypt them before storing in your GitOps repository.
1

Open the Add-on Editor

Edit an add-on within your stack by clicking on it in the Stack Builder.
2

Click the SOPS Button

In the values edit view, click the SOPS button in the toolbar to enable encryption.
3

Encrypt Sensitive Values

SOPS will encrypt sensitive values (like adminPassword or slack_api_url) while keeping keys readable for easier Git diffs.
4

Save

Save your add-on configuration. The encrypted values will be stored safely in your GitOps repository and decrypted automatically when deployed.
SOPS encryption requires initial setup. See SOPS Encryption for configuration instructions.

Manifests

A manifest is a Kubernetes YAML file that defines resources or configuration, like namespaces, CRDs, or RBAC rules. In Ankra, manifests help you:
  • Include manifests in stacks: Make sure your clusters are ready for add-ons by setting up all prerequisites and custom resources first.
  • Automate environment setup: Create the foundational resources your add-ons and workloads need, so your stacks are fully self-contained and repeatable.
Manifests are key for customizing clusters and making sure every deployment fits your team’s needs. Learn more about Manifests →
With add-ons, manifests, and stacks, Ankra makes it easy to manage, scale, and standardize your Kubernetes infrastructure, no matter how complex your needs are.

Explore the Add-ons API

Want to automate add-on management or integrate with your CI/CD workflows? Check out the API Reference for endpoints to list, install, and manage add-ons programmatically.