You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/upgrading_to_v2.0.md
+9-4Lines changed: 9 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -44,12 +44,17 @@ module "kubernetes_engine" {
44
44
45
45
### Enabling Kubernetes Basic Authentication
46
46
47
-
Starting with GKE v1.12, clusters will have Basic Authentication and
48
-
client certificate issuance disabled by default. In previous versions
49
-
of *kubernetes-engine*, Basic Authentication was enabled and configured with the username `"admin"` and an automatically generated password. Basic Authentication is now disabled by default and requires credentials to be provided to remain enabled.
47
+
Starting with GKE v1.12, clusters will by default disable the Basic
48
+
Authentication method of authenticating. In previous versions of
49
+
*kubernetes-engine*, Basic Authentication was enabled and configured
50
+
with the username `"admin"` and an automatically generated password if
51
+
the managed version of Kubernetes was less than v1.12.
52
+
Basic Authentication is now requires credentials to be provided to be
53
+
enabled.
50
54
51
55
Using Basic Authentication causes Terraform to store the credentials in
52
-
a state file. It is important to use a Terraform Backend which supports encryption at rest, like the [GCS Backend][gcs-backend]. The
56
+
a state file. It is important to use a Terraform Backend which supports
57
+
encryption at rest, like the [GCS Backend][gcs-backend]. The
53
58
[Sensitive Data in State article][sensitive-data] provides more context
54
59
and recommendations on how to handle scenarios like this.
0 commit comments