WPA will get panic if we try to scale Openshift DeploymentConfig about watermarkpodautoscaler HOT 10 CLOSED

👋 We added support for Openshift resources in the new minor version (0.3.0) that should be released in the next few days.
Thanks again for reporting this issue - I am going to close it for now, feel free to reach out if you have any more questions.

from watermarkpodautoscaler.

Hey @yummydsky - Apologies for the delay.
Could you try out the datadog/watermarkpodautoscaler:v0.2.0 ?

from watermarkpodautoscaler.

@CharlyF ok, we will try WPA v0.2.0, thanks for your reply.

from watermarkpodautoscaler.

@CharlyF Could you tell me how can I install WPA v0.2.0 from watermarkpodautoscaler_0.2.0_Linux_x86_64.tar.gz?
After unzip the file, I see a binary file watermarkpodautoscaler. I have no idea how to use it because the installation step of v0.1.0 is installed through Helm.

Usage of ./watermarkpodautoscaler:
--kubeconfig string Paths to a kubeconfig. Only required if out-of-cluster.
--master --kubeconfig (Deprecated: switch to --kubeconfig) The address of the Kubernetes API server. Overrides any value in kubeconfig. Only required if out-of-cluster.
-v, --version print version
--zap-devel Enable zap development mode (changes defaults to console encoder, debug log level, and disables sampling)
--zap-encoder encoder Zap log encoding ('json' or 'console')
--zap-level level Zap log level (one of 'debug', 'info', 'error' or any integer value > 0) (default info)
--zap-sample sample Enable zap log sampling. Sampling will be disabled for integer log levels > 1
--zap-time-encoding timeEncoding Sets the zap time format ('epoch', 'millis', 'nano', or 'iso8601') (default )
pflag: help requested

Thanks.

from watermarkpodautoscaler.

@CharlyF

NVM, I found another link to download v0.2.0.tar.gz on tags

Thanks for your help.

from watermarkpodautoscaler.

Okay, glad to hear - Has 0.2.0 solved your issue ?

from watermarkpodautoscaler.

Sorry for the delay, the environment is missing, we are trying to re-build the environment, will let your know the result asap.

from watermarkpodautoscaler.

@CharlyF ,
Still the same issue in version 0.2.0

from watermarkpodautoscaler.

@yummydsky thanks for confirming.
The error you got in the first place was due to the controller not being able to retrieve the right RESTMapping, but we changed the error handling to avoid this issue, new logic here.
Could you paste the equivalent logs (error log from the controller) so I can investigate ?

from watermarkpodautoscaler.

wpa.log
Sorry for the delay.

from watermarkpodautoscaler.