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

[Docs] be able to configure version and custom init image on AMQ Broker operator

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • operator
    • None

      when the operator is upgraded to 7.11 is not possible anymore to manage the previous version of the deployment, it forces to specify the exact image version when a custom init image is used.

      for example, using the below cr 

      apiVersion: broker.amq.io/v1beta1
kind: ActiveMQArtemis
metadata:
  name: amq-broker
  namespace: test-broker
spec:
  console:
    expose: true
  deploymentPlan:
    initImage: registry.redhat.io/amq7/amq-broker-init-rhel8@sha256:b4d18fdf02b37de84dc1b04090d26bba7757a86312f61bf58bb756c97b917e2d
    size: 1
  upgrades:
    enabled: true
    minor: false
  version: 7.10.2

       
      after upgrading to 7.11 the custom resource status appears as below:

      status:
    conditions:
    - lastTransitionTime: "2023-04-13T09:25:27Z"
      message: Version and Images cannot be specified at the same time
      observedGeneration: 1
      reason: VersionAndImagesConflict
      status: "False"
      type: Valid

      to fix that problem is possible to configure a specific version also of the image.

      it would help to have a flag to disable that check in order to be able to gradually adapt the custom resources.

              jcliffor@redhat.com John Clifford
              rhn-support-mgolfari Matteo Golfarini (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: