Following the marketplace tutorial, the current GKE version 1.18.16 in setup_properties.sh fails with errors around the inability to enable basic auth.
Basic auth removal
This PR removes --username "admin" (basic auth).
Q: Does disabling basic auth impact any extended operations beyond setup?
I skimmed the docs and didn't see basic auth references and gcloud captures GKE credentials.
Version tweaks
Looking at the history of setup.sh, most of the commits are GKE_VERSION house keeping.
The PR also swaps out a specific cluster version with a release channel variable GKE_RELEASE_CHANNEL. Also, GKE_CLUSTER_VERSION is no longer necessary.
I understand there's value to pinning a specific version in production clusters. However, it's safe to assume the setup script will only run the first time. As folks adopt "day-2" operations, an upgrade plan will follow.
Following the marketplace tutorial, the current GKE version
1.18.16
insetup_properties.sh
fails with errors around the inability to enable basic auth.Basic auth removal
This PR removes
--username "admin"
(basic auth).Q: Does disabling basic auth impact any extended operations beyond setup?
I skimmed the docs and didn't see basic auth references and
gcloud
captures GKE credentials.Version tweaks
Looking at the history of
setup.sh
, most of the commits are GKE_VERSION house keeping.The PR also swaps out a specific cluster version with a release channel variable
GKE_RELEASE_CHANNEL
. Also,GKE_CLUSTER_VERSION
is no longer necessary.I understand there's value to pinning a specific version in production clusters. However, it's safe to assume the setup script will only run the first time. As folks adopt "day-2" operations, an upgrade plan will follow.