Deploy self hosted pixie cloud on domain other than `dev.withpixie.dev` and use actual certificate (accessible from multiple system without installing the certificate on all the systems) and move away with dns updater.

[c3-pranjaysagar]

My use case.

Want to deploy the self managed pixie on the cluster for cluster monitoring and the Live ui to be accessible to all the team members.

Current scenario based on installation steps

• mkcert creates a locally trusted certificate.
• Predefined domain - dev.withpixie.dev
• dns updater updates the host file in the system for the sac ips
• If any other member needs to access the live ui, the local certificate has to be shared and installed in the team members system.

Scenario We want

• use proper certificate to create the tls, that is used by the services
• Use our domain to host pixie
• No need to keep running the dns updater
• No need of sharing the certificate for other members to access the live ui (If we are using proper certificate fort ls, that issue will be resolved.)