one component exception will affect the deployment process of multiple components

[xiqiu618]

Expected behavior (what you expected to happen):
The management of multiple components is decoupled from each other and has complementary effectsActual behavior (what actually happened):
one component exception will affect the deployment process of multiple components

Environment:

• Addon-operator version: v1.0.0-rc.1
• Helm version: v3
• Kubernetes version: 1.16.9
• Installation type (kubectl apply, helm chart, etc.): helm chart

Anything else we should know?:

addon-operator/pkg/module_manager/module_manager.go

Lines 751 to 755 in 64c5a1a

	for _, moduleName := range enabledModules {
	if err = mm.RegisterModuleHooks(mm.allModulesByName[moduleName], logLabels); err != nil {
	return nil, err
	}
	}

Additional information for debugging (if necessary):

Hook script

Logs

[diafour]

Hello! Sorry for the long delay.
You quote a code related to configuring hooks at module start. It’s easy to catch these errors with simple tests before releasing.
We consider that the act of bundling hooks and modules in one image is a release of the solution. If there is an error in configuring just one hook at start, the solution might not work at all, so it is crucial to stop and wait until the fixed image arrives.

Can you get more details on your components and describe the reason to tolerate configuring errors?