chore(doc): registry requirements

Closes #4720

docs/modules/ROOT/pages/installation/registry/registry.adoc

@@ -46,9 +46,19 @@ spec:
 
 You can therefore update the values in the `IntegrationPlatform` in order to perform any change to the registry configuration after the Camel K operator is installed. The changes will be immediately reconciled and ready to use.
 
+[[configuring-registry]]
+== Container registry requirements
+Each platform may have its default registry of choice. And each container registry may have a slight different configuration. Please, be aware that we won't be able to support all the available solutions.
+
+The only requirement we have is that the registry must be able to produces/consumes images with the following tagging convention: `<registry-host>[:<registry-port>]/<k8s-namespace>/camel-k-kit-<hash-code>@sha256:<sha256-code>`, ie `10.110.251.124/default/camel-k-kit-ck0612dahvgs73ffe5g0@sha256:3c9589dd093b689aee6bf5c2d35aa1fce9d0e76d5bb7da8b61d87e7a1ed6f36a`.
+
+This should be within the standard convention adopted by https://docs.docker.com/engine/reference/commandline/pull/#pull-an-image-by-digest-immutable-identifier[pulling a Docker image by digest] (immutable).
+
+NOTE: you can configure Camel K to use an insecure private registry. However, your Kubernetes cluster may not be able to https://github.com/apache/camel-k/issues/4720#issuecomment-1708228367[pull images from an insecure registry without proper configuration].
+
 [[configuring-registry-list]]
-== Special container registry requirements
-Each platform may have its default registry of choice. And each container registry may have a slight different configuration. We have some hints that can help you configuring on the most common platforms:
+=== Special container registry requirements
+We have some hints that can help you configuring on the most common platforms:
 
 - xref:installation/registry/digitalocean.adoc[DigitalOcean]
 - xref:installation/registry/dockerhub.adoc[Docker Hub]