covalenthq/orbital

Make internal deployer work for "fresh" clusters/namespaces

tsutsu opened this issue · 0 comments

  • if KALM is not installed, install it
  • if cluster is not migrated to correct minimum cluster-version as specified in migrations ConfigMap in orbital-system Namespace, then clone the relevant cluster-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
    • the Application
    • the ReleaseTrack
  • Ensure the Secret unsealed from the ManagedSecret exists before applying the new version to the ReleaseTrack