Skip to content
Permalink
master
Switch branches/tags
Go to file
 
 
Cannot retrieve contributors at this time

Enhancements Lead Handbook

Overview

While the Enhancements Lead serves as a member of the Release Team (a subproject of SIG Release), this role is also a liaison to sig-arch-Enhancements subproject of SIG Architecture.

Responsibilities

An Enhancements Lead holds the following responsibilities:

  • Maintain the active status of Enhancements within kubernetes/enhancements
  • Facilitate communication between Enhancement Owners, and SIG leadership, as necessary
  • Collate the major themes of the release, including but not limited to:
    • new enhancements
    • long-awaited enhancements
    • enhancements moving into GA
    • enhancement deprecations
    • notable changes to existing behaviors
  • Assist in Communications activities (in conjunction with the Communications Lead & the CNCF Communications team):
    • Draft and / or review https://kubernetes.io/blog/ release announcement post, leveraging the themes collected across the release cycle e.g., 1.17 Announcement
    • Engage with media analysts during the embargo period to discuss the release themes
    • CNCF Kubernetes Release webinar
    • Identify potential contributors for the “5 Days of Kubernetes” blog series
  • Identify candidates to assume the Enhancements Lead role (according to the Release Team selection process) in the following release cycle
    • Chose Enhancement shadows whom you believe would be a good fit for succession and help mentor them throughout the release cycle

Prerequisites for Enhancements Lead and Shadows

General Requirements

Before continuing on to the Enhancements specific requirements listed below, please review and work through the tasks in the Release Team Onboarding Guide.

Enhancements Specific Requirements

Helpful characteristics of an Enhancements Lead include:

  • experience with the Kubernetes community, code layout, ecosystem projects, organizational norms, governance, SIG structure, architecture, and release process
  • product / project / program management experience
  • release management experience

Time Commitments

Enhancement is one of the most time-intensive areas of the release team, and especially so during the early parts of the release. An Enhancements Lead can expect to spend:

  • Beginning of the cycle through enhancement freeze: ~8–15 hours a week
  • Week of enhancements freeze: 20+ hours
  • Enhancement Freeze through Code Freeze: ~4–7 hours a week
  • Code Freeze through Release Day: ~1–4 hours a week

Note that Enahncements Lead in particular will need to do work during the week during the early release, and will need to be available at least daily.

Enhancements shadows can expect to spend ~10–15 hours a week during the early release until enhancements freeze, and ~1–5 hours a week after enhancements freeze. Unlike Enhancements Lead, shadows can expect to do their work largely on weekends if they desire.

Mentoring Shadows

The selected shadows should be:

  • Interested in learning more about the Kubernetes release process.
  • Able to dedicate a couple hours each week to attending the Release meeting in addition to helping with weekly tasks.

The shadows should be selected keeping in mind that one of them may eventually be taking up the Enhancements Lead role. It is important to delegate tasks and give the shadows broad exposure to the different aspects of the role.

Getting Started

Access Required

Ensure that the previous Enhancements Lead has given you access to:

  • The previous Kubernetes Release Enhancements Tracking Sheet.

Ensure that you and the shadows have been added to:

  • GitHub teams

Slack

Join the following Kubernetes Slack channels:

Process

Standards

As mentioned previously, the Enhancements Lead role encompasses several cross-functional responsibilities with sig-arch-Enhancements subproject of SIG Architecture.

The process of maintaining an enhancement in Kubernetes is documented in the kubernetes/enhancements repo. Any questions / concerns / suggestions for improvement to the Enhancements process should be raised as GitHub issues / PRs to k/enhancements.

It is important that this process be followed and documentation remain up-to-date as the Enhancements repo is the primary ingress point for contributors interested in tracking enhancements.

Milestone Activities + Timing

Note: The week #n timings given below are tentative. There are special releases like Kubernetes 1.19 or releases at the end of the year which may not strictly conform to that.

Pre-Collection (Week 0)

  • Duplicate the previous enhancement collection spreadsheet into your own Google Drive and adjust it for the current milestone. Enhancements Tracking sheet is shortlinked with the pattern k8sxyy-enhancements e.g., http://bit.ly/k8s113-enhancements. Create a free account on bitly to create a shortlink for the new enhancement collection spreadsheet.
  • Clean up the spreadsheet by removing all currently tracked issues from all tabs.
  • Update the permissions on the enhancement collection sheet.
  • Update the permission on the protected sheets on the enhancement collection sheet.
    • For KEP Collection sheet, grant Edit access to the SIG Leads Google Group.
    • For Docs sheet, grant Edit access to Docs Lead and Docs shadows.
  • Make a pull request to add the shortlinked Enhancement Tracking sheet to the current release page in sig-release
  • Find Issues from previous milestone that have graduated to Stable. Remove tracked/yes or tracked/no labels. Check to see if the KEP status has been updated to implemented. If it has, close the issue. If it has not, ask the issue contact to both update the KEP status field and close the Enhancement issue once the update PR has merged.
  • Find Issues labeled tracked/yes and change to tracked/no until the Enhancement is ready to be tracked for the upcoming release.
  • Close previous milestone by ensuring that there are no open issues/PRs in that milestone.
  • Gather Shadows to have them read this handbook and give expectations on what the process looks like and their particular role. If possible, try to schedule a call with the shadows to get them accustomed to the team. This helps as a great team building exercise.

Pre-Enhancements Freeze (Week 1)

  • Send an email to the Kubernetes-Dev mailing list and a message to #chairs-and-techleads slack channel with a call for enhancements and how to opt-in to the release.
  • Verify issues have k/k PRs associated so they can be referenced and easily tracked. This is going to be critical come Enhancement Freeze and Code Freeze to see the status of the code.
  • Work with the Release Lead to introduce yourself, talk about release information, and relay information about opting into the release with SIG Leads.
  • Weekly Release meetings require updates of current status. Use the Feature stats tab to update the release team on counts of enhancements in good and bad progress.

Collection Monitoring and Triage (Week 1-2)

  • Monitor the KEP Collection tab regularly for new additions as SIGs opt-in KEPs into the release.
  • Move data from KEP Collection into the data tab to be tracked officially for the release.
  • Manually add the KEP issue number into the Enhancements tab and verify that the KEP is now included.
    • Entering the KEP issue number will auto populate the Enhancement Name, SIG, KEP Assignee, Proposal, and KEP State.
    • Fill out rest of the column manually based on current status of the KEP.
  • For the opted in issues, apply the correct milestone, tracked/yes label, and stage/xxx label.
  • Start reminding opted in Issue owners that KEPs are required for each enhancement and that KEPs must meet the acceptance criteria (implementable state, graduation criteria, test plan, and production readiness review) by Enhancement Freeze.
  • Stay on top of comments in issues when owners respond and update their status in the sheet if necessary.
  • Mark features as At Risk if there is no communication, active PRs on the issues, or it is missing other requirements coming into Enhancement Freeze.
  • Start syncing with Communications Team on giving an induction what's coming up for the release.
  • Send an email to Kubernetes-Dev that Enhancement freeze is coming and share current Enhancements status. Examples 1.

Enhancements Freeze (Week 3)

  • On Freeze day, send an email to Kubernetes-Dev that freeze has happened and upcoming key dates. Examples 1.
  • Remove SIG Leads Google Group's access to the KEP Collection sheets on the enhancement collection sheet.
  • Remove any enhancements that failed to meet the criteria by the Enhancement freeze deadline.
    • Set their status in the sheet to Removed from Milestone and use the Enhancements -> Remove Enhancements from Milestone menu option to move them over to the Removed from milestone tab.
    • Remove the milestone and change tracked/yes label to tracked/no on the enhancement issue.
  • Clean up Enhancements issues by removing milestone from the enhancements that have not opted-in and make sure that number of in-tree open issues with current milestone matches number of opted-in enhancements.
  • Any enhancements removed from the milestone will now require an exception. As exception requests come in, discuss each with the Release Lead (and Shadows) to arrive at an approve/reject decision.
    • Create an exception file in the Release for exceptions Example 1.
    • If a previously removed Enhancement has had their exception Approved, set their status to Tracked and use the Enhancements -> Track Removed Enhancements menu option to move it back to the Enhancements and Docs tabs.

Post Enhancements Freeze (Week 4–10)

  • Stay on top of issues and continually monitor them twice a week and look at attached PRs. As Code Freeze gets closer, if there are PRs that have not been merged, move the issue to At Risk. If there is no activity, ping issue owners on either the issue or the k/k PR.
  • Monitor issues that are At Risk closely, almost daily. Code Freeze means no new code and keeping tabs on the status of the k/k PR is critical to planning. Make decisions if the enhancement should be deferred and work with SIG Leads to determine the best path forward.

Code Freeze (Week 10+)

  • Remove any enhancements that failed to merge their code by the Code freeze deadline.
    • Set their status in the sheet to Removed from Milestone.
    • Remove the milestone and change tracked/yes label to tracked/no on the enhancement issue.
    • Remove the milestone from all open k/k PRs related to the enhancement.
  • Any enhancements removed from the milestone will now require an exception. As exception requests come in, discuss each with the Release Lead (and Shadows) to arrive at an approve/reject decision.
    • Add a /hold label to k/k PRs associated with incoming exceptions to prevent from accidental merge.
    • Add incoming exception information to the previous created exception.yaml file.
    • If a previously removed Enhancement has had their exception Approved, set their status back to Tracked
  • Start planning for the next release while assisting the Release Lead with anything relating to analytics or Public Relation planning of the release. Work with the Communications Lead to develop major themes for the official Kubernetes blog post.

Working with the Enhancement Tracking Sheet

Cross Release Enhancement Tracking

The source of truth for Enhancements is the data tab within the tracking sheet. All other tabs are driven off the data in this tab. Any changes to the KEP Assignee, KEP owning SIG, KEP link, and KEP state should be done in the data tab.

Column Description
Issue Enhancement Issue Number.
Name Enhancement Issue Name and link. Generated from Issue Number.
Responder Last person to respond on behalf of an Enhancement.
SIG Owning SIG. Generated from KEP path. If no KEP (PR in flight), requires manual entry.
KEP Link to KEP or KEP PR.
KEP State KEP State (Pending, Implementable etc).
Completed in Release The release in which the Enhancement graduated to stable.

Dashboard

The Dashboard tab is intended to be an at-a-glance view of the current Enhancement status from both the perspective of the Enhancements and Docs teams. It is 100% generated from the Enhancements and Docs tabs and should NOT be updated manually.

Enhancement Signal

Enhancements that are missing any criteria should be labeled as At Risk. To help make this easier for the Enhancement team to label. Proposals and KEP State are color coded indicating their current readiness state.

  • Proposal
    • #B7E0CD KEP is merged
    • #FCE8B2 KEP PR in flight
    • #F4C7C3 No KEP or KEP PR found
  • KEP State
    • #B7E0CD Implementable or Implemented
    • #FCE8B2 Provisional
    • #F4C7C3 none or invalid

Removing Tracked Enhancements

If the Enhancement is being bumped to a later release, set it's state to Deferred.

If it is being removed due to missing criteria or lack of response after being included in the milestone, set its state to Removed from Milestone.

Once done, use the Enhancements -> Remove Enhancements from Milestone menu item to automatically to move it to the Removed from Milestone tab removing it from the Dashboard, Enhancements and Docs tabs.

Moving a Removed Enhancement Back into the Milestone

If a removed item has had an exception granted. Set it's status to Tracked in the Removed from Milestone tab. Then use the Enhancements -> Track Removed Enhancement menu option to move it back to the Dashboard, Enhancements, and Docs tabs.

Tips on judging Stage Status

  • If the feature is graduating to Alpha, the status can either be Net New/Major Change. But usually when features are introduced to Kubernetes, they are not Major Changes.
  • If the feature is graduating to Beta/Stable, almost always the state is Graduating/Major Change. One exception to that is some features directly jump the hoop to Beta, in that case, the status can be Net New for even a Beta feature.

Feel free to ask the previous enhancements leads about this when in doubt.

Escalation / Handling Unresponsive Enhancement Owners

For issues where the initial owner is unresponsive, try escalating to the relevant SIG's leadership to determine if the issue is still targeted for the release.

If there is continued unresponsiveness on issues, remove them from the milestone at your discretion.

Exceptions

Exception process is outlined here

CNCF / Media Engagement

  • You may be called upon by the communications lead to help with media engagement near the end of the release cycle. Please ensure that if there are any restrictions or training required by your company before engaging that you have completed those ahead of Code Thaw.

Succession

  • Select who will be the new enhancement lead for the next release. Shadows should be the first source pool. If none are available to lead then look externally through other release team members or members of SIG Architecture Enhancements Subproject
  • Enhancements Tracking sheet is shortlinked with the pattern k8sxyy-enhancements e.g., http://bit.ly/k8s113-enhancements
  • Continually work to improve Enhancements process
  • Review / update documentation as the release cycle ends
  • Close issues marked as stable that made it into the release, only after the corresponding KEPs have been marked Implemented
  • Close milestones that are complete
  • Cleanup old milestones

Limitations

Signals

Tips & Tricks

Sample Searches (examples)

GitHub Notifications

https://groups.google.com/forum/#!topic/kubernetes-dev/5qU8irU7_tE