I am trying to use a private registry to pull images by following these instructions.
When setting only the spec.reaper.containerImage.registry and spec.medusa.containerImage.registry properties, it seems to affect the tags that are used as well. Instead of using the default fixed versions, it is using the latest tags for the repear and medusa images.
I would have expected the tags not to be affected since I am only providing the information I case about. With the current behaviour I need to provide the tags and I need to update them each time the version changes.
How to reproduce it (as minimally and precisely as possible):
Create the K8ssandraCluster without setting spec.reaper.containerImage.registry and spec.medusa.containerImage.registry.
Check the images versions used for each container.
Delete the K8ssandraCluster.
Set the spec.reaper.containerImage.registry and spec.medusa.containerImage.registry perperties with the default registry: docker.io.
Check the images versions used, they are different.
What happened?
I am trying to use a private registry to pull images by following these instructions.
When setting only the
spec.reaper.containerImage.registry
andspec.medusa.containerImage.registry
properties, it seems to affect the tags that are used as well. Instead of using the default fixed versions, it is using thelatest
tags for the repear and medusa images.Did you expect to see something different?
I would have expected the tags not to be affected since I am only providing the information I case about. With the current behaviour I need to provide the tags and I need to update them each time the version changes.
How to reproduce it (as minimally and precisely as possible):
K8ssandraCluster
without settingspec.reaper.containerImage.registry
andspec.medusa.containerImage.registry
.K8ssandraCluster
.spec.reaper.containerImage.registry
andspec.medusa.containerImage.registry
perperties with the default registry:docker.io
.Environment
Kubernetes version information:
```yaml
apiVersion: k8ssandra.io/v1alpha1 kind: K8ssandraCluster metadata: name: test spec: auth: true cassandra: serverVersion: "4.1.5" serverImage:/k8ssandra/cass-management-api:4.1.5-ubi8
serviceAccount: cassandra
superuserSecretRef:
name: test-superuser
telemetry:
mcac:
enabled: false
prometheus:
enabled: true
datacenters:
tag: 3.6.1
pullSecretRef: name: docker-cfg telemetry: mcac: enabled: false prometheus: enabled: true deploymentMode: SINGLE medusa: containerImage: registry:
tag: 0.22.0
pullSecretRef: name: docker-cfg cassandraUserSecretRef: name: test-medusa purgeBackups: false storageProperties: prefix: test credentialsType: role-based storageSecretRef: name: "" storageProvider: s3 region: eu-west-1 bucketName: s3-test-cassandra sslVerify: true maxBackupAge: 5
maxBackupCount: 30
apiVersion: v1 kind: ServiceAccount metadata: name: cassandra annotations: eks.amazonaws.com/role-arn: "arn:aws:iam::XXXXXXXXXXXX:role/iam-role-sa-test-cassandra" imagePullSecrets:
┆Issue is synchronized with this Jira Story by Unito ┆Issue Number: K8OP-1