support set securityContext

[alochym01]

error: error validating "rabbitmq-cluster.yaml": error validating data: ValidationError(RabbitmqCluster.spec): unknown field "securityContext" in com.rabbitmq.v1beta1.RabbitmqCluster.spec; if you choose to ignore these errors, turn validation off with --validate=false

apiVersion: rabbitmq.com/v1beta1
kind: RabbitmqCluster
metadata:
    name: rabbit-alochym
    namespace: rabbitmq-system
spec:
    securityContext:
        fsGroup: 1000
        runAsUser: 1000    
    replicas: 1
    persistence:
        storageClassName: local-storage
        storage: 10Gi    
    tolerations:
    - key: "node-role.kubernetes.io/master"
      operator: "Equal"
      #value: "rabbitmq"
      effect: "NoSchedule"    
      # node-role.kubernetes.io/master:NoSchedule
    resources:
        requests:
            cpu: 500m
            memory: 1Gi
        limits:
            cpu: 4000m
            memory: 8Gi

[Zerpet]

You can configure the security context via StatefulSet override, something like this:

apiVersion: rabbitmq.com/v1beta1
kind: RabbitmqCluster
metadata:
  name: my-rabbitmqcluster
spec:
  # Any properties you already have +
  override:
    statefulSet:
      spec:
        template:
          spec:
            containers:
              - name: rabbitmq
            securityContext:
              fsGroup: 1000
              runAsUser: 1000

We do not plan to add the security context as a top level proeprty in our Spec for now.

[Zerpet]

I will convert this issue to a GitHub discussion. Currently GitHub will automatically close and lock the issue even though your question will be transferred and responded to elsewhere. This is to let you know that we do not intend to ignore this but this is how the current GitHub conversion mechanism makes it seem for the users :(