harborcluster registryctl resources config is not used by registryctl container

[karaguo]

If you are reporting a problem, please make sure the following information are provided:

Expected behavior and actual behavior: A clear and concise description of what you expected to happen and what's the actual behavior. If applicable, add screenshots to help explain your problem.

Expected: The resource config set in harborcluster CR in spec.registryctl.resources is expected to control the real resource configuration in registry deployment registryctl container.

Actual: The resource config in spec.registryctl.resources such as cpu resource request doesn't take effect when the values are different from the ones in spec.registry.resources

Steps to reproduce the problem: Please provide the steps to reproduce this problem.

• at harbrocluster CR, set resource configuration differently between registry and registryctl

  registry:
  resources:
  requests:
    cpu: 1000m
  registryctl:
  resources:
  requests:
    cpu: 50m

• after reconciling, both container registry and registryctl in registry deployment both follow the configuration set for registry

Versions: Please specify the versions of following systems.

harbor operator version: 1.2.0 harbor version: 2.6.2 kubernetes version: 1.24.2

[karaguo]

It is because all containers including registry and registryctl in deployment registry are populated with the resource configuration values provided by registry component spec, as code and code. The configuration in registryctl component spec is not used