-
Notifications
You must be signed in to change notification settings - Fork 0
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
Release 2.6 #29
Open
wikiq
wants to merge
15
commits into
main
Choose a base branch
from
release-2.6
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Release 2.6 #29
Conversation
This file contains 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
Use the current kube config namespace by default if --namespace is not specified. This makes 'helm upgrade --install' and 'helm install' handle namespaces the same way.
(cherry picked from commit f278675)
When release upgrade fails, updatedRelease is already created in a storage by *ReleaseServer.UpdateRelease, therefore we should be updating it's status, not creating it again. (cherry picked from commit 38c3f58)
…rrors during tests (cherry picked from commit ff5acc9)
The alias functionality only works when a hardcoded version is used. Any use of semver logic causes unexpected behavior. I use version.IsCompatibleRange to check the dependency version. Closes #2794 (cherry picked from commit 0440b54)
… kind name Adds additional manifest sorting logic so that different unknown kinds are sorted alphabetically so that manifest order is more deterministic. (cherry picked from commit ed24b31)
Helm dependency update --verify should fail when verification fails. Closes #2717 (cherry picked from commit d84b707)
(cherry picked from commit c3f9120)
When running glide update there are errors due to pinned versions in the glide.yaml file mixed with getting a more recent version of kubernetes. client-go needs a newer version of go-autorest. Note, go-autorest is pinned to v8.0.0 rather than the latest release of v8.4.0 because kubernetes is pinned to v8.0.0. (cherry picked from commit b69d6ce)
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.
What this PR does / why we need it:
Special notes for your reviewer:
If applicable: