Chao Xu
Chao Xu
/remove-sig api-machinery please re-tag us if sig auth needs support from sig apimachinery on this issue.
/triage accepted
Currently the discovery document is served from memory. The discovery document needs to be stored in etcd for HA apiservers to coordinate the content. @lavalamp can you explain more on...
Did you remove the vendor directory? Anyway, could you try again with the latest example, on a v1.9.0-alpha.1 or v1.8.0 Kuberentes cluster?
I'll update the example this week. The problem you saw is due to a recent change in the upstream: https://github.com/kubernetes/kubernetes/pull/50476.
Try again? You need to use it with the latest Kubernetes release (v1.8.0 or v1.9.0-alpha.1)
Merged the PR. Thanks.
What annotations specifically? I have some hypothesis but need to know the specific fields.
It's caused by the mismatching object version: the apiserver encodes the pod as api.Pod, and the webhook decodes the pod as v1.Pod. The issue will be fixed by the beta...
Hi @JorTurFer Can we expect #6655 in the next release? It's a very useful feature for our use case.