Make internal deployer work for "fresh" clusters/namespaces
tsutsu opened this issue · 0 comments
tsutsu commented
- if KALM is not installed, install it
- if cluster is not migrated to correct minimum cluster-version as specified in
migrations
ConfigMap inorbital-system
Namespace, then clone the relevantcluster-migrations
repo (specified by the deploy env) and run migrations against the cluster - Create cluster resources if they don't exist:
- the
Namespace
- the
deployer-role
ClusterRoleBinding - the
deployer
ServiceAccount - the
git-token
Secret- this should be a
ManagedSecret
in the project - if the
ManagedSecret
doesn't exist, build it interactively, using GitHub OAuth device flow
- this should be a
- the
Application
- the
ReleaseTrack
- the
- Ensure the
Secret
unsealed from theManagedSecret
exists before applying the new version to theReleaseTrack