docs(qdrant): add guides and examples

[tamalsaha]

Summary

• expand Qdrant guides to match the detailed style used in Postgres docs
• replace brief/stub content with full step-by-step operational walkthroughs
• update Qdrant concept and overview pages to accurately describe day-2 workflows and autoscaling behavior

What Was Updated

• operation guides expanded with detailed flow and verification:
  • UpdateVersion
  • Restart
  • VolumeExpansion
  • Reconfigure
  • ReconfigureTLS
  • RotateAuth
  • HorizontalScaling
  • VerticalScaling
• monitoring guides expanded:
  • Builtin Prometheus
  • Prometheus Operator
• autoscaler guides expanded:
  • Compute autoscaling
  • Storage autoscaling
• core docs expanded:
  • quickstart
  • RBAC
  • private registry usage
  • custom RBAC usage
  • configuration via config file
• concepts updated:
  • Qdrant
  • QdrantVersion catalog
  • QdrantOpsRequest
  • QdrantAutoscaler
• overview pages updated across Qdrant guide sections (including backup, ops-request, monitoring, tls, reconfigure, scaling, update-version, rotate-auth, autoscaler)

Notes

• changes are documentation-focused and intended to make Qdrant docs consistent with existing KubeDB guide depth and structure
• PR remains scoped to Qdrant documentation and related guide index updates

[github-actions]

Visit the preview URL for this PR (updated for commit 703df95):

https://kubedb-v2-hugo--pr865-pr-qdrant-docs-gb1pk8kq.web.app

_{(expires Mon, 11 May 2026 06:57:47 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: 0f29ae8ae0bd54a99bf2b223b6833be47acd5943}

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
32981133	Triggered	Generic Private Key	62d9aaf	ca.key	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}