Rework integration docs & add mcp

[mjudeikis]

Summary

What Type of PR Is This?

Related Issue(s)

Fixes #

Release Notes

NONE

[kcp-ci-bot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[kcp-ci-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign embik for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ntnn]

Suggested change

	# Kubernetes MCP Server Helm Values for KCP
	# Kubernetes MCP Server Helm Values for kcp

[ntnn]

Instead of a fixed file a create secret command with --from-literal values instead?
Same in postgres-cluster. I think that's clearer and nicer for users going through the docs and we won't run into the possibility of some codescanning recognizing that as secrets.

[ntnn]

I think we can scrap or shorten listing the types, if we add more it will get very long.

Suggested change

	Each deployment type (dekker, vespucci, comer, zheng) has its own subdirectory with complete configuration files and deployment manifests.
	Each deployment type (dekker, vespucci, ...) has its own subdirectory with complete configuration files and deployment manifests.