Fix adapative_export image name in vizier releases#30
Merged
Conversation
Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
ddelnano
temporarily deployed
to
pr-actions-approval
GitHub Actions
Inactive
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary: Fix adapative_export image name in vizier releases
Running px deploy with k8sstormcenter Pixie releases fails because the Vizier manifests reference an invalid image for adaptive_export (missing the
ghcr.io/k8sstormcenterprefix). This fixes the image name and deploys it with 0 replicas to get a working vizier on initialpx deploy.The replica change will be reverted once we have the system working end to end on a fresh deployment
Relevant Issues: N/A
Type of change: /kind bugfix
Test Plan: Inspected vizier manifests from a broken release