-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge crab rest, log pipeline, and serviceaccount manifests together in single helm chart #8677
Comments
@belforte @aspiringmind-code I would like to hear your comment about a new
Here is the full directory structure:
What do you think? |
You can view these files in my fork here: https://github.com/novicecpp/CMSKubernetes/tree/crab_canary/helm/crabserver |
I like it |
This is done, merge to CMSKubernetes, and documents. |
Sorry. I need to keep this open because it does not deploy on production yet. test (at least test12) and preprod are now use new helm chart. |
I would like to commit the new serviceaccount for CI to CMSKuberentes but I do not know where to put it. Also, the crab's logstash manifests is in different place.
After discuss with @arooshap, she suggested to put everything together in single helm chart,
helm/crabserver
, and use value flags to render specific resources groups.We have 3 resource group:
For example, the
values-testX.yaml
only for rendercrabserver
-related manifests:To render log pipeline and CI serviceaccount (e.g.,
values-admin.yaml
), the value file will look like this:This will be easier for cluster admin to maintain all our services.
And for us, we only need to focus on modifying the
crabserver
resourec group, e.g., adding a new canary deployment.The text was updated successfully, but these errors were encountered: