G8/Helm: artifacts grouping and naming profiles #6
Labels
No Label
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: siatel/cloud#6
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
currently the namespace specified on chart install is used to group the artifacts deployed as a Gargantua app instance and also the ingress, it's host url, the persistent volumes claims etc, i.e. if installing the chart to namespace 'demo' then an ingress named 'demo-ingress' will be deployed to namespace 'demo' and will configure the 'https://demo.' for access to the app, a 'demo-database-pvc' claim for database storage if specified as 'provisioned' etc.
A means that will allow for profile-based schemas of naming and grouping the app resources that is not exclusively based on the namespace, but on an 'appKey' chart value is to be developed.
Profiles 'localDev', 'siatelRo' and 'siatelCom' with pre-enabled ingress and hostPath storage are available. A database is included based on the availability of .Values.database.jdbcUrl