@@ -4,7 +4,7 @@ UnderStack **Components** are deployed via [ArgoCD]
4
4
as [ Applications] [ argocd-app ] , these are generated using [ ArgoCD] [ argocd ] 's
5
5
[ ApplicationSet] [ argocd-appset ] controller. This allows us to use common
6
6
patterns to deploy each of the components and allow specific environments
7
- to modify or disable some components. See the [ Configuring Components] ( ./component-config.md )
7
+ to modify or disable some components. See the [ Configuring Components] ( ../deploy-guide /component-config.md )
8
8
guide for more info on how to do so.
9
9
10
10
## Adding a Component to UnderStack
@@ -50,12 +50,26 @@ sources:
50
50
51
51
{% endraw %}
52
52
53
+ ### Configuring the namespace
54
+
55
+ If the namespace you'll be adding the component to is currently not in
56
+ use, you will have to add it to the appropriate AppProject for the
57
+ ApplicationSet in one of the following:
58
+
59
+ - ` apps/appsets/project-understack-infra.yaml`
60
+ - ` apps/appsets/project-understack-operators.yaml`
61
+ - ` apps/appsets/project-understack.yaml`
62
+
53
63
# # Removing an application from UnderStack
54
64
55
65
Removing a Component permanently from UnderStack is as easy as
56
66
deleting its YAML config from its AppSet in the `apps/<appset>/`
57
67
directory.
58
68
69
+ !!! note
70
+ Remove the namespace from the AppProject if it is no longer
71
+ in use.
72
+
59
73
[argocd] : <https://argo-cd.readthedocs.io/en/stable/>
60
74
[argocd-app] : <https://argo-cd.readthedocs.io/en/stable/user-guide/application-specification/>
61
75
[argocd-appset] : <https://argo-cd.readthedocs.io/en/stable/operator-manual/applicationset/>
0 commit comments