Simone Tiraboschi
Simone Tiraboschi
> Could you please elaborate how can we commit to enable a non graduated feature by default? Is there a policy that is followed here? As for https://github.com/kubevirt/kubevirt/blob/39dd8b6948de11ba7ccbda50fac711cb88421768/pkg/virt-config/feature-gates.go#L25 Feature gates...
@jean-edouard we see a few failing tests on https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/kubevirt_hyperconverged-cluster-operator/2846/pull-ci-kubevirt-hyperconverged-cluster-operator-main-hco-e2e-kv-smoke-gcp/1775480051035279360
> I am just raising a flag that your interpretation of this is not how FGs are regarded per my understanding, including in Kubevirt. From Kubevirt side, the feature is...
> So you have kinds in your cache config that you don't watch, since you say the config worked in 0.15? That doesn't seem correct No, not really. During its...
> Well if you already have code to detect presence and create watches, you can use that same code to conditionally add cache config for those types depending on presence...
Thanks, it correctly worked for our case.
> Can this be closed? I fear we are not going the only one hitting this. If we cannot really prevent it, I think we should at least document it...