search

hazelcast / hazelcast-operator

Apache License 2.0
10 stars 14 forks source link

Unable to influence mancenter image tag #49

Closed robinroos closed 3 years ago

robinroos commented 3 years ago

Hello,

I use OpenShift Operator for Hazelcast (v0.3.6) to deploy only Hazelcast Management Center.

My cluster, deployed seperately as Hazelcast embedded in a SpiringBoot application, is version 5.0-SNAPSHOT.

The deployed version of mancenter cannot support the version of the cache instance:

Cluster version 5.0 is not compatible with this version of Management Center (4.2021.03)

I am attempting to cause the Operator to install the 5.0-BETA-1 version of Management Center, which does exist on hub.docker.com. No matter what I do, the resulting StatefulSet always has:

image: 'hazelcast/management-center:4.2021.03'

Below is the best config I have so far, applied in the Operator after deleting the only Hazelcast and then recreating it, using YAML inputs.

apiVersion: hazelcast.com/v1alpha1
kind: Hazelcast
metadata:
  name: hz
  namespace: bento
spec:
  securityContext:
    runAsUser: ''
    runAsGroup: '0'
    fsGroup: ''
  hazelcast:
    enabled: false
  mancenter:
    enabled: true
    image:
      tag: "5.0-BETA-1"
    adminCredentialsSecretName: mancenter-admin-credentials-secret
    persistence:
      existingClaim: hazelcast-mancenter-data

Can anyone spot my mistake?

robinroos commented 3 years ago

Upon examining hz-op-dockerhub-release.yml (line 97) it is evident that mancenter.image.tag is respected only if mancenter.image.repository is also specified.

The same would be true for the Hazelcast version also: image.tag respected only if image.repository is also specified.