Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

I’m trying to gain more control over the cloud resources created by my deployments, but I’m finding the “magic” that the do agent performs to translate k8s resources into DO resources (e.g. load balancers) to be hard to opt-out of. Is there a way to turn off some of those features for the cluster? Here’s a few things I’m running into:
Creating a LoadBalancer service automatically creates a DO load balancer asynchronously. There appears to be a way to stop this if I provide a custom annotation including the load balancer ID, but 1) this requires using provider specific annotations which I’m trying to avoid, and 2) this requires the LB to exist before the service exists.
Every time I create a NodePort service it automatically opens up the port to the public via the firewall rules. I don’t need this because I plan on creating and connecting a DO load balancer to the nodeport. Again, I can turn this off with an annotation, but once again its an annotation specific to DO, and more importantly specific to that service resource.
Can I just create k8s resources and have DigitalOcean do nothing without custom annotations on every resource?
jazzybruno
jazzybruno
9c24208528c843f2bcdb7d54782c69
Sean DesPortes
Robin van der Knaap
Robin van der Knaap
Attila Kovacs
Tomy Hsieh
Tuschl
Alexander Freyr
marcelhaldimann
Emiliano Maccaferri