Skip to content
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

Closed
3 tasks done
yuvipanda opened this issue May 9, 2021 · 4 comments
Closed
3 tasks done

Comments

@yuvipanda
Copy link
Member

yuvipanda commented May 9, 2021

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.

Chart Purpose
Prometheus Collect metrics from nodes, k8s, hub
nginx-ingress Provide single external endpoint to get traffic into the cluster
cert-manager Setup HTTPS via Let's Encrypt for all our services

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

  • Make sure our support/ chart is up to date
  • Write a deploy-support script that'll deploy the support components for a given cluster
  • Auto deploy it for each cluster
@yuvipanda
Copy link
Member Author

Another question here is what to do about Grafana. Should we do one per cluster? Or have a centralized one?

@damianavila
Copy link
Contributor

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.

yuvipanda added a commit to yuvipanda/pilot-hubs that referenced this issue Jun 8, 2021
- 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
yuvipanda added a commit to yuvipanda/pilot-hubs that referenced this issue Jun 8, 2021
- 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
yuvipanda added a commit to yuvipanda/pilot-hubs that referenced this issue Jun 9, 2021
- 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
yuvipanda added a commit to yuvipanda/pilot-hubs that referenced this issue Jun 10, 2021
- 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
yuvipanda added a commit to yuvipanda/pilot-hubs that referenced this issue Jun 16, 2021
- 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
yuvipanda added a commit to yuvipanda/pilot-hubs that referenced this issue Jun 16, 2021
- 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
@choldgraf
Copy link
Member

This one feels like an important "standardize and professionalize our deployments infrastructure" issue, so adding to the backlog

@yuvipanda
Copy link
Member Author

This is done now!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants