Resource
dcloud_eks_access_entry
Lets an IAM user, group or role into a Kubernetes cluster as a Kubernetes user and groups. What it may do there comes from dcloud_eks_access_policy_association (or from RBAC bound to its groups). Import with <cluster_id>/<entry_id>.
Example Usage
resource "dcloud_eks_access_entry" "deployer" {
cluster_id = dcloud_eks_cluster.main.id
principal_type = "role"
principal = dcloud_iam_role.deployer.name
kubernetes_groups = ["deployers"]
}Schema
Required
cluster_id(String) The id of the parent resource ({cluster}in the path). Changing it replaces the resource.principal(String) The IAM user name, group name or role name; 404 when none has it, 409 when it already has an entry on the cluster. Up to 128 characters. Changing it replaces the resource.principal_type(String) Whatprincipalnames: user, group or role (IAM) One of:user,group,role. Changing it replaces the resource.
Optional
kubernetes_groups(Set of String) Extra Kubernetes groups the entry’s tokens carry, for your own RBAC bindings; at most 20, each 1–100 letters, digits and : . _ @ -, not starting system: or ews:. Default noneusername(String) Kubernetes username the entry’s tokens carry, prefixed ews: by the cluster (RBAC sees ews:); 1–100 letters, digits and : . _ @ -, not starting system:. Default: the IAM user name of whoever gets the token. Up to 100 characters. Must match^[A-Za-z0-9][A-Za-z0-9:._@-]*$.
Read-Only
id(String) The resource's id.principal_id(String) The IAM principal's id.
Import
Import is supported using the following syntax:
The terraform import command can be used, for example:
terraform import dcloud_eks_access_entry.deployer <cluster-id>/<entry-id>Generated from the provider's schema.
Related