-
Hi,
Not sure if I'm missing a setting (newish to k3s) however nodes that I specify with --node-taint CriticalAddonsOnly=true:NoExecute in the underlying K3S still receive pods from vCluster (and thus…
-
Hi,
I installed loft today on our onprem upstream kubernetes 1.19.10 cluster without any problem. Afterwards, I tried to create a vcluster which crashes constantly
I see lots of timeouts in the …
-
**Issue**
Unable to create vcluster in Civo kubernetes cluster which internally uses k3s. Able to connect to api-server but unable to deploy anything as coredns is failing for vcluster
**Steps**
…
-
As of the latest release of `v0.3.0-beta.3`, DownwardAPI metadata.labels for StatefulSet Pods would reference wrong label names. Here's a minimum reproducer:
```yaml
apiVersion: v1
kind: Namespac…
-
### Verification
- [X] I understand that [if I ignore these instructions, my issue may be closed without review](https://github.com/Homebrew/homebrew-cask/blob/master/doc/faq/closing_issues_without_r…
-
## Bug Report
Documentation for Contour package at:
* https://quirky-franklin-8969be.netlify.app/docs/latest/package-readme-contour-1.17.1/
says for the `envoy.service.type` option:
> The …
-
It looks to be that combination of `--target-namespace` , `--fake-nodes=false` and `--sync-all-nodes=true` works fine but when I change to `--sync-all-nodes=false` then those nodes gets created witho…
-
It would be nice to have the ability to specify the kube-context to use when calling vcluster. Currently the default one is used so you have to ensure you are setup correctly before calling vcluster.
…
-
After creating a vCluster, as per the getting started documentation, I deployed an nginx workload. Everything worked as expected. After which, I deleted the vCluster and things worked well. Host clust…
-
Hi,
we are currently facing the following issue when running an integration test against a vcluster (`version 0.3.1`). The test deploys some workload to the cluster, in this case istio. After execu…