Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-4732

Doc: Adding support to define SecurityContext

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Duplicate
    • Icon: Major Major
    • None
    • AMQ 7.8.1.CON.2.GA, AMQ 7.8.1.OPR.2.GA
    • documentation
    • None

      Integrating the PVC of ActiveMQ Artemis with some storage providers sometimes requires to be able to define the SecurityContext which should be used for the Pod.

      It should be possible to define an optional SecurityContext in the ActiveMQArtemis deploymentPlan spec, for example:

      apiVersion: broker.amq.io/v2alpha4
      kind: ActiveMQArtemis
      metadata:
        name: example
      spec:
        deploymentPlan:
          size: 1
          image: quay.io/artemiscloud/activemq-artemis-broker-kubernetes:0.2.0
          securityContext:
            runAsUser: 1000
            runAsGroup: 3000
            fsGroup: 2000
      

      The Operator should configure the StatefulSet to use the SecurityContext in the PodTemplate.

      Using mutating webhooks to modify the created Pods. But it would be much nicer to have this possibility built-in.

            jcliffor@redhat.com John Clifford
            jbyrne@redhat.com John Byrne
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: