New RunLLM response generated: >>>*# Question* I'm trying to upgrade flyte in my GCP deployment. I'm using the flyte-deploy terraform code. It looks like a helm upgrade should do it, is that right? I'm running into an issue with that, though, because I'm using variables in my values file, like

hostName: ${hostname}

etc. which helm can't read. Does anyone know how I can do this flyte upgrade? # Answer Yes, a

helm upgrade

is the correct approach for upgrading Flyte. However, Helm does not support variable substitution directly in the values file. You need to preprocess the values file to replace the variables with actual values before running the

helm upgrade

command. You can use tools like

envsubst

to substitute environment variables in your values file. Here's a general approach: 1. Create a template values file with placeholders for your variables, e.g., `values-template.yaml`:

common:
      ingress:
        host: "${hostname}"

2. Export the required environment variables:

export hostname="your.actual.hostname"

3. Use

envsubst

to replace the placeholders and generate the actual values file:

envsubst < values-template.yaml > values.yaml

4. Run the

helm upgrade

command with the generated values file:

helm upgrade <RELEASE_NAME> flyteorg/flyte-core -n <YOUR_NAMESPACE> --values values.yaml

Would you like more details on any of these steps? Sources: - Single Cluster Production-grade Cloud Deployment Slack Link https://flyte-org.slack.com/archives/CP2HDHKE1/p1724697500.758049 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.