To define if the namespace that team will use need to be created
List of execution role to associated with the VC namespace ExecutionRoleDefinition
Readonly
nameRequired unique name for organization. May map to an OU name.
Optional
Readonly
namespaceDefaults to team name prefixed by "team-"
Optional
Readonly
namespaceAnnotations such as necessary for GitOps engine.
Optional
Readonly
namespaceOptional, but highly recommended setting to ensure predictable demands.
Optional
Readonly
namespaceLabels such as necessary for AWS AppMesh
Optional
Readonly
serviceService Account Name
Optional
Readonly
serviceIf specified, the IRSA account will be created for with the IRSA role having the specified managed policies.
Optional
Readonly
teamOptional, directory where a team's manifests are stored
Optional
Readonly
teamTeam Secrets
Optional
Readonly
userOptions existing role that should be used for cluster access. If userRole and users are not provided, then no IAM setup is performed.
Optional
Readonly
usersTeam members who need to get access to the cluster
Optional
virtualTags to apply to EMR on EKS Virtual Cluster
Optional
extensionOptional, Use this function to add infrastructure or workloads deploymentto the team
Interface to define a EMR on EKS team