docs: Guides for popular use-cases

[kostis-codefresh]

Checklist:

• Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this is a chore.
• The title of the PR is (a) conventional with a list of types and scopes found here, (b) states what changed, and (c) suffixes the related issues number. E.g. "fix(controller): Updates such and such. Fixes #1234".
• I've signed my commits with DCO
• I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
• My builds are green. Try syncing with master if they are not.
• My organization is added to USERS.md.

[sonarcloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[github-actions]

Go Published Test Results

2 106 tests   2 106 ✅  2m 50s ⏱️
  118 suites      0 💤
    1 files        0 ❌

Results for commit e3a6f4a.

[github-actions]

E2E Tests Published Test Results

  4 files    4 suites   3h 31m 19s ⏱️
106 tests  95 ✅  6 💤  5 ❌
448 runs  398 ✅ 24 💤 26 ❌

For more details on these failures, see this check.

Results for commit e3a6f4a.

[todaywasawesome]

Excellent 👌