Private GKE with restricted access to cluster master endpoints
A guide to private Google Kubernetes Engine cluster with different level of restricted access to cluster master endpoints
/opt/spinnaker/env/prod.envget sourced during runtime?
When udf is enabled, such as for aws, Spinnaker will inject server information into the user data during an execution of a deploy stage of an application. This information will end up in into
If we have an application called
armoryspinnaker-prod-nonpolling, it’ll look something like:
$ cat /etc/default/server-env CLOUD_ACCOUNT="aws-prod" CLOUD_ACCOUNT_TYPE="aws-prod" CLOUD_ENVIRONMENT="aws-prod" CLOUD_SERVER_GROUP="armoryspinnaker-prod-nonpolling-v984" CLOUD_CLUSTER="armoryspinnaker-prod-nonpolling" CLOUD_STACK="prod" CLOUD_DETAIL="nonpolling" EC2_REGION="us-west-2" LAUNCH_CONFIG="armoryspinnaker-prod-nonpolling-v984-0828050116281"