Store application secrets/settings for each deployment

Description

We need to store application parameters values in a deterministic place so that everything that is deployed can be destroyed and redeployed by any individual on the team. Additionally, this would ensure that we can create more generic deployment scripts that do not contain references to individual deployments.

Details

List of items that require storage (this is a non-exhaustive list at the moment):

• Helm Chart Values
• Kubernetes credentials for CI
• Kubernetes credentials for Engineers
  • In the future, we'd want to be more sophisticated in how we grant access to kubernetes. Ideally we'd have some kind of SSO setup so that management of access isn't a time consuming affair. For speed, we can keep the credentials for kubernetes in a centralized place. This is fine for now because the information stored on our current kubernetes clusters is not highly sensitive.

Current candidates for storage of these items

• AWS SSM Parameter storage
• Kubernetes Secrets
• HashiCorp Vault with Consul or Etcd

We will need to make sure that we determine what will work best for our use cases.

Considerations

• How will a given tool we use affect our ability to maintain infrastructure in a cloud provider like IBM Bluemix or AliCloud so that we can support SGX?

Acceptance Criteria (things that need to be done in order to complete this issue)

• Documentation on how to access/update. Must be linked in the employee onboarding doc
• Additional issues must be created detailing how we will trigger deployments based on changes to some configuration parameters