Provide a cluster diagnostic tool with best practices, compliance and recommendations

[pbochynski]

Description
Provide a tool that can check cluster configuration and give warnings or recommendations how to make it more secure, follow best practices, and make it production ready.
Example checks:

• mtls is enabled and access to the services is limited (peer authentication)
• logs are pushed outside of the cluster (external service)
• topology spread constraint are used (HA setup of workload)
• pod security standards are enabled
• image signature verification is enabled
• geoblocking
• rate limiting

Reasons
Kyma runtime is flexible and can be fully configured by the user. Can be used for development and for production scenarios. Fast and cost-efficient development settings are not suitable for production systems. Kyma team decided to leave the final decision to the user, but it would be beneficial to give users recommendation how to improve the configuration to make it more resilient, secure, and performant.

[kyma-bot]

This issue or PR has been automatically marked as stale due to the lack of recent activity.
Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

• After 60d of inactivity, lifecycle/stale is applied
• After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Close this issue or PR with /close

If you think that I work incorrectly, kindly raise an issue with the problem.

/lifecycle stale

[kyma-bot]

This issue or PR has been automatically closed due to the lack of activity.
Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

• After 60d of inactivity, lifecycle/stale is applied
• After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle stale

If you think that I work incorrectly, kindly raise an issue with the problem.

/close

[kyma-bot]

@kyma-bot: Closing this issue.

In response to this:

This issue or PR has been automatically closed due to the lack of activity.
Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

• After 60d of inactivity, lifecycle/stale is applied
• After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle stale

If you think that I work incorrectly, kindly raise an issue with the problem.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[tobiscr]

Could be partially addressed (at least in regards for security related improvements) by the ideas bundled in the Kyma Security Module (#internal-backlog/5467).