Fabian Kramm
Fabian Kramm
Would be nice if devspace could convert a docker compose file via kompose to a devspace, which would help people to adopt devspace if they already use docker compose.
Currently DevSpace does not add DevSpace vars as environment variables to command execution, except for pipelines. This makes it difficult for users to access variables in scripts and other commands...
Currently DevSpace will not sync files until there is at least a short duration where no file changes occur. However, in certain scenarios there are constantly changing files, like logs...
Currently we deploy vcluster in a single configuration in parallel in 4 different jobs for each distro. While this works and smoke tests vcluster, several features and areas of vcluster...
## Use Case Currently its not possible to use common logging solutions such as FluentD or ELK stack inside vcluster, because all of them mount the node host path directly....
Currently vclusters run as root by default. We should change that to non root and mark this as a breaking change as this will cause problems if vcluster is updated...
We should update the k0s, k3s & k8s versions for v1.21, v1.22, v1.23 & v1.24 [here](https://github.com/loft-sh/vcluster/tree/main/pkg/helm/values)
Currently the vcluster controller starts without waiting for vcluster itself to be ready, which often leads to pods initially failing. It would be better to wait until the api server...
Currently `namespaceSelectors` are not supported in vcluster, which means that `networkpolicies` and `spec.affinity.podAffinitity` are not fully supported. One way to translate a `namespaceSelector` into a pod `labelSelector` is by syncing...