Original issue here: kubernetes/kubernetes#22159

@timstclair it looks like the docs PR number is outdated. Please update the PR number and check the docs box once it's done

Fixed. Thanks @janetkuo !

Docs kubernetes/website#1147 - @kubernetes/docs

Is there an issue? I merged this one in last week.

On Sep 21, 2016 1:30 PM, "Tim St. Clair" notifications@github.com wrote:

Docs kubernetes/website#1147
kubernetes/website#1147 -
@kubernetes/docs https://github.com/orgs/kubernetes/teams/docs

—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub
#24 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARmNwOTArylXQHoAoz2lMTsKhg9luaTYks5qsZPlgaJpZM4JMBOR
.

No, I was just following the instructions at the bottom of the issue, which I hadn't done before...

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

/remove-lifecycle rotten

@tallclair @liggitt
Any plans for this in 1.11?

If so, can you please ensure the feature is up-to-date with the appropriate:

• Description
• Milestone
• Assignee(s)
• Labels:
  • stage/{alpha,beta,stable}
  • sig/*
  • kind/feature

cc @idvoretskyi

/lead-opted-in

/label lead-opted-in

hey @tallclair - sorry, I missed this KEP when scouring the boards earlier in this release cycle. Enhancements freeze is in just a few hours... https://github.com/kubernetes/enhancements/pull/4417/files needs to merge before we can track this towards the release. Do you think that will be possible?

Hello 👋, 1.30 Enhancements team here.

Unfortunately, this enhancement did not meet requirements for enhancements freeze.

This question under scalability is now required in the KEP: https://github.com/kubernetes/enhancements/tree/master/keps/NNNN-kep-template#can-enabling--using-this-feature-result-in-resource-exhaustion-of-some-node-resources-pids-sockets-inodes-etc

If you still wish to progress this enhancement in 1.30, please file an exception request. Thanks!

/milestone clear

@tjons Sorry, I missed your comment on this issue. The KEP in question actually did merge in time for enhancements freeze, unless I mixed up the dates. Does this still need an exception request?

/milestone v1.30

Hello @tallclair 👋, 1.30 Docs Lead here.

Does this enhancement work planned for 1.30 require any new docs or modification to existing docs?
If so, please follows the steps here to open a PR against dev-1.30 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday February 22nd 2024 18:00 PDT.

Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.
Thank you!

The AppArmor docs definitely need a refresh. Most of these changes can be made against the main branch though. There will also be some API updates needed on the 1.30 branch though.

Docs placeholder: kubernetes/website#45176

Hi @tallclair, 👋 from the v1.30 Communications Team! Are you planning to write a blog for this?

We encourage blogs for features including, but not limited to: breaking changes, features and changes important to our users, and features that have been in progress for a long time and are graduating.

To opt in, you need to open a Feature Blog placeholder PR against the website repository.
The placeholder PR deadline is 27th February, 2024.
Here's the 1.30 Release Calendar

Hey again @tallclair 👋 Enhancements team here,

Just checking in as we approach code freeze at 02:00 UTC Wednesday 6th March 2024 .

Here's where this enhancement currently stands:

• All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• All PR/s are ready to be merged (they have approved and lgtm labels applied) by the code freeze deadline. This includes tests.

For this enhancement, it looks like the following PR is open and needs to be merged before code freeze:

• AppArmor fields API kubernetes#123435

Could you please add the above PR to the issue description?

Also, please let me know if there are other PRs in k/k we should be tracking for this KEP.
As always, we are here to help if any questions come up. Thanks!

Updated the issue description with a link to kubernetes/kubernetes#123435. This is currently in the API review queue, scheduled for Thursday.

With the exception request being approved, this can now be marked as tracked for code freeze.

Hey @tallclair - Enhancements team here. Now that this has merged and is on track to be stable in 1.30, would you kindly mark the feature as status: implemented in the associated KEP?

Thank you!

To clarify, we implemented all the planned changes, but decided to hold the feature in beta for another release. Should I still mark it as implemented, or wait for GA?

Ah I understand. In that case wait for GA, thanks!