Improve Kubernetes agent documentation

What does this MR do?

• unified examples to gitlab-kubernetes-agent as all examples where a mix of gitlab-kubernetes-agent, gitlab-agent & <YOUR_NAMESPACE>
• added # - grpc://host.docker.internal:5005 # use this when connecting from within Docker e.g. from kind to existing examples
• added # - wss://kas.gitlab.com to existing examples
• added section how to remove the agent

Screenshots (strongly suggested)

Does this MR meet the acceptance criteria?

Conformity

• Does this MR need a changelog?
  • I have included a changelog entry.
  • I have not included a changelog entry because this change is docs-only.
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• Tested in all supported browsers
• Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team

@phil.xx

Thank you for your contributions to GitLab. We believe that everyone can contribute and contributions like yours are what make GitLab great!

Our Merge Request coaches will ensure your contribution is reviewed in a timely manner. To learn more about the merge request triage process you can refer to the Wider Community Merge Request Triage page.

To bring your merge request to the attention of the relevant team within GitLab, you can ask our bot to label it with a group label. For example, if your merge request changes a project management feature, it can be labelled by commenting @gitlab-bot label ~"group::project management". To find the most relevant group for your change, you can look up the group based on the most relevant product category in the product categories table. Once you have found the group name, type @gitlab-bot label ~group::, then start to type the group name and select the applicable group label, then submit the comment and the bot will apply the label for you.

If after a few days, there's no message from a GitLab team member, feel free to ping @gitlab-org/coaches or ask for help by commenting @gitlab-bot help.

These resources may help you to move your Merge Request to the next steps:

• Contributing to GitLab
• How to get help
• Ping a Merge request coach

This message was generated automatically. You're welcome to improve it.

added Community contribution label

Hi @marcia, please review this documentation Merge Request.

added documentation twtriaged labels

cc @nagyv-gitlab

added Category:Kubernetes Management groupconfigure [DEPRECATED] labels

added devopsconfigure [DEPRECATED] label

changed title from update-kubernetes-agent-documentation to Improve Kubernetes agent documentation

Context: We tried the Kubernetes agent this week and encountered some blockers which we debugged and resolved in the live stream. Collected details and recording in https://everyonecancontribute.com/post/2021-04-28-cafe-27-gitlab-kubernetes-agent-gitops/

added 1 commit

• 9c31661c - fix markdownlint issues

Compare with previous version

added 1 commit

• 63d2fb56 - remove list Note for GraphQL and add new Note msg

Compare with previous version

added 1 commit

• 2a5d4455 - fix MD031/blanks-around-fences

Compare with previous version

@marcia Content-wise the changes are OK. I don't know if there is any stylistic or other element you would like to ignore. The "Remove the GitLab Kubernetes Agent" section is valuable on its own too.

assigned to @marcia