Operator SDK Upgrade to v1.3.2

[yersan]

• Initial work for SDK upgrade

[yersan]

At the moment, the testsuite is throwing the following error from time to time, which delays the execution of the transaction recovery process, which results in a longer test execution that makes the testsuite to fail:

2022-07-25T10:48:43.165Z	ERROR	controllers.WildFlyServer	Failures during scaling down recovery processing	{"name": "wildfly-op-test-ns/wildfly-server-scale-down", "Desired replica size": 1, "Number of pods to be removed": 1, "error": "Failed to verify if the transaction subsystem is available. Error: Cannot execute management operation ':read-children-names(child-type=subsystem)' at pod wildfly-server-scale-down-0, error: Cannot decode JBoss CLI '${JBOSS_HOME}/bin/jboss-cli.sh --output-json -c --commands=':read-children-names(child-type=subsystem)'' executed on pod wildfly-server-scale-down-0 return data 'Failed to connect to the controller: The controller is not available at localhost:9990: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: Connection refused\n' to JSON. Cause: Fail to parse reader data to JSON, error: invalid character 'F' looking for beginning of value"}
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
	/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:298
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
	/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:253
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func1.2
	/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:216
k8s.io/apimachinery/pkg/util/wait.JitterUntilWithContext.func1
	/go/pkg/mod/k8s.io/[email protected]/pkg/util/wait/wait.go:185
k8s.io/apimachinery/pkg/util/wait.BackoffUntil.func1
	/go/pkg/mod/k8s.io/[email protected]/pkg/util/wait/wait.go:155
k8s.io/apimachinery/pkg/util/wait.BackoffUntil
	/go/pkg/mod/k8s.io/[email protected]/pkg/util/wait/wait.go:156
k8s.io/apimachinery/pkg/util/wait.JitterUntil
	/go/pkg/mod/k8s.io/[email protected]/pkg/util/wait/wait.go:133
k8s.io/apimachinery/pkg/util/wait.JitterUntilWithContext
	/go/pkg/mod/k8s.io/[email protected]/pkg/util/wait/wait.go:185
k8s.io/apimachinery/pkg/util/wait.UntilWithContext
	/go/pkg/mod/k8s.io/[email protected]/pkg/util/wait/wait.go:99

This is currently under investigation.

[yersan]

This is currently under investigation.

The reason was we were not using default readiness probes, so the testsuite was invoking the scale down without waiting until the applications were ready

[jmesnil]

@yersan thank you so much for that work!