OpenshiftClient scale deploymentConfig Error

[cgcgccg]

Describe the bug

When I use openshift-client v6.7.1 to scale openshift deploymentConfig like below:

It will return error like this:

Fabric8 Kubernetes Client version

6.7.1

Steps to reproduce

Init openshift client
then use scale func
will return this error

Expected behavior

openshift client can scale deploymentConfig normal

Runtime

OpenShift

Kubernetes API Server version

1.25.3@latest

Environment

Windows, Linux

Fabric8 Kubernetes Client Logs

No response

Additional context

No response

[manusa]

We changed the way we scale resources to use the scale subresource. Maybe the OpenShift cluster is not supporting this operation. Could you share your cluster details (version, and so on).

/cc @shawkins

[cgcgccg]

We changed the way we scale resources to use the scale subresource. Maybe the OpenShift cluster is not supporting this operation. Could you share your cluster details (version, and so on).

/cc @shawkins

Hi, this is the version info:
Openshift version : 4.10
and

[shawkins]

Yes more than likely DeploymetConfigs don't support v1 scale. We have overriden support for jobs and v1beta1 resources that will likely be applicable here.

[shawkins]

Sure enough:

{"kind":"Scale","apiVersion":"extensions/v1beta1", ...

Supprising that it's still using the deprecated api.

[cgcgccg]

Sure enough:

{"kind":"Scale","apiVersion":"extensions/v1beta1", ...

Supprising that it's still using the deprecated api.

Thanks shawkins. So that's mean I should config my openshift-client apiVersion is v1beta1, is right?

[shawkins]

So that's mean I should config my openshift-client apiVersion is v1beta1, is right?

No, it means that /scale on a DeploymentConfig resource understands v1beta1 scale, not v1.

I guess they haven't committed to addressing this upstream: https://bugzilla.redhat.com/show_bug.cgi?id=1931897 https://issues.redhat.com/browse/OCPBUGS-865

[cgcgccg]

I understand. Thanks.

[manusa]

So that's mean I should config my openshift-client apiVersion is v1beta1, is right?

We'll probably release a 6.7 patch to address this and other issues.