Fixes auto-scaling issue + optional CRDs check + release 0.4.1

leochr commented 4 years ago

Signed-off-by: leochr leojc@ca.ibm.com

What this PR does / why we need it?:

Fixes the following issues:

Auto scaling does not work as expected. The changes made to Deployment by HorizontalPodAutoscaler are reversed. (#252)
Operator might crash on startup when optional CRDs API group (eg. serving.knative.dev/v1alpha1) is available, but actual CRD (Knative Service) is not present. (#251)
Release 0.4.1

Does this PR introduce a user-facing change?

[x] User guide
[x] CHANGELOG.md

Which issue(s) this PR fixes:

Fixes #

iamnogada commented 4 years ago

With Appsody 0.4.1. I increased instance to 2 but it reverted to one

leochr commented 4 years ago

@iamnogada The resources created and managed by Appsody Operator should not be modified directly. Operator continuously watches to ensure that they are in the desired state specified in AppsodyApplication CR.

Specify your settings in AppsodyApplication (app-deploy.yaml).

appsody / appsody-operator

Fixes auto-scaling issue + optional CRDs check + release 0.4.1 #254