You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description: "The handler name. Handlers for the same hook within a single external component implementing Runtime Extensions must have different names",
Description: "Status code 200 indicates that the request has been processed successfully. Runtime Extension authors must use fields in the response like e.g. status and message to return processing outcomes.",
Summary: "Called before Cluster topology is created.",
185
-
Description: "This blocking hook is called after the Cluster is created by the user and immediately before all the objects which are part of a Cluster topology are going to be created.",
183
+
Tags: []string{"Lifecycle Hooks"},
184
+
Summary: "Cluster API Runtime will call this hook before a Cluster's topology is created",
185
+
Description: "Cluster API Runtime will call this hook after the Cluster is created by the user and immediately before "+
186
+
"all the objects which are part of a Cluster's topology are going to be created.\n"+
187
+
"\n"+
188
+
"Notes:\n"+
189
+
"- This hook will be called only for Clusters with a managed topology\n"+
190
+
"- The call's request contains the Cluster object\n"+
191
+
"- This is a blocking hook; Runtime Extension implementers can use this hook to execute\n"+
192
+
"tasks before the objects which are part of a Cluster's topology are created",
Summary: "Called before the Cluster is upgraded.",
197
-
Description: "This blocking hook is called after the Cluster object has been updated with a new spec.topology.version by the user, and immediately before the new version is propagated to the Control Plane.",
206
+
Tags: []string{"Lifecycle Hooks"},
207
+
Summary: "Cluster API Runtime will call this hook before the Cluster is upgraded",
208
+
Description: "Cluster API Runtime will call this hook after the Cluster object has been updated with a new spec.topology.version by the user, "+
209
+
"and immediately before the new version is propagated to the control plane.\n"+
210
+
"\n"+
211
+
"Notes:\n"+
212
+
"- This hook will be called only for Clusters with a managed topology\n"+
213
+
"- The call's request contains the Cluster object, the current Kubernetes version and the Kubernetes version we are upgrading to\n"+
214
+
"- This is a blocking hook; Runtime Extension implementers can use this hook to execute "+
215
+
"tasks before the new version is propagated to the control plane",
Summary: "Called after the Control Plane is upgraded.",
203
-
Description: "This blocking hook is called after the Control Plane has been upgraded to the version specified in spec.topology.version, and immediately before the new version is propagated to the MachineDeployments.",
219
+
Tags: []string{"Lifecycle Hooks"},
220
+
Summary: "Cluster API Runtime will call this hook after the control plane is upgraded",
221
+
Description: "Cluster API Runtime will call this hook after the a cluster's control plane has been upgraded to the version specified "+
222
+
"in spec.topology.version, and immediately before the new version is going to be propagated to the MachineDeployments. "+
223
+
"A control plane upgrade is completed when all the machines in the control plane have been upgraded.\n"+
224
+
"\n"+
225
+
"Notes:\n"+
226
+
"- This hook will be called only for Clusters with a managed topology\n"+
227
+
"- The call's request contains the Cluster object and the Kubernetes version we upgraded to\n"+
228
+
"- This is a blocking hook; Runtime Extension implementers can use this hook to execute "+
229
+
"tasks before the new version is propagated to the MachineDeployments",
Description: "This non-blocking hook is called after the Cluster, Control Plane and MachineDeployments have been upgraded to the version specified in spec.topology.version.",
233
+
Tags: []string{"Lifecycle Hooks"},
234
+
Summary: "Cluster API Runtime will call this hook after a Cluster is upgraded",
235
+
Description: "Cluster API Runtime will call this hook after a Cluster has been upgraded to the version specified "+
236
+
"in spec.topology.version. An upgrade is completed when all control plane and MachineDeployment's Machines have been upgraded.\n"+
237
+
"\n"+
238
+
"Notes:\n"+
239
+
"- This hook will be called only for Clusters with a managed topology\n"+
240
+
"- The call's request contains the Cluster object and the Kubernetes version we upgraded to \n"+
Description: "This blocking hook is called after the Cluster deletion has been triggered by the user, and immediately before objects of the Cluster are going to be deleted.",
245
+
Tags: []string{"Lifecycle Hooks"},
246
+
Summary: "Cluster API Runtime will call this hook before the Cluster is deleted",
247
+
Description: "Cluster API Runtime will call this hook after the Cluster deletion has been triggered by the user, "+
248
+
"and immediately before objects of the Cluster are going to be deleted.\n"+
249
+
"\n"+
250
+
"Notes:\n"+
251
+
"- This hook will be called only for Clusters with a managed topology\n"+
252
+
"- The call's request contains the Cluster object \n"+
253
+
"- This is a blocking hook; Runtime Extension implementers can use this hook to execute "+
254
+
"tasks before objects of the Cluster are deleted",
Summary: "GeneratePatches generates patches during topology reconciliation for the entire Cluster topology.",
180
-
Description: "A GeneratePatches call generates patches for the entire Cluster topology. Accordingly the request contains all templates, the global variables and the template-specific variables. The response contains generated patches.",
178
+
Tags: []string{"Topology Mutation Hook"},
179
+
Summary: "Cluster API Runtime will call this hook when a Cluster's topology is being computed",
180
+
Description: "Cluster API Runtime will call this hook when a Cluster's topology is being computed "+
181
+
"during each topology controller reconcile loop. More specifically, this hook will be called "+
182
+
"while computing patches to be applied on top of templates derived from the Cluster's ClusterClass.\n"+
183
+
"\n"+
184
+
"Notes:\n"+
185
+
"- The call's request contains all templates, the global variables and the template-specific variables required to compute patches\n"+
Summary: "ValidateTopology validates the Cluster topology after all patches have been applied.",
186
-
Description: "A ValidateTopology call validates the Cluster topology after all patches have been applied. The request contains all templates of the Cluster topology, the global variables and the template-specific variables. The response contains the result of the validation.",
190
+
Tags: []string{"Topology Mutation Hook"},
191
+
Summary: "Cluster API Runtime will call this hook after a Cluster's topology has been computed",
192
+
Description: "Cluster API Runtime will call this hook after a Cluster's topology has been computed "+
193
+
"during each topology controller reconcile loop. More specifically, this hook will be called "+
194
+
"after all patches have been applied to the templates derived from the Cluster's ClusterClass.\n"+
195
+
"\n"+
196
+
"Notes:\n"+
197
+
"- The call's request contains all templates, the global variables and the template-specific variables used while computing patches\n"+
198
+
"- The response must contain the result of the validation",
0 commit comments