Road to supported Installation - round 2

[cirocosta]

Hey,

At the moment, hush-house has pretty much feature parity with
wings, which was accomplished through our first iteration (see
#27).

In this second iteration, we plan to refine it more, aiming at two goals:

• making hush-house compelling for internal teams, and
• making it more maintainable.

To achieve those, here are some of the steps to get us there:

• Add panel descriptions - metrics: add panel descriptions #15
• Allow teams to leverage credential management
  • Verify if we can use k8s secrets as team credential management - hh: per-team credential management #40
    • if so, go with it
    • otherwise, evaluate Vault
• Deploy hush-house from main Concourse pipeline - hh: deploy from the main Concourse pipeline #28
• Alert based on SLIs - metrics: alert based on SLIs #39
• document k8s credential management - No documentation for Kubernetes credential manager docs#96
• Remove hush-house.concourse-ci.org domain from concourse-ci-org zone
  • 7735302
• Improve documentation about the terraform definitions
  • 3d1da46
• fix terraform deprecation warnings - terraform: address deprecation warnins #44
• get rid of AlertManager - metrics: get rid of alertmanager #43

---

Not included in this iteration, but soon to be:

• Allow the provisioning of team-specific workers
  • some teams might have the desired of having their own team-specific workers;
    what if we could just manage their workers for them?
• Continuously deploy metrics
• Continuously terraform apply
  • whenever the terraform scripts are updated.

Thanks!