Decommission Hasura

[jimleroyer]

Description

As a system operator for GCNotify, I want to get rid of Hasura, So that we remove tools with subpar security and audit best practices And leverage newer tools that are better aligned with these.

WHY are we destroying?

Hasura served us long enough for direct access to the database but it is limited for audits, user managements and logs. We now have AWS VPNs in place which do these better.

WHAT are we building?

Getting rid of Hasura.

VALUE created by our solution

Better alignment with the organization best practices around audits and security. Simplifying our overall access to the database management while having something more solid in place.

Acceptance Criteria

• [x] Hasura is inaccessible and removed from our kubernetes resources.

QA Steps

• [x] Check if we can still connect to Hasura.
• [x] Check if Hasura pods are up and runnning in staging.
• [x] Check if Hasura pods are up and runnning in production.

[jimleroyer]

We removed the Hasura instances in both staging and production environments. This should not be reachable anymore and completely down. The PR to remove it from Terraform/kustomize was merged as well so further infrastructure releases will recreate Hasura related resources.