cf-api-kpack-watcher
deployment usesadmin_client_secret
non secretcloud-controller-ng-yaml
configmap consumes postgres passwordcloud-controller-ng-yaml
is just a huge yaml dump. can this be broken down into key-value config mapcloud-controller-ng-yaml
bunch of other secrets that are unused but still in the configmapcloud-controller-ng-yaml
configmap consumes blobstore passwordcloud-controller-ng-yaml
configmap consumes uaa password as plain textcloud_controller_username_lookup_client_secret
eirini
config-map consumes secret nameapp-registry-credentials
as config yaml (instead of secret).- Will
kapp
rotate CRDs that reference secret names e.g.Gateway.istio-ingressgateway.credentialName
uaa-config
config map consumesencryption.encryption_keys.passphrase
uaa-config
config map consumes certs directlyserviceProviderKey
,serviceProviderKeyPassword
,serviceProviderCertificate
uaa-config
config map consumesLOGIN_SECRET: uaa-login-secret
instead of mounted pathuaa-config
config map consumes client secrets as plain textcf-k8s-networking
,cloud_controller_username_lookup
,capi_kpack_watcher
uaa-config
config map consumescf_admin_password
from values.yml as plain text- cf-for-k8s is using the same uaa admin passwords for components. instead, it should use separate passwords for each client.
Last active
June 11, 2020 16:42
-
-
Save Syerram/e00a2d70337b0ba7d6853c7606a2f735 to your computer and use it in GitHub Desktop.
Audit of final cf-for-k8s deployment
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment