Rastislav Wagner

Improve watch on CTI controller only for argocd resources

1

Currently every HostedCluster/ClusterDeployment is being watched. We should limit this to resources created by argocd (label `app.kubernetes.io/instance`)

Allow making specific day2 setup steps optional

1

Currently any day2 in CT is always executed. We should allow making some of the day2 optional and CTI creator can opt-in only for required ones

operator currently does not have a logic to detect errors on ClusterDeployment installation

The operator should not override changes to cost field See also https://github.com/stolostron/cluster-templates-operator/issues/97

Currently access to admin/kubeconfig secrets are added to users only when cluster is created. There is no mechanism to keep the access up to date. We should have a separate...

The current set of APIs require to provide a reference to argocd secret. If user uses CLI and public repo, there is no need to create argocd secret

We should allow making a dynamic updates to cost of the template based on some value in helm chart. The value would usually represent a number of nodes. The value...