Consistent API for image configurations

[Miles-Garnsey]

What is missing?

K8ssandra operator now has an Image struct which is a structured API for setting image configurations (including the ability to specify different docker credentials for each image).

It would be good if cass-operator used the same mechanism for consistency and to ensure that creds can be set. At present, the image fields are strings.

┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: CASS-46

[jimdickinson]

Why is an image string field not good enough? This is the standard across many k8s projects, and I would actually advise to simplify all the image stuff for cassdc to "the user must pass an image string, and it is used"

[Miles-Garnsey]

@jimdickinson, you're entirely correct in saying that Pods, Deployments et al. all use strings to specify images. The thrust of this ticket is that the mechanism should be consistent.

k8ssandra-operator has introduced a struct image field, which does have the advantage of allowing different docker creds per image.

Whether it makes sense to allow different docker registry creds per container I'm unsure - I don't know if k8s actually supports specifying multiple credentials for a single pod, now you ask the the question.