Create a separate DockerHub organization/user for Sealed Secrets container images

[carrodher]

Which component: Controller

Is your feature request related to a problem? Please describe. In relation to the issue that occurred some days ago (https://github.com/bitnami-labs/sealed-secrets/issues/822), it would be nice that Sealed Secrets has its own organization or user in DockerHub as an independent project instead of relying on the Bitnami organization. The Bitnami Org is oriented to host container images belonging to the Bitnami Application Catalog which has a different purpose, tag nomenclature, etc, as well as unexpected changes like the Quay one can be expected without taking into account that Sealed Secrets images are hosted in that organization but serving for a different purpose.

We have a similar example in Kubeapps, which is a project maintained by Bitnami/VMware but whose images are hosted in its own DockerHub account see https://hub.docker.com/u/kubeapps, then, those images are the ones used by the kubeapps/kubeapps chart:

  image:
    registry: docker.io
    repository: kubeapps/dashboard
    tag: latest

Then, the Kubeapps images are part of the Bitnami DockerHub organization because they are part of BAC, but this is something totally separate from the release process of Kubeapps as a project.