feat: onboard directus

[walkoss]

Summary

• Onboard directus Onboard Directus.io #536

Test Plan

• Deployed helm chart + terraform locally

Next

• Set docker image from plural registry
• Configure file storage backend (s3, gcs, blob)
• Configure OIDC

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

[michaeljguarino]

rm this file

[michaeljguarino]

does directus not require S3 or another form of object storage?

[walkoss]

They don't need it to get it work, but I'm planning to add a file storage to the bucket later along with postgres backend and oidc auth

[michaeljguarino]

We should definitely use the postgres operator to set up a proper db here as well, you should be able to see a lot of prior art using the module-library postgres chart that wraps a lot of the helpful resources together for it

[walkoss]

We should definitely use the postgres operator to set up a proper db here as well, you should be able to see a lot of prior art using the module-library postgres chart that wraps a lot of the helpful resources together for it

Yes for sure! Might need some help for this maybe

[michaeljguarino]

you can see some postgres related templating here: https://github.com/pluralsh/plural-artifacts/pull/635/files

jupyterhub was weird because we had to feed it the entire postgres url, which isn't needed for directus, looks like you can just wire up these env vars: https://docs.directus.io/self-hosted/config-options.html to give it the right db configuration. You'll almost certainly need to add DB_SSL__REJECT_UNAUTHORIZED=false too as an env var

it looks like directus does require s3/gcs/etc so might want to revert the kube terraform module and go back to the standard cloud specific ones too

[plural-bot]

🎉 This PR is included in version 1.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀