Documentation

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

Ability to Bookmark Tutorials. I don't want to keep a track of comments and updates. But at times I just want to go back to the tutorial I read last week quickly. Yes I can use Browser bookmarks but it would be better if Digitalocean alows us to keep a list of tutorials to refer to again.

The parameter mention "droplet_id" but the examples only provide field "id" and not "droplet_id"

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.

It is not completely intuitive or obvious for everyone what each cache status means, so the documentation should include that to make it clearer for the user.

It'd be nice to be able to receive release notes in my email, alongside status emails. Often, a release change can have the same level of impact on my organization as an outage.

I started by searching for a way to visualise logs that are stored in my logs folders. I then found an article by Digital Ocean's Erin Glass which helped a great deal in getting things up and running. Although I had several concerns over stability and also thought what if I could have everything, ie: all tooling under one roof. I then ported the install to Kali Linux, to try to see whether it'd be possible. Instead of using Nginx, I used Apache2 web server. As a final product, the entire solution was installed on Kali Linux. If you would like a write-up, you may contact me at abrnet@outlook.com .

Please update my rocketchat version

The following DigitalOcean documentation is missing a crucial configuration step: https://docs.digitalocean.com/support/how-do-i-enable-proxy-protocol-when-my-load-balancer-sends-requests-to-the-nginx-ingress-controller/ • This guide does not include the do-loadbalancer-hostname configuration, which is essential for proper setup. • Without this, internal traffic routed via the Load Balancer starts failing. To resolve this, the following section should be included or at list mentioned: https://docs.digitalocean.com/products/kubernetes/how-to/configure-load-balancers/#accessing-by-hostname

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.