Helm Values Examples
This section contains examples of values.yaml
configuration for various infrastructure combinations. The examples in this section are not complete values.yaml
files and are meant to demonstrate only the settings directly relevant to each example.
RDS with IAM User
rds:
enabled: true
iamAuth: true
# password unused if `iamAuth: true`
postgresUser: "<STYRA_POSTGRES_USER>"
postgresPassword: "" # leave unset
postgres:
enabled: false
aws:
enabled: true
access_key_id: “<STYRA_IAM_USER_ACCESS_KEY>”
secret_access_key: “<STYRA_IAM_USER_SECRET_KEY>”
RDS with IAM Role
serviceAccount: styra-das
dynamoDB:
enabled: false
rds:
enabled: true
iamAuth: true
postgresUser: "<STYRA_DAS_USER>"
postgresPassword: "" # leave unset
postgresAddress: "<set the postgres endpoint>"
postgresDBName: "<set the postgres database name>"
postgres:
enabled: false
aws:
enabled: true
access_key_id: "" # leave unset
secret_access_key: "" # leave unset
region: "<set the region>"
irsa:
enabled: true
serviceAccount:
create: true
aws_account_id: "<set the AWS Account ID of the target Role>"
aws_iam_role: "<set the AWS IAM Role name>"
DynamoDB with S3 IAM User Authentication
dynamoDB:
enabled: true
resourcePrefix: "<STYRA_RESOURCE_PREFIX>"
rds:
enabled: false
postgres:
enabled: false
aws:
enabled: true
access_key_id: "<AWS_ACCESS_KEY_ID>"
secret_access_key: "<AWS_SECRET_ACCESS_KEY_ID>"
region: "<AWS_REGION>"
DynamoDB with S3 IAM Role Authentication
Set the serviceAccount
field to the STYRA_DAS_SERVICE_ACCOUNT
value chosen in Amazon DynamoDB with S3. This will be used to name the Kubernetes service account created during installation.
serviceAccount: <STYRA_DAS_SERVICE_ACCOUNT>
dynamoDB:
enabled: false
resourcePrefix: "<STYRA_RESOURCE_PREFIX>"
rds:
enabled: false
postgres:
enabled: false
aws:
enabled: true
access_key_id: "" # leave unset
secret_access_key: "" # leave unset
region: "<set the region>"
irsa:
enabled: true
serviceAccount:
create: true
aws_account_id: "<set the AWS IAM Role name>"
aws_iam_role: "<set the AWS IAM Role name>"
aws.irsa.service_account.create
must be set to false
if using a ServiceAccount that has already been deployed. This might be the case when, for example, using a ServiceAccount pre-created through eksctl
.