-
Notifications
You must be signed in to change notification settings - Fork 3
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
Helm v3.6.3 for werf #99
Open
distorhead
wants to merge
32
commits into
release-3.6
Choose a base branch
from
HelmV3.6.3ForWerf
base: release-3.6
Could not load branches
Branch not found: {{ refName }}
Could not load tags
Nothing to show
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
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
- change "main" package name to "helm_v3"; - make all top-level helm commands constructors exportable for helm_v3 package.
- Added helm cmd creation options to redefine: - postrenderer; - create-namespace, wait, atomic flags; - value-opts.
…erfChart extensions, added custom loader options support - Patched loader package to accept ChartExtender-interfaced object and factory to create extender for subcharts using loader.GlobalLoadOptions structure. - Added support for custom chart files loader, chart locator and values-related files reader using loader.LoadOptions. - Needed to implement determinism mode in the werf: werf/werf#2874. - ChartExtender allows adding extra templates and values, generation of Chart.yaml. - Exported 'helm chart' subcommand.
…in pending install/upgrade/rollback status
…he end of the template Refs werf/werf#2304
errPending on upgrade could occur when some deploy has been interrupted by a signal. In this case helm leave release in inconsistent state which could not be healed by automatical redeploy. Werf uses own distributed release locking by release name using Kubernetes configmap annotations to synchronize multiple deploy processes. Werf implementation supports interrupting of werf-deploy process by some signal. helm#8987
Also added ability to export chart into exactly specified directory (helm uses DESTINATION/CHART_NAME by default).
…or DOCKER_CONFIG variable) for 'helm chart *' commands
- Put all loader function callbacks into extender. - Fix subchart loading. - Refactor chart.Extender interface functions itself.
…-is-upgrade options
…ce getter to use overriden namespace if set
Allow case when namespace already exists in the cluster and user does not have a permission to create namespaces. `helm install --create-namespace` would not try to create namespace in such case. This change makes `--create-namespace` flag behaviour moreidempotent.
…en installed successfully yet .Release.IsInstall will be true until we successfully installed release.
Signed-off-by: Ilya Lesikov <[email protected]>
feat: implement export-values
…reached on initial installation Fixed old releases rotation procedure to not require a deployed release to exists. An error will arise when there are no successfully deployed release yet, but releases history limit has been reached. In such situation helm will refuse to upgrade release anymore with "... has no deployed releases" error. Furthermore, release rotation procedure already expecting lastDeployedRelease to be either nil, or not nil. So it is assumed that deployed release may exist or may not and these both outcomes were already expected as a valid situation rather than a failure.
…_limit_hit_for_werf fix: "... has no deployed releases" error when release history limit reached on initial installation
feat(helm for werf): support post-renderer chaining
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.
No description provided.