Update docs for configuring the provider #1132
Conversation
|
@jrhouston There is another way to configure the provider, specifically for AWS EKS clusters, which is with data "aws_eks_cluster" "eks" {
name = var.eks_cluster_id
}
data "aws_eks_cluster_auth" "eks" {
name = var.eks_cluster_id
}
provider "kubernetes" {
token = data.aws_eks_cluster_auth.eks.token)
host = data.aws_eks_cluster.eks.endpoint)
cluster_ca_certificate = base64decode(data.aws_eks_cluster.eks.certificate_authority.0.data))
}This should be used instead of the "Exec-based credential plugins" style which is problematic in that it depends on the presence of the Please also fix the getting started guide |
jrhouston
force-pushed
the
update-config-docs
branch
from
e58cc08
to
7289d86
Compare
|
@jrhouston FYI the website-lint is failing. |
| (or default) location. Depending on whether you have a current context set | ||
| this _may_ require `config_context_auth_info` and/or `config_context_cluster` | ||
| and/or `config_context`. | ||
| For a full list of supported provider authentication arguments and their corresponding environment variables, see the [argument reference](#argument-reference) below. |
There was a problem hiding this comment.
Nice, this section makes it a bit more clear. I like the addition of the links.
|
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks! |
ghost
locked as resolved and limited conversation to collaborators
Description
This PR improves the docs for configuring the provider