search

loft-sh / loft

Namespace & Virtual Cluster Manager for Kubernetes - Lightweight Virtual Clusters, Self-Service Provisioning for Engineers and 70% Cost Savings with Sleep Mode
https://loft.sh/docs/introduction
Other
737 stars 65 forks source link

Unable to access other namespaces? #227

Closed withinboredom closed 1 year ago

withinboredom commented 1 year ago

We use loft and devspace to deploy Once but it isn't working due to

error for bootstrap "builder0": cannot access namespace image-builder through space once

This is because our shared builder lives in another namespace to take advantage of build caches. In v2, there were no 'automatic policies' like this. How can I disable this policy or add an exception?

withinboredom commented 1 year ago

Looks like the workaround is loft use cluster && devspace use namespace XXX.

withinboredom commented 1 year ago

Apparently, you cannot update helm charts through the UI:

cannot access namespace kube-system through space kube-prometheus-stack

cc: @FabianKramm

neogopher commented 1 year ago

Hi @withinboredom, This has been addressed now in Loft v3.0.1. Kindly upgrade to this version from the Loft UI and the app upgrades should start working as well.

withinboredom commented 1 year ago

I'll give it a go @neogopher!

neogopher commented 1 year ago

Hey @withinboredom, Just wanted to check whether you got a chance to try this out. If it is working for you now, we could close this issue.

withinboredom commented 1 year ago

Seems to be working now

neogopher commented 1 year ago

Great!! Thanks @withinboredom for confirming and for your patience while we addressed it. :blush: Feel free to reach out in case of any issues.

alexandradragodan commented 1 year ago

Thanks again for opening up this issue. 🏅 As @neogopher mentioned, feel free to open another one if you encounter any other issues.

I'll close this one for now.