devtron doc: Revamped Resource Browser Doc

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)

Apr 30 '24 14:04 ashokdevtron

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

May 07 '24 18:05 abhibhaw

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

Reviewed by @ajaydevtron on May 10th

May 14 '24 11:05 ashokdevtron

⚠️ 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	82cf58008c826d3c102a329becd7bcef0aec2c71	charts/devtron/devtron-bom.yaml	View secret
10220829	Triggered	Generic High Entropy Secret	82cf58008c826d3c102a329becd7bcef0aec2c71	charts/devtron/values.yaml	View secret

🛠 Guidelines to remediate hardcoded secrets

Understand the implications of revoking this secret by investigating where it is used in your code.
Replace and store your secrets safely. Learn here the best practices.
Revoke and rotate these secrets.
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.}