Closed rteeling-evernorth closed 2 months ago
Hello! Thank you for filing an issue.
The maintainers will triage your issue shortly.
In the meantime, please take a look at the troubleshooting guide for bug reports.
If this is a feature request, please review our contribution guidelines.
I faced the same problem.
one or more objects failed to apply, reason: CustomResourceDefinition.apiextensions.k8s.io "autoscalingrunnersets.actions.github.com" is invalid: metadata.annotations: Too long: must have at most 262144 bytes. Retrying attempt #5 at 8:40PM.
@nikatar you can bandaid this for the moment by adding argocd.argoproj.io/sync-options: Replace=true
to that crd's annotations, but i want to get this there by default
Solution https://www.arthurkoziel.com/fixing-argocd-crd-too-long-error/
syncOptions:
- ServerSideApply=true
Yeah, that will work too
Hey @rteeling-evernorth,
I don't think we can do anything about it. CRDs are generated, and bundled together. You should just use server side apply. As long as there is a way to install CRDs and the controller, I don't think we should change this.
I think this issue can be closed
I am wondering if gha-runner-scale-set-controller chart could support additional annotation to CRDs like prometheus-operator-crds chart does 🤔
So user could easily add the server-side apply via helm values
Checks
Controller Version
0.7.0,0.8.2,0.9.0
Deployment Method
ArgoCD
Checks
To Reproduce
Describe the bug
The AutoscalingRunnerSet Custom Resource Definition is too large to be installed via ArgoCD.
Describe the expected behavior
The CRD should install with the rest of the helm chart
Additional Context
Controller Logs
Runner Pod Logs