I recently upgraded our Argo Kustomize environment and migrated all of our Ksops files to use the new executable binary. Functionality is the same, but I am seeing a significant increase in the amount of CPU the CMP sidecar container takes for every sync. Sidecar containers will use upwards of 50 CPUs if not bound with limits.
Mind you we have a large argo cluster with 300+ apps and hundreds of Ksops generators. Is there a way to improve performance of Ksops in Argo for high application clusters. Perhaps processing an entire generated kustomize build of Decryptions in the same call to the binary instead of individual calls?
Previous iteration with kustomize plugin baked in did not have these resource issues.
I recently upgraded our Argo Kustomize environment and migrated all of our Ksops files to use the new executable binary. Functionality is the same, but I am seeing a significant increase in the amount of CPU the CMP sidecar container takes for every sync. Sidecar containers will use upwards of 50 CPUs if not bound with limits.
Mind you we have a large argo cluster with 300+ apps and hundreds of Ksops generators. Is there a way to improve performance of Ksops in Argo for high application clusters. Perhaps processing an entire generated kustomize build of Decryptions in the same call to the binary instead of individual calls?
Previous iteration with kustomize plugin baked in did not have these resource issues.