Jérémie MONSINJON

Hello, We are designing this feature and several implementations seem possible. One of the possibilities is to use the native import mechanism of CoreDNS (just like AKS or DigitalOcean) https://coredns.io/plugins/import/...

We are doing our best to deploy this feature end of September or early October (available through API)

Hello, This feature has been released but the documentation is still in progress. On every new K8S cluster, or after an update, the new CoreDNS config will include an expansion...

Hello Because of it's behavior, Kube-proxy needs to use the host network directly. It's definitively not a good idea to expose on `0.0.0.0:10249`. Exposed through HTTP, without any authentication mecanism,...

Hello @ZuSe Unfortunately, we don't manage 'alpha' features. Since K8S 1.23, this feature is in v1beta so we can have a look but definitively not for K8S 1.22.

Hello, Unfortunately we will not work on this feature until it's compatible with cgroupsv2.

Hello We planned to deliver this feature for the end of October. New ApiServer's parameters (not yet defined on our API) --oidc-username-claim --oidc-username-prefix --oidc-groups-claim --oidc-groups-prefix --oidc-required-claim --oidc-ca-file

Hello, We planned to deploy this feature by the end of November. It takes some time to design how to give you an access to a data stored in our...

We implemented a behavior like this: If desired_nodes parameter is empty AND a desired_nodes value already exists --> we use the existing value If desired_nodes parameter is empty AND a...

OK sorry @matmicro I reopened it. The Kubernetes custom resource definition is not yet up to date. I will close this issue as soon as it has been done. It's...