Bug 1314728
Summary: | Build kubernetes for AH 7.2.3 | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Jan Chaloupka <jchaloup> |
Component: | kubernetes | Assignee: | Jan Chaloupka <jchaloup> |
Status: | CLOSED ERRATA | QA Contact: | atomic-bugs <atomic-bugs> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.2 | CC: | agoldste, ajia, atomic-bugs, gouyang, jchaloup, Kevin.Fox, miabbott |
Target Milestone: | rc | Keywords: | Extras |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | kubernetes-1.2.0-0.8.alpha1.gitb57e8bd.el7 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-03-31 23:26:10 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Comment 7
errata-xmlrpc
2016-03-31 23:26:10 UTC
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 |