Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

1.29 Release Notes: "Known Issues" #121886

Closed
fsmunoz opened this issue Nov 14, 2023 · 5 comments
Closed

1.29 Release Notes: "Known Issues" #121886

fsmunoz opened this issue Nov 14, 2023 · 5 comments
Labels
needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/release Categorizes an issue or PR as relevant to SIG Release.
Milestone

Comments

@fsmunoz
Copy link
Contributor

fsmunoz commented Nov 14, 2023

This issue is a bucket placeholder for collaborating on the "Known Issues" additions for the 1.29 Release Notes. If you know of issues or API changes that are going out in 1.29, please comment here so that we can coordinate incorporating information about these changes in the Release Notes.

/assign @kubernetes/release-team-release-notes

/sig release
/milestone v1.29

@k8s-ci-robot k8s-ci-robot added this to the v1.29 milestone Nov 14, 2023
@k8s-ci-robot k8s-ci-robot added sig/release Categorizes an issue or PR as relevant to SIG Release. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Nov 14, 2023
@k8s-ci-robot
Copy link
Contributor

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/test-infra repository.

@pacoxu
Copy link
Member

pacoxu commented Nov 21, 2023

We also want to highlight that Evented PLEG beta feature that is disabled by default have a critical bug: #121349 (comment) that is not resolved yet. We recommend to use extra caution when enabling this feature.

When enabling EventedPLEG feature gate(beta, default false), a static pod with 1 container may have multiple containers up and one running well and the other failed for port in use or some other issues.

@SergeyKanzhelev
Copy link
Member

From SIG Node, originally posted here:

Evented PLEG beta feature that is disabled by default have a critical bug: #121349 (comment) that is not resolved yet. We recommend to use extra caution when enabling this feature.

@fsmunoz
Copy link
Contributor Author

fsmunoz commented Dec 11, 2023

Closing, release date is near. Please reopen if anything urgent comes up between now and the release.

/close

@k8s-ci-robot
Copy link
Contributor

@fsmunoz: Closing this issue.

In response to this:

Closing, release date is near. Please reopen if anything urgent comes up between now and the release.

/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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/release Categorizes an issue or PR as relevant to SIG Release.
Projects
Archived in project
Development

No branches or pull requests

4 participants