CreateAddonRequest

import type { CreateAddonRequest } from "https://aws-api.deno.dev/v0.3/services/eks.ts?docs=full";

interface CreateAddonRequest {

addonName: string;

addonVersion?: string | null;

clientRequestToken?: string | null;

clusterName: string;

resolveConflicts?: ResolveConflicts | null;

serviceAccountRoleArn?: string | null;

tags?: {

[key: string]: string | null | undefined;

} | null;

}

§Properties

addonName: string

[src]

The name of the add-on. The name must match one of the names returned by DescribeAddonVersions.

addonVersion?: string | null

[src]

The version of the add-on. The version must match one of the versions returned by DescribeAddonVersions.

clientRequestToken?: string | null

[src]

A unique, case-sensitive identifier that you provide to ensure the idempotency of the request.

clusterName: string

[src]

The name of the cluster to create the add-on for.

resolveConflicts?: ResolveConflicts | null

[src]

How to resolve parameter value conflicts when migrating an existing add-on to an Amazon EKS add-on.

serviceAccountRoleArn?: string | null

[src]

The Amazon Resource Name (ARN) of an existing IAM role to bind to the add-on's service account. The role must be assigned the IAM permissions required by the add-on. If you don't specify an existing IAM role, then the add-on uses the permissions assigned to the node IAM role. For more information, see Amazon EKS node IAM role in the Amazon EKS User Guide.

Note: To specify an existing IAM role, you must have an IAM OpenID Connect (OIDC) provider created for your cluster. For more information, see Enabling IAM roles for service accounts on your cluster in the Amazon EKS User Guide.

tags?: {

[key: string]: string | null | undefined;

} | null

[src]

The metadata to apply to the cluster to assist with categorization and organization. Each tag consists of a key and an optional value. You define both.