Bug 1813893
| Summary: | oc client use apiVersion: extensions/v1beta1 | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Robert Bohne <rbohne> |
| Component: | oc | Assignee: | Maciej Szulik <maszulik> |
| Status: | CLOSED WONTFIX | QA Contact: | zhou ying <yinzhou> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.3.0 | CC: | aos-bugs, eparis, jokerman, mfojtik |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-03-17 12:11:52 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: | |||
|
Description
Robert Bohne
2020-03-16 12:36:25 UTC
oc is getting information which API to use when talking with server from discovery provided from the server. For backwards compatibility reasons extensions/v1beta1 was set higher than apps thus oc picks that. It was decided that this is not going to be fixed, which might cause some issues and most importantly incompatibilities between upstream and openshift. There's a simple workaround available you can use: oc get|edit... deploy.apps which will explicitly use apps/v1, instead. That sounds not clear to me. To add some more facts: - With K8s 1.16 extensions/v1beta1 is deprecated. (https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/) - The web ui use apps/v1 and NOT extensions/v1beta1 - that means the user behavior is different between cli and webui. What is the exact reason for backward compatibility? Do you have an example? And who is responsible for the default Prometheus alert rule to check for extensions/v1beta1 usage. We should have consistent behavior. If we use extensions/v1beta1 than in WebUi + CLI + no alert OR we use apps/v1 in WebUI + CLI + alert rule. (In reply to Robert Bohne from comment #2) > That sounds not clear to me. To add some more facts: > > - With K8s 1.16 extensions/v1beta1 is deprecated. > (https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/) > - The web ui use apps/v1 and NOT extensions/v1beta1 - that means the user > behavior is different between cli and webui. webui takes explicit decision which API it uses, cli follows the discovery information, which allows us to be more dynamic when working with every possible resources, see CRDs, for example. It's a concious choice on our side. > What is the exact reason for backward compatibility? Do you have an example? This goes back to when extensions/v1beta1 was first introduced, where users were seeing problems talking with apiserver and getting the right information. I don't have example of top of my head but I remember there was an issue in kubernetes repository. > And who is responsible for the default Prometheus alert rule to check for > extensions/v1beta1 usage. We should have consistent behavior. If we use > extensions/v1beta1 than in WebUi + CLI + no alert OR we use apps/v1 in WebUI > + CLI + alert rule. That rule is being removed due to this and other related issues in one of the recent upgrades to cluster-kube-apiserver-operator https://github.com/openshift/cluster-kube-apiserver-operator/pull/741 Thank you for the information, have a nice day. |