Skip to content

Commit

Permalink
docs(design): explain why we use secrets instead of CRDs
Browse files Browse the repository at this point in the history
  • Loading branch information
technosophos committed Nov 22, 2017
1 parent acb21eb commit bee54fa
Showing 1 changed file with 4 additions and 1 deletion.
5 changes: 4 additions & 1 deletion docs/topics/design.md
Expand Up @@ -198,7 +198,10 @@ and jobs. The API server is typically fronted by a Service or Ingress.
- Go was selected because it provides the most mature Kubernetes APIs.
- At various points, we explored using TPRs and later CRDs. But the feature sets
and stability of these two facilities never reached a satisfactorily stable
point. So we use secrets for configuration data.
point. So we use secrets for configuration data. Secrets have the following benefits:
- They are mountable via the volume system, a feature we use frequently
- They can be injected as environment variables
- They benefit from Kubernetes improvements to secret storage
- JavaScript was selected because of it's high score on just about all language
usage analyses.
- Node.js was selected because of its robust ecosystem
Expand Down

0 comments on commit bee54fa

Please sign in to comment.