Documentation

I am using kube-prometheus-stack and also want to have the DO insights available. The documentation said to install kube-state-metrics, and also says: "The advanced performance metrics populate in the Insights tab correctly only if the kube-state-metrics deployment is in the kube-system namespace." https://github.com/kubernetes/kube-state-metrics says: "For users of prometheus-operator/kube-prometheus stack The (kube-prometheus) stack installs kube-state-metrics as one of its components; you do not need to install kube-state-metrics if you're using the kube-prometheus stack." So I installed using the below command to put it in the correct namespace, but I'm still not seeing the advanced metrics. helm upgrade prometheus prometheus-community/kube-prometheus-stack -i --atomic --namespace kube-system Can someone help me determine why this isn't connecting and maybe update the docs to cover this situation? It's not a big deal, but would be nice to have the metrics here as well as the Grafana dashboards.

Could it become possible that it's possible to subscribe to possible breaking changes for a specific channel/product (so let's say Droplets)?

Documentation often gets out of date quickly. Allow the community to easily keep it up to date!

I would think that setting a spend / usage throttle on a droplet would be the number one thing to surface in docs. However it seems like aside from an email alert, a usage spike in a droplet will simply scale up and bill the whole thing? I think many people mistake the "minimum spend" for a flat monthly fee.

The Release Notes ( https://docs.digitalocean.com/release-notes/ ) say that "You can subscribe to the release notes RSS feed." That RSS feed has some errors which make it unusable. It is using relative URLs instead of absolute URLs, which make subscribing to it useless. These errors can be seen here: https://validator.w3.org/feed/check.cgi?url=https%3A%2F%2Fdocs.digitalocean.com%2Frelease-notes%2Findex.xml I'll attach a screenshot showing what it looks like when I subscribe to it in Slack. The links are not clickable, so I'm not able to follow it to read about the new release.

In this page: ( https://docs.digitalocean.com/products/spaces/how-to/use-aws-sdks/ ), it says: “Using presigned URLs does not allow transferred files to be cached when using the Spaces CDN. Attempting to do so may result in double the bandwidth charge without the CDN’s performance benefit.” That reads like it’s saying that you can’t use presigned URLs with the CDN. But elsewhere, such as ( https://docs.digitalocean.com/products/spaces/how-to/enable-cdn/ ), it explicitly says “You can also use presigned URLs with the Spaces CDN.” So can you clarify the note about caching and presigned URLs?

The loadbalancer docs do not include how to set the external ip to a reserved ip address.

The "How to Configure CORS on DigitalOcean Spaces" ( https://docs.digitalocean.com/products/spaces/how-to/configure-cors/ ) misses a key moment about purging the cache after adding any headers. Please add this moment to the docs. I spent a lot of hours to figure out that was the problem.

Wrong picture used in section about isolating tenants. Currently it's showing the same exact picture for isolating execution environments and I'm sure the picture should be different. https://docs.digitalocean.com/products/networking/vpc/concepts/best-practices/

Current documentation: Due to an issue with Gunicorn running in Docker, App Platform fails to run when the temporary directory is not specified in the run command. To resolve, run Gunicorn to use a different location for its temp files. Modify the run command by passing this option: gunicorn --worker-tmp-dir /dev/shm project.wsgi, where project is the name of your project. Suggested edit: Due to an issue with Gunicorn running in Docker, App Platform fails to run when the temporary directory is not specified in the run command. To resolve, run Gunicorn to use a different location for its temp files. Modify the run command by passing this option: gunicorn --worker-tmp-dir /dev/shm project.wsgi, where project is the name of your project (Django). Or in the case of Flask, the run_command: gunicorn --worker-tmp-dir /dev/shm wsgi:app, where wsgi is wsgi.py and app is the Flask application instance inside wsgi.py .