-
Notifications
You must be signed in to change notification settings - Fork 488
Automate updating the self-hosted artifact tracker's vizier, operator and cli version #2076
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
Merged
ddelnano
merged 5 commits into
pixie-io:main
from
ddelnano:ddelnano/update-artifact-versions-on-release
Jan 16, 2025
Merged
Automate updating the self-hosted artifact tracker's vizier, operator and cli version #2076
ddelnano
merged 5 commits into
pixie-io:main
from
ddelnano:ddelnano/update-artifact-versions-on-release
Jan 16, 2025
Conversation
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
Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
e27e432 to
2235a0e
Compare
Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
2235a0e to
f7e42b1
Compare
vihangm
reviewed
Jan 16, 2025
Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
vihangm
approved these changes
Jan 16, 2025
Member
vihangm
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left you a minor note about the comment rule.
Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
ddelnano
added a commit
to ddelnano/pixie
that referenced
this pull request
Aug 6, 2025
… and cli version (pixie-io#2076) Summary: Automate updating the self-hosted artifact tracker's vizier, operator and cli version This was previously done manually and from talking with end users in Slack people are often running very old Vizier versions as a result. Let's include updating this file in the same automation that updates the README on releases. Relevant Issues: Closes pixie-io#1907 Type of change: /kind cleanup Test Plan: Tested the script with the various release types ``` $ ./ci/update_files_with_release_versions.sh vizier 0.14.15 '<!--vizier-latest-release' $ git diff k8s diff --git a/k8s/cloud/public/base/artifact_tracker_versions.yaml b/k8s/cloud/public/base/artifact_tracker_versions.yaml index 69fbcaf..1aa87c7e5 100644 --- a/k8s/cloud/public/base/artifact_tracker_versions.yaml +++ b/k8s/cloud/public/base/artifact_tracker_versions.yaml @@ -12,7 +12,7 @@ spec: - name: artifact-tracker-server env: - name: PL_VIZIER_VERSION - value: "0.14.14" + value: "0.14.15" - name: PL_CLI_VERSION value: "0.8.5" - name: PL_OPERATOR_VERSION # Remove changes $ git checkout -- k8s $ ./ci/update_files_with_release_versions.sh cli 0.14.15 '<!--cli-latest-release' ddelnano@dev-vm:~/code/pixie-extra (ddelnano/update-artifact-versions-on-release) $ git diff k8s/ diff --git a/k8s/cloud/public/base/artifact_tracker_versions.yaml b/k8s/cloud/public/base/artifact_tracker_versions.yaml index 69fbcaf..e0b50ee83 100644 --- a/k8s/cloud/public/base/artifact_tracker_versions.yaml +++ b/k8s/cloud/public/base/artifact_tracker_versions.yaml @@ -14,6 +14,6 @@ spec: - name: PL_VIZIER_VERSION value: "0.14.14" - name: PL_CLI_VERSION - value: "0.8.5" + value: "0.14.15" - name: PL_OPERATOR_VERSION value: "0.1.7" # Remove changes $ git checkout -- k8s $ ./ci/update_files_with_release_versions.sh operator 0.14.15 '<!--operator-latest-release' $ git diff k8s diff --git a/k8s/cloud/public/base/artifact_tracker_versions.yaml b/k8s/cloud/public/base/artifact_tracker_versions.yaml index 69fbcaf..6466f8a4b 100644 --- a/k8s/cloud/public/base/artifact_tracker_versions.yaml +++ b/k8s/cloud/public/base/artifact_tracker_versions.yaml @@ -16,4 +16,4 @@ spec: - name: PL_CLI_VERSION value: "0.8.5" - name: PL_OPERATOR_VERSION - value: "0.1.7" + value: "0.14.15" # Remove changes and verify cloud release results in no changes $ git checkout -- k8s/ $ ./ci/update_files_with_release_versions.sh cloud 0.14.15 '<!--cloud-latest-release' $ git diff k8s/ ``` Changelog Message: Add automation to ensure self-hosted Cloud deployments receive updated vizier, operator and cli version manifests --------- Signed-off-by: Dom Del Nano <ddelnano@gmail.com> GitOrigin-RevId: 1634b86
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: Automate updating the self-hosted artifact tracker's vizier, operator and cli version
This was previously done manually and from talking with end users in Slack people are often running very old Vizier versions as a result. Let's include updating this file in the same automation that updates the README on releases.
Relevant Issues: Closes #1907
Type of change: /kind cleanup
Test Plan: Tested the script with the various release types
Changelog Message: Add automation to ensure self-hosted Cloud deployments receive updated vizier, operator and cli version manifests