-
Notifications
You must be signed in to change notification settings - Fork 65
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
Deploy common set of support components for each cluster we operate #388
Comments
Another question here is what to do about Grafana. Should we do one per cluster? Or have a centralized one? |
Who is going to the consumers of Grafana? If this is just for us, I would vote for a centralized one, if that is easily achievable. |
- Set up cert-manager explicitly, since it can not be set up as a dependent chart of our 'support' chart. - 'support' chart deploys prometheus, grafana and nginx-ingress in a standard configuration. - Allow per-cluster overrides with config under support/clusters. - Add a script that will provision the support components. Ref 2i2c-org#388
- Set up cert-manager explicitly, since it can not be set up as a dependent chart of our 'support' chart. - 'support' chart deploys prometheus, grafana and nginx-ingress in a standard configuration. - Allow per-cluster overrides with config under support/clusters. - Add a script that will provision the support components. Ref 2i2c-org#388
- Set up cert-manager explicitly, since it can not be set up as a dependent chart of our 'support' chart. - 'support' chart deploys prometheus, grafana and nginx-ingress in a standard configuration. - Allow per-cluster overrides with config under support/clusters. - Add a script that will provision the support components. Ref 2i2c-org#388
- Set up cert-manager explicitly, since it can not be set up as a dependent chart of our 'support' chart. - 'support' chart deploys prometheus, grafana and nginx-ingress in a standard configuration. - Allow per-cluster overrides with config under support/clusters. - Add a script that will provision the support components. Ref 2i2c-org#388
- Set up cert-manager explicitly, since it can not be set up as a dependent chart of our 'support' chart. - 'support' chart deploys prometheus, grafana and nginx-ingress in a standard configuration. - Allow per-cluster overrides with config under support/clusters. - Add a script that will provision the support components. Ref 2i2c-org#388
- Set up cert-manager explicitly, since it can not be set up as a dependent chart of our 'support' chart. - 'support' chart deploys prometheus, grafana and nginx-ingress in a standard configuration. - Allow per-cluster overrides with config under support/clusters. - Add a script that will provision the support components. Ref 2i2c-org#388
This one feels like an important "standardize and professionalize our deployments infrastructure" issue, so adding to the backlog |
This is done now! |
Background
All clusters we operate should have a 'baseline' set of supporting services that should be deployed uniformly. This helps us administer them in one go.
Expected timeline
We already have this deployed for two of our clusters, from
support/
in this repo. We should automatically make sure this is deployed on all our clusters.Steps to complete this goal
support/
chart is up to datedeploy-support
script that'll deploy the support components for a given clusterThe text was updated successfully, but these errors were encountered: