Deprecate the field of managedclusteraddon.spec.installNamespace

[zhujian7]

Now we can use the managedclusteraddon.spec.installNamespace field to set which namespace the addon agent will be deployed on the managed clusters. But there are some disadvantages, like using managedclusteraddon.spec.installNamespace, the value is determined by the addon deployer, not the developer, so for example, if you want to use the addon's installStrategy feature(the ManagedClusterAddon will be created automatically), the value cannot be configured and can only be the default value open-cluster-management-agent-addon

So we are exploring a more general way to set up this install namespace; In OCM, when we develop an OCM addon, we only need to implement the AgentAddon interface:

• we can use the Manifests function to define what resources we want to deploy into the managed cluster, there might be some namespace scoped resources, like deployments, let it call the namespace manifests-namespace;
• if the addon agent also wants to access the hub cluster, we can use the Registration to configure how to access hub, and a config func AgentInstallNamespace is provided to config the registration credential namespace, so when the addon is deployed, there will be a hub kubeconfig secret generated in this namespace, and the deployments can use this secret to access the hub cluster. let it call this namespace registration-namespace;

The manifests-namespace and the registration-namespace can be totally decided by the addon developer, for example, in the above two functions you can write code to read the namespace from the API addondeploymentconfig.spec.agentInstallNamespace or make it a fixed value like test-ns or any other way. No matter which way, they should be the same value. And the value will be shown in the field managedclusteraddon.status.namespace.
With this, the managedclusteraddon.spec.installNamespace is not required, using the installStrategy feature will not always deploy the agent into the open-cluster-management-agent-addon namespace as well.

[github-actions]

This issue is stale because it has been open for 120 days with no activity. After 14 days of inactivity, it will be closed. Remove the stable label to prevent this issue from being closed.

[github-actions]

This issue is stale because it has been open for 120 days with no activity. After 14 days of inactivity, it will be closed. Remove the stable label to prevent this issue from being closed.

[github-actions]

This issue is stale because it has been open for 120 days with no activity. After 14 days of inactivity, it will be closed. Remove the stable label to prevent this issue from being closed.