When registration config of an add-on changes frequently, for example 1 time per second, registration-agent will create a new CSR based on the new config on hub cluster. The number of CSRs may increase quickly. Since the registration-agent caches all those CSRs, that may cause the memory usage keep increasing. A mechanism is needed to limit the rate of CSR creation for each addon.
In response to [this](https://github.com/open-cluster-management-io/registration/issues/219#issuecomment-1308859952):
>we have added a limit on csr that can be created.
>
>/close
Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
When registration config of an add-on changes frequently, for example 1 time per second, registration-agent will create a new CSR based on the new config on hub cluster. The number of CSRs may increase quickly. Since the registration-agent caches all those CSRs, that may cause the memory usage keep increasing. A mechanism is needed to limit the rate of CSR creation for each addon.