Apache Superset – unable to change certificate

[mb8z]

Category:

Kubernetes apps

Type:

• Bug (?)
• Feature Request
• Process

---

An app deployed using Superset from the marketplace.
Among other things, it created a load balancer, static IP address, and a self-managed certificate. We wanted to update the certificate, and here are the steps we followed:

1. Create a Google-managed certificate (let's call it superset)
2. Update load balancer's frontend so the HTTPS has the superset certificate assigned
   It worked for a couple of minutes, but then the certificate is changed back to the self-managed one that was created by default.

Is this an expected behaviour, or a possible bug?
If the former is true – what'd be the correct way to change the certificate?