Open mikecutalo opened 6 years ago
Hi @guillaumerose is there any update for this?
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
comment.
Stale issues will be closed after an additional 30d of inactivity.
Prevent issues from auto-closing with an /lifecycle frozen
comment.
If this issue is safe to close now please do so.
Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. /lifecycle stale
The feature here will be to allow people to edit the kubeadm.yaml used to deploy the cluster. This is in the roadmap and I wish we can work on it soon.
Please, check https://docs.docker.com/docker-for-mac/troubleshoot/. Issues without logs and details cannot be debugged, and will be closed.
Expected behavior
To be able to use Kubernetes Initializers
Actual behavior
Unable to create an Kubernetes Initializer
Information
I had noticed that the docker-for-mac kubernetes implementation does have some flags set for kubernetes Initializers eg:
--admission-control=Initializers
However there is still an additional flag that needs to be set for thekube-apiserver
like so--feature-gates="Initializers=true"
and--runtime-config=admissionregistration.k8s.io/v1alpha1
.Steps to reproduce the behavior
Create a basic kubernetes initializerConfiguration manifest.
Create the resource in kubernetes
kubectl create -f <initializer-manifest-name>
Its at this point the error will occur.