configmap crds-configmap should conditional enable by setupEnabled flog #3896
Description
Describe the bug A clear and concise description of what the bug is.
when upgrade to 4.12.0, there is error related to crds-configmap, (not using serverside apply causing metadata too long problem)
ConfigMap "sumologic-collector-su-setup-crds" is invalid: metadata.annotations: Too long: must have at most 262144 bytes -Additional Info: This error usually means that you are trying to add a large resource on client side. Consider using Server-side apply or syncing with replace enabled. Note: Syncing with Replace enabled is potentially destructive as it may cause resource deletion and re-creation.
i checked the new helm config, this crds-configmap seems only used in setup job.
we disabled setup job, i think this configmap can be conditional enabled by the same flag.
see this file https://github.com/SumoLogic/sumologic-kubernetes-collection/blob/v4.12.0/deploy/helm/sumologic/templates/setup/crds-configmap.yaml
similar approach to this file
Logs Logs which can be helpful in investigating the issue.
Command used to install/upgrade Collection Direct command which you used to install/upgrade collection.
Configuration Configuration used for Collection e.g. user-values.yaml for helm.
To Reproduce Steps to reproduce the behavior.
Expected behavior A clear and concise description of what you expected to happen.
Environment (please complete the following information):
- Collection version (e.g.
helm ls -n sumologic): - Kubernetes version (e.g.
kubectl version): - Cloud provider:
- Others:
Anything else do we need to know Add any other context about the problem here, e.g. issue happens only occasionally.