Kubernetes TLS Community

Welcome to the Kubernetes TLS community!

• Introduction
• Community meeting
• Questions and issues

Introduction

KLTS, known as Kubernetes Long Term Support, has a primary mission to provide free long-term maintenance support for earlier versions of Kubernetes.

Kubernetes versions are expressed as x.y.z, where x is the major version, y is the minor version, and z is the patch version. For the versions maintained by KLTS, it is followed by a string beginning with lts.

Visit klts.io for in-depth information about using KLTS.

Community meeting

Regular KTLS Meeting: Tuesday at 23:00 PT (Pacific Time) (biweekly). Convert to your timezone.

• Meeting notes and Agenda.
• Meeting recordings.

Contact

• slack: klts

• metting: klts

• Open Community Issues/PRs

• Steering Committee Liaison: wzshiming(@wzshiming)

How to add a patch to Kubernetes TLS

step:

1. Modify the release.yaml config to add the patch information, and then add the patch name for any version less than that

2. run make verify-patch command to check whether all patches conflict. e.g.:

make v1.14.10-lts.0

3. If there is a conflict, add the PATH file to the Patches directory as prompted

4. Change the patch name again in release.yaml

5. Execute the following command when the execution reaches the conflict resolution stage：

QUIET=n ./hack/format_patch.sh patches/{{patchname}}.patch

6. Open another terminal, resolve the conflicting files and add them to the repository to ensure git status is clean

7. Go back to the terminal and type y to confirm

Questions and issues

If you have questions or issues with KLTS, You can create issues in the list. Of course, you are familiar with KLTS, you can pick from list to solve. We will be very grateful for this.