This message was deleted.
# ask-for-help
s
This message was deleted.
🏁 1
🦄 1
x
This bug has been fixed in the next release
b
in Yatai?
In the meantime, can I try anything?
Short of updating Yatai
x
in yatai-deployment
Now you can install the development versions of yatai and yatai-deployment to avoid this bug:
Copy code
DEVEL=true DEVEL_HELM_REPO=true bash <(curl -s "<https://raw.githubusercontent.com/bentoml/yatai/main/scripts/quick-install-yatai.sh>")
Copy code
DEVEL=true DEVEL_HELM_REPO=true bash <(curl -s "<https://raw.githubusercontent.com/bentoml/yatai-deployment/main/scripts/quick-install-yatai-deployment.sh>")
b
Thanks! Would this work on an existing installation of Yatai?
x
Yes, but you can't downgrade to a previous version, because BentoDeployment CRD upgraded to a new version
b
no problem. trying it now 😄
I assume Ill need to update the
apiVersion: <http://serving.yatai.ai/v1alpha2|serving.yatai.ai/v1alpha2>
to
v1alpha3
?
x
You don't need to do the version conversion manually, yatai-deployment has its own conversion webhook to do the conversion of different versions automatically
b
so I can leave it as:
Copy code
apiVersion: <http://serving.yatai.ai/v1alpha2|serving.yatai.ai/v1alpha2>
kind: BentoDeployment
?
I'm using the BentoDeployment CRD for deploying
x
Yes, you don't need to do anything
just upgrade yatai and yatai-deployment
b
hmm
so there's a
docker-private-registry-proxy
previous in
yatai-components
should that be stopped?
it seems the pods for
docker-private-registry-proxy
in
yatai-deployment
is stuck in
Pending
Yup can confirm, I needed to do:
Copy code
kubectl delete ds docker-private-registry-proxy -n yatai-components
@Xipeng Guan Must I do a rollout after a successful installation?
x
Are you a 0.4.x yatai? You need to follow this document to migrate to version 1.0.0.a1 first https://docs.bentoml.org/projects/yatai/en/latest/installation/migration.html
b
Ahhh.
thanks! i'll try again tomorrow and report back