diff options
| author | Vincent Ambo <mail@tazj.in> | 2019-09-03T15·26+0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-09-03T15·26+0100 |
| commit | 628cec34331ea7ef94a71f562a0dc1f8d49e9ecf (patch) | |
| tree | fe6be2f9756627ac09c3207f876430921789baec /infra/kubernetes/nixery/config.yaml | |
| parent | be28462a8a29403128b39696cc632f70363efa6e (diff) | |
| parent | 283951388c96e871c9c4a835eee6594fc27e08c0 (diff) | |
Merge pull request #5 from tazjin/feat/cloud-kms-secrets r/80
Introduce secrets management via Google Cloud KMS
Diffstat (limited to 'infra/kubernetes/nixery/config.yaml')
| -rw-r--r-- | infra/kubernetes/nixery/config.yaml | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/infra/kubernetes/nixery/config.yaml b/infra/kubernetes/nixery/config.yaml index 1bd95536ac17..796e21a7273c 100644 --- a/infra/kubernetes/nixery/config.yaml +++ b/infra/kubernetes/nixery/config.yaml @@ -3,10 +3,6 @@ # The service via which Nixery is exposed has a private DNS entry # pointing to it, which makes it possible to resolve `nixery.local` # in-cluster without things getting nasty. -# -# The 'nixery-keys' secret was configured manually using a created -# service account key. This does not use metadata-based authentication -# due to the requirement for having an actual PEM-key to sign with. --- apiVersion: apps/v1 kind: Deployment |