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

Changelog-1.25: add 1.25.0 known issues section #112106

Merged

Conversation

kikisdeliveryservice
Copy link
Member

@kikisdeliveryservice kikisdeliveryservice commented Aug 29, 2022

  • Add known issue affecting LocalStorageCapacityIsolationFSQuotaMonitoring

What type of PR is this?

/kind documentation
/kind regression

What this PR does / why we need it:

Need to document the reversion of LocalStorageCapacityIsolationFSQuotaMonitoring from beta to alpha
Reverted in master via: #112076
Reverted in 1.25 via: #112078
Open k/k tracking issue for bug: #112081
Related enhancement: kubernetes/enhancements#1029

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


@k8s-ci-robot k8s-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. kind/documentation Categorizes issue or PR as related to documentation. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. kind/regression Categorizes issue or PR as related to a regression from a prior release. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Aug 29, 2022
@k8s-ci-robot
Copy link
Contributor

@kikisdeliveryservice: 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.

@k8s-ci-robot k8s-ci-robot added needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. labels Aug 29, 2022
@k8s-ci-robot k8s-ci-robot added area/release-eng Issues or PRs related to the Release Engineering subproject sig/release Categorizes an issue or PR as relevant to SIG Release. and removed do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Aug 29, 2022
- Add known issue affecting LocalStorageCapacityIsolationFSQuotaMonitoring
@kikisdeliveryservice
Copy link
Member Author

@pacoxu @rphillips PTAL and lmk if you'd like any updates to the wording :)

@cici37
Copy link
Contributor

cici37 commented Aug 29, 2022

/cc

@k8s-ci-robot k8s-ci-robot requested a review from cici37 August 29, 2022 21:23
@pacoxu
Copy link
Member

pacoxu commented Aug 30, 2022

@pacoxu @rphillips PTAL and lmk if you'd like any updates to the wording :)

I am still working on the bug reproduction and fix.

The description is LGTM.

@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Aug 30, 2022
@kikisdeliveryservice kikisdeliveryservice changed the title [WIP] Changelog-1.25: add 1.25.0 known issues section Changelog-1.25: add 1.25.0 known issues section Aug 30, 2022
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 30, 2022
@kikisdeliveryservice
Copy link
Member Author

@rphillips PTAL

@kikisdeliveryservice
Copy link
Member Author

Kep is also being updated: kubernetes/enhancements#3485

@cici37
Copy link
Contributor

cici37 commented Sep 1, 2022

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Sep 1, 2022
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cici37, kikisdeliveryservice

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 2, 2022
@k8s-ci-robot k8s-ci-robot merged commit c250da1 into kubernetes:master Sep 2, 2022
@k8s-ci-robot k8s-ci-robot added this to the v1.26 milestone Sep 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/release-eng Issues or PRs related to the Release Engineering subproject cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/documentation Categorizes issue or PR as related to documentation. kind/regression Categorizes issue or PR as related to a regression from a prior release. lgtm "Looks good to me", indicates that a PR is ready to be merged. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. release-note-none Denotes a PR that doesn't merit a release note. sig/release Categorizes an issue or PR as relevant to SIG Release. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants