Move Docker images to ghcr.io/kedacore/http-add-on/*

[tomkerkhove]

As of today, our images are structured as following:

Which you can pull through:

docker pull ghcr.io/kedacore/http-add-on-interceptor

However, I'm wondering if we should change them to the following before v1.0:

- ghcr.io/kedacore/http-add-on-interceptor
+ ghcr.io/kedacore/http-add-on/interceptor
- ghcr.io/kedacore/http-add-on-operator
+ ghcr.io/kedacore/http-add-on/operator
- ghcr.io/kedacore/http-add-on-scaler
+ ghcr.io/kedacore/http-add-on/scaler

[JorTurFer]

I'm not 100% sure if GH supports the extra segment (I think so), but dockerhub doesn't support it, Contributors who are working in the repo and need to publish their images can't do IMAGE_REGISTRY=docker.io IMAGE_REPO=jorturfer make docker-publish, they would need to override the full qualified name for each image.
It's not a problem because it's supported, but maybe it's a side effect we haven't considered yet

[tomkerkhove]

Yes, you can definitely do this in GHCR.

I personally think it's worth the change to provide some structure but it's not a must. @kedacore/keda-maintainers @kedacore/keda-http-maintainers ?

[JorTurFer]

We can do it if there isn't any objection, my only concern is about developing experience, but I can think about how to make it easier. Next week I'll take a look

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

[zroubalik]

I wouldn't do this change personally, we don't do this for core images so I don't see much benefits in here, the prefix is there and I am not sure if the change in one character is wort the additional problems, which may be introduced by this change.