Skip to content
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

Jump to bottom

Make internal deployer work for "fresh" clusters/namespaces #10

Open
12 tasks
tsutsu opened this issue Feb 4, 2021 · 0 comments
Open
12 tasks

Make internal deployer work for "fresh" clusters/namespaces #10

tsutsu opened this issue Feb 4, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@tsutsu
Copy link
Member

tsutsu commented Feb 4, 2021 •
edited
Loading

  • 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
@tsutsu tsutsu added the enhancement New feature or request label Feb 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tsutsu