New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to create a Template on OCP3 #2373
Comments
@rohanKanojia @gastaldi Can you have a look please? We have talk about something similar in #1805 |
let me revisit this whenever I get time today. |
rohanKanojia
added a commit
to rohanKanojia/kubernetes-client
that referenced
this issue
Jul 28, 2020
Looks like code added in fabric8io#1956 BackwardCompatibilityInterceptor wasn't handling /oapi failures properly. Fix BackwardCompatibilityInterceptor logic for routing to OpenShift 3 /oapi/v1 endpoints when OpenShift 4 /apis/{group}/v1 endpoints not found. Also added some tests to assert desired behavior
11 tasks
rohanKanojia
added a commit
to rohanKanojia/kubernetes-client
that referenced
this issue
Jul 28, 2020
Looks like code added in fabric8io#1956 BackwardCompatibilityInterceptor wasn't handling /oapi failures properly. Fix BackwardCompatibilityInterceptor logic for routing to OpenShift 3 /oapi/v1 endpoints when OpenShift 4 /apis/{group}/v1 endpoints not found. Also added some tests to assert desired behavior
rohanKanojia
added a commit
to rohanKanojia/kubernetes-client
that referenced
this issue
Jul 31, 2020
Looks like code added in fabric8io#1956 BackwardCompatibilityInterceptor wasn't handling /oapi failures properly. Fix BackwardCompatibilityInterceptor logic for routing to OpenShift 3 /oapi/v1 endpoints when OpenShift 4 /apis/{group}/v1 endpoints not found. Also added some tests to assert desired behavior
rohanKanojia
added a commit
to rohanKanojia/kubernetes-client
that referenced
this issue
Sep 15, 2020
…to /oapi URLs This commit reverts 293ab9d which was added in order to fix fabric8io#2373. This behavior was causing problems with Strimzi's Kubernetes Client upgrade: strimzi/strimzi-kafka-operator#3553 . On bisecting the failing test, I found this commit as culprit. Handling OpenShift old /oapi requests seem to be handled in OpenShiftOperation where we check `config.isOpenshiftApiGroupsEnabled()` to modify OperationContext. However, fabric8io#2373 can be fixed by adding apiVersion in OpenShiftOperation.
11 tasks
rohanKanojia
added a commit
to rohanKanojia/kubernetes-client
that referenced
this issue
Sep 16, 2020
…to /oapi URLs This commit reverts 293ab9d which was added in order to fix fabric8io#2373. This behavior was causing problems with Strimzi's Kubernetes Client upgrade: strimzi/strimzi-kafka-operator#3553 . On bisecting the failing test, I found this commit as culprit. Handling OpenShift old /oapi requests seem to be handled in OpenShiftOperation where we check `config.isOpenshiftApiGroupsEnabled()` to modify OperationContext. However, fabric8io#2373 can be fixed by adding apiVersion in OpenShiftOperation.
rohanKanojia
added a commit
to rohanKanojia/kubernetes-client
that referenced
this issue
Sep 21, 2020
…to /oapi URLs This commit reverts 293ab9d which was added in order to fix fabric8io#2373. This behavior was causing problems with Strimzi's Kubernetes Client upgrade: strimzi/strimzi-kafka-operator#3553 . On bisecting the failing test, I found this commit as culprit. Handling OpenShift old /oapi requests seem to be handled in OpenShiftOperation where we check `config.isOpenshiftApiGroupsEnabled()` to modify OperationContext. However, fabric8io#2373 can be fixed by adding apiVersion in OpenShiftOperation.
rohanKanojia
added a commit
to rohanKanojia/kubernetes-client
that referenced
this issue
Sep 21, 2020
…to /oapi URLs This commit reverts 293ab9d which was added in order to fix fabric8io#2373. This behavior was causing problems with Strimzi's Kubernetes Client upgrade: strimzi/strimzi-kafka-operator#3553 . On bisecting the failing test, I found this commit as culprit. Handling OpenShift old /oapi requests seem to be handled in OpenShiftOperation where we check `config.isOpenshiftApiGroupsEnabled()` to modify OperationContext. However, fabric8io#2373 can be fixed by adding apiVersion in OpenShiftOperation.
rohanKanojia
added a commit
to rohanKanojia/kubernetes-client
that referenced
this issue
Sep 21, 2020
…to /oapi URLs This commit reverts 293ab9d which was added in order to fix fabric8io#2373. This behavior was causing problems with Strimzi's Kubernetes Client upgrade: strimzi/strimzi-kafka-operator#3553 . On bisecting the failing test, I found this commit as culprit. Handling OpenShift old /oapi requests seem to be handled in OpenShiftOperation where we check `config.isOpenshiftApiGroupsEnabled()` to modify OperationContext. However, fabric8io#2373 can be fixed by adding apiVersion in OpenShiftOperation.
rohanKanojia
added a commit
to rohanKanojia/kubernetes-client
that referenced
this issue
Sep 21, 2020
…to /oapi URLs This commit reverts 293ab9d which was added in order to fix fabric8io#2373. This behavior was causing problems with Strimzi's Kubernetes Client upgrade: strimzi/strimzi-kafka-operator#3553 . On bisecting the failing test, I found this commit as culprit. Handling OpenShift old /oapi requests seem to be handled in OpenShiftOperation where we check `config.isOpenshiftApiGroupsEnabled()` to modify OperationContext. However, fabric8io#2373 can be fixed by adding apiVersion in OpenShiftOperation.
vsalbaba
pushed a commit
to vsalbaba/xtf
that referenced
this issue
Jun 17, 2021
as fabric8io/kubernetes-client#2373 was fixed, api version guessing can be streamlined.
vsalbaba
pushed a commit
to vsalbaba/xtf
that referenced
this issue
Jun 22, 2021
as fabric8io/kubernetes-client#2373 was fixed, api version guessing can be streamlined.
4 tasks
mnovak1
pushed a commit
to xtf-cz/xtf
that referenced
this issue
Jul 13, 2021
as fabric8io/kubernetes-client#2373 was fixed, api version guessing can be streamlined.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is clone of xtf-cz/xtf#373 because I believe kubernetes client should keep backward compatibility.
I am getting
With 4.9.2 it was OK.
After some debugging, the difference is in URL:
4.9.2
:4.10.2
Workaround:
The text was updated successfully, but these errors were encountered: