Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automate updating the self-hosted artifact tracker's vizier, operator and cli version #1907

Open
ddelnano opened this issue May 16, 2024 · 0 comments
Labels
area/deployment Issues replated to deployments

Comments

@ddelnano
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/deployment Issues replated to deployments
Projects
None yet
Development

No branches or pull requests

1 participant