feat: onboard unleash

[walkoss]

Summary

• Onboard Onboard Unleash #294
• Added OIDC

Test Plan

• Deployed helm chart + terraform locally

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]

I suspect using the oauth proxy might also require oauth for the feature flag apis and some workaround will be needed there, probably w/ adding a dedicated ingress path for them

[plural-bot]

🎉 This PR is included in version 1.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[walkoss]

I suspect using the oauth proxy might also require oauth for the feature flag apis and some workaround will be needed there, probably w/ adding a dedicated ingress path for them

Good catch, I'll fix it
Should we always have OIDC support? Unleash has a auth system already

[michaeljguarino]

I don't think it's necessary to always enable oidc, what you can do is have a dedicated path for the flag apis that are exposed publicly that routes to a service that is directed to the regular unleash container ports instead of the oauth proxy ones