Come up with webhook developer workflow to test it locally

[mengqiy]

There are at least 2 possible solutions:

• Have a minikube cluster running locally and also run the webhook server locally.
• Have a cluster running in the cloud and webhook server running locally. Put a proxy service between them. The proxy service can either in the cluster or provided by a 3rd party.

Document the dev workflow.

[mengqiy]

example proxy servie https://serveo.net/ and https://ngrok.com/

[mohnishkodnani]

I have a minikube running locally and i have mutating web hook to be before pod creation.
I get the error
Internal error occurred: failed calling admission webhook
https://webhook-server-service.default.svc:443/mutating-create-update-pods?timeout=30s: dial tcp 10.104.245.128:443: getsockopt: connection refused
The IP listed is the clusterIP of the service.
I have the http server running in GoLand IDE.

[mengqiy]

I guess this is how this happened:
You have webhook configuration already installed which mutates pod. You can run kubectl get mutatingwebhookconfigurations.admissionregistration.k8s.io to check.
When you want to bring up the webhook server, it tries to create pods which will be blocked by the admission webhook if the FailurePolicy field is Fail in mutatingwebhookconfigurations.

One thing you can do to fix this is using namespaceSelector to not block the namespace where the webhook server runs.

[mohnishkodnani]

Can you tell me where the hooks are for MutatingWebHookConfiguration object ?

[mengqiy]

Can you tell me where the hooks are for MutatingWebHookConfiguration object ?

https://github.com/kubernetes/api/blob/d04500c8c3dda9c980b668c57abc2ca61efcf5c4/admissionregistration/v1beta1/types.go#L113-L124

[ukclivecox]

Is there an initial workflow for running with Minikube for this yet?
Be good to clarify what is required or manual steps. Happy to help.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[alexeldeib]

/reopen