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.

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

Staging deployment #96

Merged
merged 6 commits into from
Jun 27, 2024
Merged

Staging deployment #96

merged 6 commits into from
Jun 27, 2024

Conversation

DavidFair
Copy link
Collaborator

Description:

  • Rotates the app creds and FIP so it goes into the proper project instead of Megan's scratch space
  • Rotate the Argo keys ready for deployment

Special Notes:


Submitter:

Have you:

  • Labelled this PR, e.g. bug, deployment, enhancement ...etc.
  • A deployment can be reviewed, and merged, by a single reviewer.
  • It can only be used to deploy, change, or remove clusters based on existing patterns for staging.
  • Anything involving prod, or production facing services must use the normal 2 person review.
  • All other PR types require the usual PR process (e.g. 2 person).

Reviewer

Have you:

  • Verified this PR uses the correct label(s) based on the rules above?
  • Checked if this could affect production (e.g. a global value that's changed without an override)?
  • Tested setting this up, if it's not a deployment, to verify it can be redeployed with any documentation if appropriate?

Since our staging and prod clusters will end up in the same prod project
(initially), ensure that we include the environment to make the VMs and
resources distinguishable
Rotate the secrets to point to the correct project with a dedicated
service account now we're ready to deploy a real staging cluster
Generate a new public key to prep for the Argo portion of the deployment
Re-point to main in anticipation of this branch being merged, so that we
have the correct revision
This was stored in a secure location, so use that to make deployment
easier as we have it to hand
interface: ENC[AES256_GCM,data:BbAkqAl2,iv:C43Wn+6sc67DsuBQApNouzl8te0sN4Tej58hv/46IYk=,tag:Y7xQZ10jOY0bHUV1Kx+T8w==,type:str]
identity_api_version: ENC[AES256_GCM,data:6g==,iv:yLAVeDeTNEi135EgCH3u0y9MsOAiNGn07XV5b0HzLuA=,tag:MOvJQwEB8r+qbAhoy9ZNbQ==,type:int]
auth_type: ENC[AES256_GCM,data:VAEhPWNmMUZQMwK7ZnI3CD+Ta+qb2A4=,iv:fLvry0hPwhGQ5Ss62nwvmcKoFd8hGEbpjsQ38c0otqU=,tag:Sv8pPcZ8a8gGWfw7CNpLaw==,type:str]
clouds:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you removed openstack_cluster: top part - I don't think this will work now

This was missing the subchart name in the values, so it would not have
applied correctly
@anish-mudaraddi anish-mudaraddi merged commit 0e00719 into main Jun 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants