plural-artifacts icon indicating copy to clipboard operation
plural-artifacts copied to clipboard

feat(hasura): Upgrade hasura to latest version ENG-858

Open floreks opened this issue 3 years ago • 1 comments

Summary

Finally, with a lot of help from @DavidSpek (thank you!) it seems to be finished.

  • Moved to a different base chart that we ended up forking anyway (based on https://artifacthub.io/packages/helm/hasura-extra/hasura)
  • Bumped to the newest available stable version (v2.15.0)
  • Updated runbooks

I have tested a few different upgrade scenarios to ensure that it won't break anything for existing users using an external database.

Test Plan

Tested on my AWS cluster.

Scenario 1 (existing user with external postgres)

  • used free tier AWS RDS Postgres DB
  • installed the existing v2.0.9 artifact while settings the postgresqlDisabled: true in my context.yaml and using RDS AWS DB
  • upgraded to v2.0.15

Scenario 2 (existing user with our internal postgres)

This one creates a secret recognized by the operator that is deleted by helm during upgrade. To work around the issue with postgres operator resync not being called after upgrade, I have update our postgres configuration to switch to a new user for the existing DB. Upgrade went ok also.

Scenario 3 (new user)

This one was simple. No issues here.

Checklist

  • [ ] No images hosted from dockerhub
  • [ ] Are dashboards present to understand the health of the application. There must be at least 1 of these
    • [ ] all databases should have dashboards
    • [ ] ideally also have at least cpu/mem utilization dashboards for webserver tier of the app
    • [ ] you can use plural from-grafana to convert a grafana dashboard found via google to our CRD
  • [ ] Are scaling runbooks present
    • [ ] all databases must have scaling runbooks
    • [ ] you can use the charts in pluralsh/module-library to accelerate this
  • [ ] do you need to add config overlays?
    • [ ] inputing secrets
    • [ ] configuring autoscaling
  • [ ] If there’s a web-facing component to the app, we need to support OIDC authentication and setting up private networks if no authentication option is viable
  • [ ] All major clouds must be supported
    • [ ] Azure
    • [ ] AWS
    • [ ] GCP

floreks avatar Oct 26 '22 15:10 floreks

PTAL @DavidSpek @michaeljguarino

floreks avatar Nov 23 '22 10:11 floreks