Hide Forgot
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-0528.html
This mentions disabling extensions/v1beta1. Why was that done? It was very useful for certain things.
extensions/v1beta1 was enabled by default which caused kubelet to fail with the default configuration. I changed the default setting to disable the extension by default (as it was in the previous releases). It can be always reenabled via --runtime-config option of apiserver.
KUBE_API_ARGS="--runtime-config=v1,extensions/v1beta1=true" did enable it. thanks. Is there a rough timeline for final 1.2?
> Is there a rough timeline for final 1.2? Not aware of. Hoping for 7.2.4 release.
Kevin, checking the apiserver patches, disabling of extensions/v1beta1 was actually never done for RHEL. I applied it on Fedora only. Anyway, kubernetes-1.2.0 shipping in 7.2.4 if nothing goes wrong [1]. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1327666