pixie
pixie copied to clipboard
Automate updating the self-hosted artifact tracker's vizier, operator and cli version
I recently followed the deployment steps for deploying a self hosted Pixie cloud. Through this process, I realized that results in a stale vizier being deployed (0.12.12). This is because the versions are hardcoded here when they are normally overridden for other environments. Since we have automation for updating our README during releases, it would be handy to have this automation or another workflow update this deployment version as well.
This is mainly needed for the vizier releases since OLM (or some other mechanism) upgrades the operator during deployment.