[Question]: ghcr.io/k8sgpt-ai/k8sgpt-operator:latest is not up to date

[botchk]

Checklist

• I've searched for similar issues and couldn't find anything matching
• I've included steps to reproduce the behavior

Affected Components

• K8sGPT (CLI)
• K8sGPT Operator

K8sGPT Version

No response

Kubernetes Version

No response

Host OS and its Version

No response

Steps to reproduce

Currently ghcr.io/k8sgpt-ai/k8sgpt-operator:latest` (https://github.com/k8sgpt-ai/k8sgpt-operator/pkgs/container/k8sgpt-operator/88781850?tag=latest) is a 1 year old image

Expected behaviour

Pulling ghcr.io/k8sgpt-ai/k8sgpt-operator:latest should either pull the latest released version OR the existing latest image should be removed from the registry.

Actual behaviour

No response

Additional Information

I know this is more of a user fault if they don't check where the latest tag leads to, but pointing to a 1 year old image can be quite misleading. Often latest images are used when trying out a new tool for the first time and are expected to be up to date. Using a 1 year image without realizing it, can lead to some confusion.

[arbreezy]

I think we abandoned latest tag when we set up the release pipelines so it's unused and the preference is to use specific semver releases for both the operator and the k8sgpt project.

It could be misleading though as this tag still exists from the inception of the k8sgpt-operator project.

@AlexsJones are you able to untag any latest tag so it fails when someone tries to pull from the registry ?