https://flyte.org logo
Join Slack
Powered by
I'm trying to upgrade flyte in my GCP deployment. ...
# flyte-support
b
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?
a
Hey Andrew. I';m looking at it, have you tried doing a 
helm repo update
and then the 
terraform plan
?
the 
helm_release
resource supports setting up a specific 
version
but there are tradeoffs between hardcoding a version vs making it an input variable (most people evaluating wouldn't be sure what version to use) vs just leaving Helm to use the latest in the repo cache
b
Trying this now, seems like it did register changes in terraform, I'll try an apply with that
👍🏽 1
Well, supposedly this is working, but whenever I try to do the 
terraform apply
, I runs for 6 minutes 30 seconds and then outputs 
Error: client rate limiter Wait returned an error: context deadline exceeded
Looking online, it looks like that's normally a network issue, but it doesn't seem like that would be my problem. Have you ever seen that?
a
I've seen the 
context deadline exceeded
but when some of the flyte Pods don't come up and Terraform times out waiting. Can you confirm the status of the Flyte pods?
b
Everything is in the running state except for one webhook pod for some reason
looks like its an autoscaling issue for that webhook pod, so that may be related
a
can you do a 
kubectl describe
on the Pending pod?
b
yeah, i'm trying to figure it out now. looks like it can't find a node to fit onto, i tried allowing the node it should be on to scale up one more to see if that helps
Ok, I got that apply to go through. How can I check if it updated flyte? The ui version is the same, can't tell otherwise
a
do a 
helm ls -n flyte
b
looks like its still v1.10.0, which seems low
a
I think the most reliable option for now will be that you may add a new line here (but on your local copy) with the following: 
version   = xyz
with xyz being 
v1.13.0
for example
is there any particular version you need to upgrade to?
b
Not necessarily, I just didn't want to get too far behind and cause issues, mostly just wanted to get ahead of it and be aware of how it works
I could try that out. Unless you think it wouldn't really improve anything
a
I mean, in the upstream files there are drawbacks setting a version, but in your local modules that should get you to the desired version
b
Sounds great, I’ll go with that, then. Thank you for the help!
🙇🏽 1
2 Views
Open in Slack
PreviousNext
Powered by