From 85da563e4f914372d6a5ad21e8721601021aa33b Mon Sep 17 00:00:00 2001 From: Eduardo Baitello Date: Thu, 4 May 2017 14:19:52 -0300 Subject: [PATCH] Remove warnings about hook ordering guarantees With hook weights, execution ordering can be built. --- docs/charts_hooks.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/docs/charts_hooks.md b/docs/charts_hooks.md index 1fef8cca3..6ac9bc2b0 100644 --- a/docs/charts_hooks.md +++ b/docs/charts_hooks.md @@ -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: