Creating a Values Override File

Before installing AtScale, you need to create a file containing any configuration settings that are specific to your system.

AtScale's configuration settings are defined in the values.yml file included in its Helm chart. If you need to change any settings from the defaults, you must create a new YAML file that contains only those settings and their new values. When you run the installer, the values defined in this file override the ones defined in values.yml.

note

Save your values override file after installing AtScale, as you may need it to update your configuration later. For more information, see Upgrading AtScale.

For a first-time install, AtScale recommends creating an override file with the following settings.

global:
  ingressDomain: "subdomain.domain.com"

  atscale:
    # Set the certificate for TLS deployement.
    # For deployment, include the certificate and key in base64 format.
    tls:
      ## @param existingSecret; If empty, the secret will be auto-generated.
      ## In order to use a custom existingSecret, it is also needed to specify it on atscale-proxy.tls.existingSecret
      existingSecret: ""

      ## @param tlsCrt; If empty and no existingSecret provided, the certificate will be auto-generated.
      ## TLS Certificate Base64 encoded.
      tlsCrt: ""

      ## @param tlsKey; If empty and no existingSecret provided, the key will be auto-generated.
      ## TLS Key Base64 encoded.
      tlsKey: ""

      ## @param caCerts; If empty and no existingSecret provided, the CA certificate will be auto-generated.
      ## CA Certificates Base64 encoded.
      caCerts: ""

The following table describes the recommended override settings.

Setting	Description
`ingressDomain`	The ingress domain for the AtScale cluster. If you enable TLS, this should be the same as the domain defined in your certificate (see `tlsCrt` below).
`existingSecret`	Your manually-created TLS secret, if available. This needs to be of type `kubernetes.io/tls`. For more information, refer to the Kubernetes documentation. Note: Providing an `existingSecret` overrides any values specified for `tlsCrt` and `tlsKey`.
`tlsCrt`	The base64 encoded value of your TLS certificate file.
`tlsKey`	The base64 encoded value of your TLS certificate key.
`caCerts`	The base64 encoded value of your TLS Certificate Authority file.

Next steps​

Next steps