Centralised Documentation of CNCF-Conformant Kubernetes Distribution Variations in Ports, Paths, and Components

[developer1622]

What would you like to be added?

[existing, however] I propose creating a centralised section in the official Kubernetes documentation that provides a comprehensive table listing CNCF-conformant Kubernetes distributions.

The table should outline key details such as:

Ports used by critical components like etcd, kube-apiserver, and kubelet.
Default PKI certificate paths for each component.
Deviations from standard Kubernetes configurations, if any.

This table would act as a reference for understanding the variations in Kubernetes distributions and help teams build tools and solutions that cater to diverse environments.

Basically a overview of distro given by the distro owners how it deviates from upstream k8s.

Why is this needed?

Monitoring and observability solutions often need to support multiple Kubernetes distributions, each of which might have slight differences in configuration, such as:

Non-standard ports for components like etcd or kubelet(if any).
Different PKI certificate paths for authentication and encryption.
Variations in component behavior or configurations that deviate from upstream Kubernetes.

Currently, there is no centralized place to find these details. This leads to challenges for organizations and solution providers who need to support multiple distributions

By documenting these variations in a standardised table, we can:

Simplify the development and deployment of observability tools across diverse Kubernetes distributions.

Reduce the troubleshooting burden for users and vendors.

Promote transparency and a better understanding of Kubernetes environments.

This enhancement aligns with Kubernetes' ethos of being distribution-agnostic while acknowledging practical deviations in implementations

Thank you.

[k8s-ci-robot]

There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:

• /sig <group-name>
• /wg <group-name>
• /committee <group-name>

Please see the group list for a listing of the SIGs, working groups, and committees available.

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-sigs/prow repository.

[k8s-ci-robot]

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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-sigs/prow repository.

[dims]

/transfer website
/sig docs