feat(webscocket): helm support for async query with superset-websocket

[benjaminrene]

SUMMARY

Requires #21379 to be resolved
Deploy superset-websocket on helm chart to enable QUERY_ASYNC feature for helm deployement.

Add a deployment dedicated to websocket
Add a service to expose websocket pods
Allow to configure a BASE_PATH on superset-websocket in order to expose websocket on the same port (80)
Add to the existing ingress a subpath to redirect websocket queries
Tune superset config to activate QUERY_ASYNC feature

TESTING INSTRUCTIONS

helm install with websocket.enabled = true on values file

ADDITIONAL INFORMATION

• Has associated issue: Helm: deploy websocket for the benefit of query async feature #21457
• Required feature flags:
• Changes UI
• Includes DB Migration (follow approval process in SIP-59)
  • Migration is atomic, supports rollback & is backwards-compatible
  • Confirm DB migration upgrade and downgrade tested
  • Runtime estimates and downtime expectations provided
• Introduces new feature or API
• Removes existing feature or API

[Yann-J]

Hey FYI @benjaminrene I just noticed this PR, I think it's superseded by #21806 (which also includes other improvements such as more configurable probes and support for a flower UI).

It doesn't have some of the automatic Python config that your PR has... I think those are easy enough to pass separately as overrides, and I'm a bit cautious about forcing too many assumptions in the config - e.g. one may want to enabled websockets and set GLOBAL_ASYNC_QUERIES_TRANSPORT=ws in superset_config.py, but not use the Chart's deployment to run the websocket server... or craft their own GLOBAL_ASYNC_QUERIES_WEBSOCKET_URL that doesn't depend on the ingress settings (e.g. in my organization we don't use any chart's built-in ingresses because we maintain our own with a special security and approval process).

Unfortunately that PR was merged but the helm release process seems broken - #21963 will hopefully fix this.

I've also seen your PR #21379 which I'm also looking forward to! FYI you might be interested to look into #21954

[craig-rueda]

Closing in favor of #21806