doc: Revamped Resource Browser Doc

[ashokdevtron]

Done

• Repurposed the old content and restructured the whole doc
• Shifted node operations from another doc to this
• Removed old cluster doc
• Added gifs wherever possible
• Added videos
• Moved a portion of ephemeral container to this doc
• Added glossary item for 'K8s object'
• Included a guide to download pod log
• Added workload filter and last restart pod log
• Added redirection from old cluster doc to RB doc
• Replaced snapshots of node operations
• Added creatives for easy explanation of node ops
• RBAC
• Proofreading (for grammar and errors)

[abhibhaw]

• RBAC needs to be crosschecked, current mentions concludes, resource browser can only be used by superadmins. (I believe RBAC is pending as per PR description)
• We should attach more reference links to k8s docs

[abhibhaw]

Request someone from @devtron-labs/devops-team to review this doc.

[ashokdevtron]

Request someone from @devtron-labs/devops-team to review this doc.

Reviewed by @ajaydevtron on May 10th

[abhibhaw]

LGTM

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets 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 secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
10220829	Triggered	Generic High Entropy Secret	82cf580	charts/devtron/devtron-bom.yaml	View secret
10220829	Triggered	Generic High Entropy Secret	82cf580	charts/devtron/values.yaml	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 secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
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.}

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud