Skip to content

Update component multi tenancy how-to for multi-instance aware components #186

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
simu merged 1 commit into from
Feb 21, 2025
Merged

Update component multi tenancy how-to for multi-instance aware components #186

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 13 additions & 1 deletion docs/modules/ROOT/pages/how-tos/component-multi-tenancy.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,8 +33,20 @@ local appPath =
['%s/<component>' % appPath]: app, <1>
}
----
<1> Replace `<component> with the component's name.
<1> Replace `<component>` with the component's name.
<2> We use `std.get()` here because `commodore component compile` generates an empty application manifest by default.
+
[NOTE]
====
If you're making a multi-instance aware component multi-tenant aware, you'll need to make sure that you create an ArgoCD app per instance.
Additionally, you'll need to call `argocd.App()` with the optional parameter `base` set to the component name.

[source,jsonnet]
----
local instance = inv.parameters._instance;
local app = argocd.App(instance, params.namespace, secrets=true, base=<component>);
----
====

. Adjust the component's Kapitan compile step for the application manifests (in `class/<component-name>.yml`)
+
Expand Down