Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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