Missing security context for the Operator Pod

[logdnalf]

Expected behaviour

The Operator Pod should be able to start up properly. However, as from the current state in master and due to a missing security context, the Operator Pod fails to start up because of the following error:

Error: container has runAsNonRoot and image will run as root

This probably has to do with the Docker image refusing to run as root.

Actual behaviour

The Operator Pod enters a configuration crash loop because it won't run as root. A proper security context is needed.

Steps to reproduce the behaviour

Deploy the Redis Operator from the master branch as described in the documentation:

kubectl apply -f example/operator/all-redis-operator-resources.yaml

Environment

 kubectl version
Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.2", GitCommit:"59603c6e503c87169aea6106f57b9f242f64df89", GitTreeState:"clean", BuildDate:"2020-01-23T14:21:54Z", GoVersion:"go1.13.6", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.5", GitCommit:"2166946f41b36dea2c4626f90a77706f426cdea2", GitTreeState:"clean", BuildDate:"2019-03-25T15:19:22Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}

How are the pieces configured?

• Redis Operator version: docker-pullable://quay.io/spotahome/redis-operator@sha256:a008aaadd862132bce225b5b39f6d84b2c5837459823989f2716ddc61ea62fa5
• Kubernetes version: 1.13.5
• Kubernetes configuration used: RBAC

[logdnalf]

Fixed in #228 .