Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in
Toggle navigation
H
helm3
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Commits
Issue Boards
Open sidebar
go
helm3
Commits
85da563e
Commit
85da563e
authored
May 04, 2017
by
Eduardo Baitello
Committed by
GitHub
May 04, 2017
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Remove warnings about hook ordering guarantees
With hook weights, execution ordering can be built.
parent
7ec64a4b
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
4 deletions
+2
-4
charts_hooks.md
docs/charts_hooks.md
+2
-4
No files found.
docs/charts_hooks.md
View file @
85da563e
...
...
@@ -155,12 +155,10 @@ One resource can implement multiple hooks:
Similarly, there is no limit to the number of different resources that
may implement a given hook. For example, one could declare both a secret
and a config map as a pre-install hook. It is important to keep in mind,
though, that there are no ordering guarantees about hooks.
and a config map as a pre-install hook.
When subcharts declare hooks, those are also evaluated. There is no way
for a top-level chart to disable the hooks declared by subcharts. And
again, there is no guaranteed ordering.
for a top-level chart to disable the hooks declared by subcharts.
It is also possible to define a weight for a hook which will help build a
deterministic executing order. Weights are defined using the following annotation:
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment