Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

FargateProfile

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

An object representing an Fargate profile.

interface FargateProfile {
clusterName?: string | null;
createdAt?: Date | number | null;
fargateProfileArn?: string | null;
fargateProfileName?: string | null;
podExecutionRoleArn?: string | null;
selectors?: FargateProfileSelector[] | null;
status?: FargateProfileStatus | null;
subnets?: string[] | null;
tags?: {
[key: string]: string | null | undefined;
}
| null;
}

§Properties

§
clusterName?: string | null
[src]

The name of the Amazon EKS cluster that the Fargate profile belongs to.

§
createdAt?: Date | number | null
[src]

The Unix epoch timestamp in seconds for when the Fargate profile was created.

§
fargateProfileArn?: string | null
[src]

The full Amazon Resource Name (ARN) of the Fargate profile.

§
fargateProfileName?: string | null
[src]

The name of the Fargate profile.

§
podExecutionRoleArn?: string | null
[src]

The Amazon Resource Name (ARN) of the pod execution role to use for pods that match the selectors in the Fargate profile. For more information, see Pod Execution Role in the Amazon EKS User Guide.

§
selectors?: FargateProfileSelector[] | null
[src]

The selectors to match for pods to use this Fargate profile.

§

The current status of the Fargate profile.

§
subnets?: string[] | null
[src]

The IDs of subnets to launch pods into.

§
tags?: {
[key: string]: string | null | undefined;
}
| null
[src]

The metadata applied to the Fargate profile to assist with categorization and organization. Each tag consists of a key and an optional value. You define both. Fargate profile tags do not propagate to any other resources associated with the Fargate profile, such as the pods that are scheduled with it.