Superset production configuration and testing

[bmtcril]

There are a number of production use cases and configurations that we need to test and fix where broken. This issue is to track all of those, and they can be broken out into separate issues if the size of the work warrants it. Right now this is just collecting things in one place.

• Test against ClickHouse Cloud
• Test against ClickHouse SSL
• Test Superset SSL configuration
• Make a production ready k8s configuration
• Test K8s, including Superset running from a different namespace than other services
• Pin image versions
• Run a security pass on Superset packages versions, image, and configuration

[Ian2012]

@bmtcril When running on HTTPS the sso doesn't work because the redirect uri is taken as http:{{LMS_HOST}}/...

Any ideas?

Checking the application configuration shows the correct information:

[Ian2012]

The following tasks were performed:

• Test Superset SSL configuration
• Make a production ready k8s configuration
• Pin image versions

[bmtcril]

Thanks @Ian2012 , I've updated the ticket. I also created a new issue for the SSL bug mentioned above: #30

[mariajgrimaldi]

Can we list the current issues blocking production configuration? Like #30? Or the only blocking stuff is what is listed above?

[bmtcril]

The list of known v1 blocking issues should be everything labeled "oars v1": https://github.com/search?q=org%3Aopenedx+label%3A%22oars+v1%22++++&type=issues&state=open

If you run across anything missing the label let me know or use the Github comment-to-label action: label: oars v1

[Ian2012]

@bmtcril can this be closed?

[bmtcril]

I think so, we'll need another round of testing everything once the projects are consolidated but that's a whole other ticket