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: website/docs/index.html.markdown
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,13 +53,13 @@ There are generally two ways to configure the Kubernetes provider.
53
53
### File config
54
54
55
55
The provider always first tries to load **a config file** from a given
56
-
(or default) location. Depending on whether you have current context set
56
+
(or default) location. Depending on whether you have a current context set
57
57
this _may_ require `config_context_auth_info` and/or `config_context_cluster`
58
58
and/or `config_context`.
59
59
60
60
#### Setting default config context
61
61
62
-
Here's an example for how to set default context and avoid all provider configuration:
62
+
Here's an example of how to set default context and avoid all provider configuration:
63
63
64
64
```
65
65
kubectl config set-context default-system \
@@ -75,8 +75,8 @@ Read [more about `kubectl` in the official docs](https://kubernetes.io/docs/user
75
75
76
76
If no other configuration is specified, and when it detects it is running in a kubernetes pod,
77
77
the provider will try to use the service account token from the `/var/run/secrets/kubernetes.io/serviceaccount/token` path.
78
-
Detection of in-cluster execution is based on the sole availability both of the `KUBERNETES_SERVICE_HOST` and `KUBERNETES_SERVICE_PORT` environment variables,
79
-
with nonempty values.
78
+
Detection of in-cluster execution is based on the sole availability of both of the `KUBERNETES_SERVICE_HOST` and `KUBERNETES_SERVICE_PORT` environment variables,
79
+
with non-empty values.
80
80
81
81
```hcl
82
82
provider "kubernetes" {
@@ -117,7 +117,7 @@ provider "kubernetes" {
117
117
118
118
119
119
120
-
~> If you have **both** valid configuration in a config file and static configuration, the static one is used as override.
120
+
~> If you have **both** valid configurations in a config file and static configuration, the static one is used as an override.
121
121
i.e. any static field will override its counterpart loaded from the config.
122
122
123
123
## Argument Reference
@@ -127,7 +127,7 @@ The following arguments are supported:
127
127
*`host` - (Optional) The hostname (in form of URI) of Kubernetes master. Can be sourced from `KUBE_HOST`.
128
128
*`username` - (Optional) The username to use for HTTP basic authentication when accessing the Kubernetes master endpoint. Can be sourced from `KUBE_USER`.
129
129
*`password` - (Optional) The password to use for HTTP basic authentication when accessing the Kubernetes master endpoint. Can be sourced from `KUBE_PASSWORD`.
130
-
*`insecure` - (Optional) Whether server should be accessed without verifying the TLS certificate. Can be sourced from `KUBE_INSECURE`. Defaults to `false`.
130
+
*`insecure` - (Optional) Whether the server should be accessed without verifying the TLS certificate. Can be sourced from `KUBE_INSECURE`. Defaults to `false`.
131
131
*`client_certificate` - (Optional) PEM-encoded client certificate for TLS authentication. Can be sourced from `KUBE_CLIENT_CERT_DATA`.
132
132
*`client_key` - (Optional) PEM-encoded client certificate key for TLS authentication. Can be sourced from `KUBE_CLIENT_KEY_DATA`.
133
133
*`cluster_ca_certificate` - (Optional) PEM-encoded root certificates bundle for TLS authentication. Can be sourced from `KUBE_CLUSTER_CA_CERT_DATA`.
0 commit comments