This message was deleted.
# ask-for-helps
Slackbot
06/13/2023, 9:31 AMThis message was deleted.
x
Xipeng Guan
06/13/2023, 9:56 AMIt looks like you have a problem with your k8s cluster, manually see if you can get the secret:
Copy code
kubectl -n yatai-system get secret yatai-common-envs
Siddhanth Shetty
06/13/2023, 10:02 AMDoes this look right?
Siddhanth Shetty
06/13/2023, 1:26 PMWonder if it could be related to this:
x
Xipeng Guan
06/13/2023, 1:33 PMI think you should check your network. I can't reproduce the error your preferred
👍 1
s
Siddhanth Shetty
06/13/2023, 3:32 PMAhh ok will try to debug that, any idea why the
kubectl apply -f my_deployment.yamlSiddhanth Shetty
06/14/2023, 9:41 AMI figured out what the issue was, it was related to helm, fixed that by running
Copy code
helm upgrade --install yatai-image-builder yatai-image-builder \
--repo <https://bentoml.github.io/helm-charts> \
-n yatai-image-builder \
--set dockerRegistry.server=$DOCKER_REGISTRY_SERVER \
--set dockerRegistry.inClusterServer=$DOCKER_REGISTRY_IN_CLUSTER_SERVER \
--set dockerRegistry.username=$DOCKER_REGISTRY_USERNAME \
--set dockerRegistry.password=$DOCKER_REGISTRY_PASSWORD \
--set dockerRegistry.secure=$DOCKER_REGISTRY_SECURE \
--set dockerRegistry.bentoRepositoryName=$DOCKER_REGISTRY_BENTO_REPOSITORY_NAMEkubectl apply