The superset and superset-next need to be registered in the Puppet service catalog and point to the DSE k8s ingress discovery CNAME record.
Description
Description
Details
Details
Related Changes in Gerrit:
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | brouberol | T353782 Decommission an-tool1010 | |||
| Resolved | brouberol | T347710 Migrate the Analytics Superset instances to our DSE Kubernetes cluster | |||
| Resolved | brouberol | T356483 [superset k8s] Add entries to the puppet service catalog |
Event Timeline
Comment Actions
Change 997857 had a related patch set uploaded (by Brouberol; author: Brouberol):
[operations/puppet@production] service: register superset and superset-next under ingress
Comment Actions
Change 997857 merged by Brouberol:
[operations/puppet@production] service: register superset and superset-next under ingress
Comment Actions
Change 1002362 had a related patch set uploaded (by Brouberol; author: Brouberol):
[operations/puppet@production] superset: set puppet service states to production
Comment Actions
Change 1002362 merged by Brouberol:
[operations/puppet@production] superset: set puppet service states to production