Newer version of Kubernetes support

[patrickshan]

Hi there,

Looking at the Compatibility Matrix, it seems that currently scheduler-plugins only supports Kubernetes version up to 1.27.8. But when I checked the go modules dependency, it seems that it's already using 1.28.4 library. Does that mean current master already supports 1.28 ? How about 1.29 ? Is there any plan to sync with the Kubernetes release ?

Thanks,
Patrick

[Huang-Wei]

Does that mean current master already supports 1.28 ?

Yes, master vendors 1.28, and we treat master as the developer branch.

How about 1.29 ?

I will cut release 0.28 no late than next week. And meanwhile, bump k8s deps on master to 1.29.

Is there any plan to sync with the Kubernetes release ?

We are intentionally making master one release behind the latest release of k8s release.

[patrickshan]

@Huang-Wei thanks for the information. Any link I can read for the reason behind the decision about the third question ? (one release behind the latest release)

[Huang-Wei]

@patrickshan One reason is based on users' demands, i.e., how confident the majority of our users would be if master jump onto latest k8s release immediately when it's released.

The other reason is, the latest release may need some time to soak to reveal issues, which is one another issue staying one release behind is a good choice.

The last reason is b/c of maintainer's bandwith, we don't do backport fixes frequently, so developing on a stable k8s base is critical.

Ref: #503 (comment)

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[Huang-Wei]

It's already completed.