You can use GitHub Packages as docker registry.
However, if it is private, you need to authorize your k8s cluster for pulling.
There is an option to create a k8s docker-registry secret using PAT(Personal Access Token).

While working fine for test/dev stuff I’m curious about the correct way to do it for a production. I’m not sure that way when a DevOps creates PAT and uses it for an environment configuration is the best and optimal. The problem I see here -> if the person leaves an organisation and we terminate the access, the token will not work and we will have an issue.

Any suggestions about a better way?

I’ve thought about using system tokens which are available during GitHub Actions CI/CD, however, they are short-term, and if you need to scale your deployment for example after GitHub Action is finished it probably will fail.