account for move of repo from vmware-tanzu to vmware on GitHub #2526
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.
Change all
vmware-tanzutovmwareas it relates to GitHub in the source and docs.This changes a lot of documentation and web site links.
Most importantly, it changes the default value for the location of the container image in the ytt templates for the Concierge and Supervisor (in the
values.yamlfiles). In the upcoming v0.40.0 release, we cannot push to our old container repository atghcr.io/vmware-tanzu/pinniped/pinniped-serveranymore because the git repository was moved to a new GitHub org (trying to push returns an error saying that it was moved permanently). Therefore, we will need to push the container image toghcr.io/vmware/pinniped/pinniped-serverinstead. This PR updates the ytt templates to make this the new default location for Concierge and Supervisor deployments.This also accounts for the move of
vmware-tanzu/carveltocarvel-dev/carvelin our docs and scripts, although that technically happened a long time ago.Release note: