Kubernetes

It was surprising to me you can only have one registry per-account ( https://docs.digitalocean.com/products/container-registry/details/limits/ ). This is especially true when they are zoned in one region. For reliability, I'd like to create one in each region I run k8s clusters in. I would also like to separate permissions for say prod vs staging, by having different repositories. One related feature, which could be a solution to part of the problem - is multi-homing registries - so even one can survive clusters going down.

Currently digitalocean supports only 1 container registry per account. It will be useful to support multiple registry (may be with max limit - changed by tickets). This will help organize multiple project/microservices deployment in their own registry.

Add ability to scale Kubernetes across multiple regions.

It would be great if Container Registries could have a maintenance window like Kubernetes Clusters. In this maintenance window, the Garbage Collection process would be run. This would reduce the space used by untagged images and unreferenced blobs.

Please release a way to make k8s users authenticating through an OpenID Connect Identity provider, it would greatly enhance the maneageability for those organization already using this way of authenticating. I really like DO k8s, but I'm not sure I'm going to use it on a wider scale due to this limitation; as you know for sure, other cloud providers allow it.

It would be nice to specify which tags we are deleting on your container registry page in the confirmation box. As the moment we're asked to specify (hope I get my terms right) the name of the container registry, and not the path therein. Thanks.

Would be great if CSI Volume Cloning was supported. Currently the only way this is achievable is by creating a snapshot and then generating a new volume from that snapshot. since taking snapshots of volumes does not show "progress" (see https://ideas.digitalocean.com/storage/p/progress-or-completed-at-date-for-volume-snapshots ) this solutions is very impractical however. See also: https://kubernetes.io/docs/concepts/storage/volume-pvc-datasource/

When using Digital Ocean Droplets as Kubernetes Worker Nodes, there is no possibility of assigning the Reserved IP´s to the Droplets. This is a Digital Ocean Reserved IP´s limitation described in: https://docs.digitalocean.com/products/networking/reserved-ips/details/limits/ When using external systems with whitelists tied to Droplets IP´s, every time they change either for a manual action or during the cluster upgrades (the most common scenario), the access to the external system is lost and a manual update of the whitelist must be done. So, as this a very common scenario in production systems, it will be great to be added.

When creating node pool for kubernetes can have option to taint the node hence only digital ocean related resources and certain application can be deployed over that pool.