dcloud eks access-entries create

Give an IAM user, group or role an access entry

IAM eks:CreateAccessEntryChanges state

policies associates access policies at once and also needs eks:AssociateAccessPolicy. A person also needs eks:AccessKubernetesApi in IAM to get a token.

Synopsis

dcloud eks access-entries create cluster --principal-type principalType --principal principal [flags]

Arguments

  • <cluster>Required

    string

    Also accepted as --cluster. Constraints: /^(ewk-[0-9a-f]{12}|[a-z]([a-z0-9-]{0,38}[a-z0-9])?)$/

Flags

  • --principal-typeRequired

    enum

    What `principal` names: user, group or role (IAM)

    One of: user, group, role

  • --principalRequired

    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

    Constraints: 1-128 chars

  • --usernameOptional

    string

    Kubernetes username the entry’s tokens carry, prefixed ews: by the cluster (RBAC sees ews:<username>); 1–100 letters, digits and : . _ @ -, not starting system:. Default: the IAM user name of whoever gets the token

    Constraints: 1-100 chars, /^[A-Za-z0-9][A-Za-z0-9:._@-]*$/

  • --kubernetes-groupsOptional

    array 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 none

    Constraints: 1-100 chars, /^[A-Za-z0-9][A-Za-z0-9:._@-]*$/

  • --policiesOptional

    array of json

    Access policies to associate at once

Example

dcloud eks access-entries create cluster --principal-type user --principal example

Generated from the API description, the same one the API checks requests against and the CLI is built from.