kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
community/sig-release/meeting-notes-archive/2021.md

110 KiB
Raw Permalink Blame History

December 14, 2021 - Async meeting via Slack

Topics [timebox to 20 min]:

  • [Rey] Release team selection process - GH discussion
    • Common themes as highlighted by James:
      • Reduce the volume of shadows by attaching additional criteria, e.g., "need at least one contribution already".
      • Implement a long-term application tracking process, and reach out to repeat applicants in some way.
      • Maintain a stable release team "roster" from which release teams are built. Select fewer shadows to compliment "roster" folk each cycle, and give shadows the chance to join the "roster" after one or two cycles.
      • Proactively increase diversity in applications, e.g., outreach, refine role handbooks, publicize success stories.
      • Add video call interviews for shadow applicants.

November 30, 2021 (recording)

Host: Sascha Grunert

Attendees (pronouns):

  • Nabarun Pal (he/him)
  • Rey Lejano (he/him)
  • James Laverack (he/him)
  • Meha Bhalodiya (she/her)
  • Jim Angel (he/him)
  • Adolfo García Veytia (he/him/él)
  • Verónica López (she/her)

Note Taker:

  • Rey Lejano

Topics [timebox to 20 min]:

  • Welcome any new members or attendees
  • Subproject updates
  • Roadmap and Vision update:
    https://groups.google.com/g/kubernetes-dev/c/0vagxffQ6j4/m/s65AfYNFBgAJ
    • SLSA compliance: https://github.com/kubernetes/enhancements/pull/3051
    • Signing release artifacts: https://github.com/kubernetes/enhancements/pull/3061
    • [Sascha] Goal is to merge both KEPs before Christmas, encourage reviews and need support from the whole SIG. Next goal is to integrate signing of release artifacts, not completely clear how we will do that, we will experiment with container image signing
    • [Adolfo] SLSA KEP received comments from Tim and will look and address. Lagging a little behind with signing artifacts since the initial technologies that were initially talked about are no longer in use
    • [Veronica] Familiar with SLSA compliance framework, not sure where this is at, at this point, does the main effort on SIG Release?
      • [Adolfo] After a few discussions and trials in code, suggesting as a SIG to use cosign and implement SLSA framework. Have had discussions and see consensus see most momentum with cosign and SLSA. The KEPs are open for comments and suggestions. This is a decision which technologies to use and framework we’re adopting. As a SIG we’ll own the implementation.
      • [Sascha] SIG Release is main owner, maybe SIG Testing with technical details
      • [Adolfo] Asked feedback from SIG Security but SIG Release will be driving the KEPs
      • [Sascha] We can carve out follow-ups to the KEPs
      • [James] Asking for a call to action
      • [Sascha] First thing is to merge KEPs
  • [Marko, Nabarun, Adolfo] 1.23 merges + cherry picks
    • [Adolfo] Background, before 1.19 to make branches even, a release manager would do a ff. In 1.19 a decision was made to stop doing ff when PRs didn’t have proper checks and milestones. So in 1.19 we require PR authors to file a cherry-pick besides their feature PR. Today when submitting a PR, submit a cherry-pick to the release branch e.g. release-1.23. The decision was not well communicated. For 1.21 and 1.22, people did not know this process existed. We expect PR authors to follow with cherry-picks, even now in 1.23 we see some confusion.
    • [Veronica] Saw that 1.21 and 1.22, people were unaware of the change. This topic was set for a bigger discussion. We would like some input from the release team
    • [Nabarun] Just checked the master branch, there were 3 PRs merged, we can do the cherry-picks ourselves for 1.23 as we did this for 1.22 and 1.21.
    • [James] What’s the history
    • [Sascha] We want to reduce tooling effort, minimize time between Code Freeze and Thaw (down to 2 weeks), and create branch with RC. Benefits is a short period where k/k master is frozen. Same process as cherry-picking to a release-branch for a patch release. With FFs we have to maintain tools and documentation. For now, we can watch the master branch merges and we can ask PR authors to make cherry-pick PRs or we make them manually.
    • [James] Are we trying to reducing Code Freeze more?
    • [Sascha] Idea is not to block the master branch, PR authors would have to cherry-pick
    • [Adolfo] In 1.22, when some objections were raised about the cherry-pick requirements, Adolfo looked at the history of the decision and sent an email to the community
      https://groups.google.com/g/kubernetes-dev/c/NiKByLbWZ1g/m/GYhi_Ip3BAAJ
    • [Adolfo] For 1.24, we should establish a roadmap. It’s not currently in the Branch Manager handbook
    • [Veronica] Should we continue with cherry-picking?
    • [Marko] Discussion with Jordan, cherry-picking is a manual step and can be forgotten.
    • [Sascha] Doing cherry-picks is more manual process
    • [Sacha] For now, we can’t change the process, we can write another summary to k-dev and sig-release and the Branch Managers are watching what is merged to master branch and PR authors should make a corresponding cherry-pick PR
  • Publishing bot issue: https://github.com/kubernetes/release/issues/2337
    • [Marko] Tags are missing for 1.23.0-beta.0 and 1.23.0-rc.0. Publishing bot failed to add new tag. Reason is that the master branch for staging repos like kubectl/client-go is missing a commit. Publishing bot does not know how to handle the tree when we build when we push the release. In June, we changed the process and don’t rebase instead we do merge commits. Others (Dims, Nikhita, et. al.) are trying to fix this and trying to push the missing commits. They suggest to us that we should look at the process with merge commits.
    • [Sascha] Don’t understand what caused the missing commit. Any issues with the release? Did we have to retry?
    • [Marko] Not sure and have to check
    • [Adolfo] Why did it happen on the beta release?
    • [Marko] We probably had many commits and it triggered this behavior, we can investigate more
    • [Nabarun] When the publishing bot runs, it found commit from where 2 different branches forked. We’re not using the parent master as the parent. When we push our changes, instead of pushing to master, we can raise a PR so it goes through usual work flow. So it has the right parent commit and the publishing bot has the right parent commit.
    • [Sascha] Agree that the publishing bot doesn’t see the right parent commit, creating a PR is a good process. The release tag should land on master after the release is done
    • [Marko] We shouldn’t have a problem with release branches, master is an issue since we do multiple releases with multiple patch releases. The PR idea is a probably a good one
    • [Sascha] Let’s follow up on the issue

Walk the Board [timebox to 20 min]:

**
Open Discussion [timebox to 5 min]**

  • (feel free to add any topics you’d like to discuss, even when they came up during the meeting)

November 02, 2021 (recording)

Host: Jeremy Rickard

Attendees (pronouns):

  • Sascha Grunert (he/him)
  • Rey Lejano (he/him)
  • Verónica López (she/her)
  • Nabarun Pal (he/him)
  • Priyanka Saggu (she/her)
  • Eddie Zaneski (he/him)

Note Taker:

  • Rey Lejano

Topics [timebox to 20 min]:

  • Welcome any new members or attendees
  • Subproject updates
  • Release team selection process GitHub Discussion 1714
    • Should have a few actionable items
    • Summarize high level points in the discussion and send to the SIG Release mailing list
  • Mid-cycle shadow surveys
    • About 50% shadows completed the survey
    • Will add several relevant topics to the release retro
  • (feel free to add any topics you’d like to discuss as part of the agenda)

Walk the Board [timebox to 20 min]:

**
Open Discussion [timebox to 5 min]**

  • (feel free to add any topics you’d like to discuss, even when they came up during the meeting)

October 19, 2021 (recording)

**Host: **Adolfo García Veytia (@puerco)

Attendees (pronouns):

  • Rey Lejano (he/him)
  • Shivanshu Raj Shrivastava (he/him)
  • Marko Mudrinić (he/him)
  • Arsh Sharma (he/him)
  • Nabarun Pal (he/him)
  • Pravar Agrawal (he/him)
  • Eddie Zaneski (he/him)
  • Joseph Sandoval (he/him/él)
  • Sascha Grunert (he/him)
  • Meha Bhalodiya (she/her)

Note Taker:

Topics [timebox to 20 min]:

Walk the Board [timebox to 20 min]:

**
Open Discussion [timebox to 5 min]**

October 5th, 2021

Host: Jeremy Rickard

Attendees (pronouns):

  • Rey Lejano (he/him)
  • Arsh Sharma (he/him)
  • Joseph Sandoval (he/him)
  • Sascha Grunert (he/him)
  • Nabarun Pal (he/him)
  • Appu Goundan (he/him)
  • Stephen Augustus (he/him)
  • Chun Wu (he/him)
  • Pravar (he/him)

**Note Taker: **Joseph Sandoval

Topics [timebox to 20 min]:

  • Welcome any new members or attendees:
    • Appu Goundan (loosebazooka)/Google software supply security.
      • Works on building audit trails with build and releases.
  • Subproject updates
  • Follow up to Releasing and versioning kubectl independently
    • Discuss what coordination is needed
      • Discuss where things will go
      • Who will have access to repos
    • Draw inspiration from Kops?
    • Kubeadm issue: https://github.com/kubernetes/enhancements/issues/1424 (Nabarun) How do we build Kubeadm after it's out of tree? How do we know how to build the binary? Small KEP to move out code generator (https://github.com/kubernetes/enhancements/pull/1252/files) . It raised the issue “what is versioning schema?”. Now if they move to a new tagging schema. (https://docs.google.com/presentation/d/1Utf8NgLZTrS8FmVoU6dZN3siewjGOwvTmFcsJ6vgQLI/edit#slide=id.p) Currently we have our own shell scripts and localized knowledge of the process. Move out the business logic but leave the entry point. Will that be ok? We move all traces of source code. What version, how do want to build? After Kubectl then expect Kubeadm to be next. How do we ensure the bump we do passes all the tests? How do we run the tests?
    • [Stephen] Probably time to make decisions about path we go. One state could be a build system where we input shas and that is your release. Should think about the value of only partially removing (i.e. leaving cmd/ in k/k?).
    • [Stephen] What do we do for last mile of the release - binaries we are producing don’t require container images, but require debs/RPMs (kubectl and kubeadm), which means they need to be in the same spot-ish or play nicely with packaging tools. Not difficult, just pointing to multiple repos.
    • [Stephen] versioning - probably easiest to break away from k/k versioning. Look at cluster autoscaler azure?
    • [Stephen] then the question: how do we build it. Each repo could have own build scripts, but things should get to same place via artifact promo or into same staging bucket. Who is in control - is it shared? We don’t want to own repos we don’t need to. Where build happens should be toward portion we control. Cri tools/etcd/cni plugins => examples where repo external to project but we consume staged artifacts and control to make sure build is promoted, maintaining that pattern seems reasonable. Prow has support for skew testing already, we can work matrix
    • [Nabarun] Q: SIG owns code, do we own build scripts or do we own a contract they follow?
    • [Stephen] We own contracts - produce artifacts, outside of pre-submits should have CI jobs running that represent the expected state (e.g. expected state is to be in a bucket and test should see if it’s in a bucket)
    • [Nabarun] Eventually we won’t have the code (for kubectl)
    • [Stephen] We ensure the artifact ends up somewhere (e.g. in a bucket) and a subsequent part of release that picks it up from a staging bucket to a production bucket. We remove the need to vendor it in the core code. Only care that the artifacts get to where they need to. Today there is no explicit requirement for kubectl to be released when core components are released.
    • [Stephen] Better that out-of-tree components don’t follow release cadence
    • [Nabarun] Will SIG Release help them or how do they get help from us
    • [Stephen] Artifact promotion - https://github.com/kubernetes/k8s.io/tree/main/artifacts. This link should be enough for people to start on artifact promotion - used by kops
    • [Jeremy] Good opportunity to help SIG CLI and volunteer to help
    • [Stephen] Give cleanup of file promotion bits around validation to Jeremy from Adolfo
    • [Stephen] Would like to get some baseline validation in, start with repos that we co-own. Would like to prove the process with cri tools and cni plugins (had issues defining their release process) and pull releases and move to staging buckets and issue promotion PRs like how we do for krel promote-images. As we prove this out for repos that we need for the release, then roll out to others
    • [Stephen] As we’re heading to KubeCon, next release engineering meeting is cancelled. Nabarun is sort-of point for kubectl out-of-tree and suggest to take notes to Q & A, and we can build a timeline.
    • [Nabarun] We will start a kep on this and formalize thoughts. Lubomir also had thoughts because kubeadm is also up to be moved out-of-tree.
    • [Stephen] We should do one first (kubectl) and apply practices to the next one (kubeadm)
    • [Stephen] Suggest to publish Q & A before the kep and use it for the kep
  • [Adolfo] Release cherry-pick deadline falls in KubeCon week, should we send advance notice or move it
  • [Jeremy] Bump it for a week and send notice

September 21st, 2021 Recording

**Host: **Jeremy Rickard

Attendees (pronouns):

  • Rey Lejano (he/him)
  • James Laverack (he/him)
  • Maciej Szulik (he/him)
  • Taylor Dolezal (he/him)
  • Max Körbächer (he/him)
  • Joseph Sandoval (he/him/él)
  • Chun Wu (he/him)
  • Mostafa Elmenbawy (he/him)
  • Bhargav Krishna (he/him)
  • Pravar Agrawal (he/him)

Note Taker:

  • Rey Lejano

Topics [timebox to 20 min]:

  • Welcome any new members or attendees
    • Bhargav Krishna, joined yesterday
    • Chun from Apple, applied to be a shadow but was not selected
    • Maciej, SIG Apps and SIG CLI lead, works at Red Hat works in CLI and controllers
    • Pravar works at IBM in India started to make contributions to SIG Scheduling and scheduling code
  • Subproject updates
  • [eddiezane, soltysh] Releasing and versioning kubectl independently
    • [Maciej] Short idea, we’ve had staging for a long time, kubectl and is one of the projects/subprojects interested in being part of a separate repo and they are already syncing the code and the last bit is figuring out how to release kubectl outside of k8s, the goal is to release kubectl faster than k8s. The first goal is to align them and make the kubectl release go faster.
    • [Jeremy] We haven’t done anything outside of k/k in terms of the core artifacts. This is an area to collaborate.
    • [Maciej] For a period of time, may have to release kubectl artifacts in k/k and in their own repo
    • [Maciej] Already have a KEP to move kubectl related code to staging, either update this KEP or create a follow-up KEP. Is releasing in a separate repo an issue?
    • [Jeremy] We need to follow-up on this, is there a GH issue
    • https://github.com/kubernetes/enhancements/issues/1020 (old KEP)
    • https://github.com/kubernetes/enhancements/tree/master/keps/sig-cli/1020-kubectl-staging (KEP)
    • [Maciej] Since KEP only talks about a move to staging, have to create a follow-up on moving to another repo. Will sync with Eddie to create the enhancement issue and start to sketch out the follow-up KEP
  • [James Laverack] Release team selection improvements for future releases.
    • [James] Start a conversation before the start of 1.24, we’re outgrowing the existing shadow mentoring process. It’s a victim of its own success, had ~185 shadow applications, and have ~24-30 spots. Need to provide more consistency to have people come back more consistent, and have a better process to apply. Max has a diagram of an idea
    • [Jeremy] Worth re-visiting this and make improvements. It’s difficult for applicants who applied multiple times. We talked about this in the 1.22 retro part 2, first start a GH discussion in the SIG Release repo and start collecting thoughts and diagrams like the one Max made. We can start there, start with the known state and work in the open. Don’t have good suggestions on what it should look like. Applications will continue to grow. Once concern, is we don’t get the long term succession planning out of it like we had in the past. For 1.23 we had challenges to get role leads staffed. We need a better way to back-fill. Like we got Karen Chu who was a previous lead, we need to identify better reach-back policy.
    • [Taylor] There’s some merit, in the rejection letters it gives people opportunities to jump into things in the projects so we may be able to reach out to SIG leads if they’re looking for someone
    • [Joseph] It’s a good problem we had, maybe SIG Contribex can help with this, is there a way to channel energy from the release team to other places. Some people need more than bread crumbs.
    • [Taylor] There’s an issue from onboarding and something comes up like burnout or something else comes up.
    • [Veronica] One of the reasons is lack of processes or lack of robust documentation, can see new people come in, it’s hard to start working in this project who is new. In all areas of SIG Release, documentation can be better. Do an iterative process of people who are shadows can leave documentation in a better state, document own process on how they learned things
    • [Taylor] Maybe have documentation in easy-to-ingest format like Google slides
    • [Jeremy] Couple of parallel issues: selection process and onboarding/training/documentation available. Worth starting a GH issue and make some concrete action items / selection process
    • [AI - James] To start with a GH issue about selection process (EDIT: GitHub discussion opened https://github.com/kubernetes/sig-release/discussions/1714)
    • [AI - Jeremy] To start with a GH issue about documentation/onboarding/training and work with Rey and Veronica
  • [Taylor Dolezal] Zoom/Splain/YouTube integration is back on track!
    • Meetings will now upload to YouTube, but do require setting live and adding to the SIG Release playlist (which I or the YouTube admins can assist with).
    • Currently working through the SIG Release backlog of uploads.
    • [Taylor] Issue with recorded meetings weren’t not pushed to Youtube, the integration used is called Splain. Integration setup was fine, what changed is when we changed to GSuite email address, so needed to remove integration and re-create integration. Does not associate the video to a playlist and integration sets the video to private. After meetings Taylor can set the video to public and put the video in the right playlist manually

Walk the Board [timebox to 20 min]:

**
Open Discussion [timebox to 5 min]**

  • (feel free to add any topics you’d like to discuss, even when they came up during the meeting)

September 7th, 2021

**Host: **Jeremy Rickard (he/him)

Attendees (pronouns)

  • Sascha Grunert (he/him)
  • Rey Lejano (he/him)
  • Marko Mudrinić (he/him)
  • Anubhav Joshi (he/him)
  • Subhrodip Mohanta (he/him/his)
  • Debabrata(he/him)
  • Mostafa Elmenbawy (he/him)

Note Taker:

  • Rey Lejano (he/him)

Topics [timebox to 20 min]:

Walk the Board [timebox to 20 min]:

**
Open Discussion [timebox to 5 min]**

  • (feel free to add any topics you’d like to discuss, even when they came up during the meeting)

August 24th, 2021

**Host: **Jeremy Rickard (he/him)

Attendees (pronouns)

  • Sascha Grunert** **(he/him)
  • James Laverack (he/him)
  • Nabarun Pal (he/him)
  • Marko Mudrinić (he/him)
  • Adolfo García Veytia (he/him)
  • Savitha Raghunathan (she/her)
  • Rey Lejano (he/him)
  • Kunal Verma (he/him)
  • Arnaud Meukam (he/him)
  • Mritunjay Sharma(he/him)
  • Jesse Butler (he/him)
  • Joseph Sandoval(he/him/él)

Note Taker:

  • Rey Lejano

Topics [timebox to 20 min]:

Walk the Board [timebox to 20 min]:

**
Open Discussion [timebox to 5 min]**

  • (feel free to add any topics you’d like to discuss, even when they came up during the meeting)

July 27, 2021

Host: Jeremy Rickard

Attendees:

  • Rey Lejano
  • Nabarun Pal
  • Taylor Dolezal
  • James Laverack
  • Sascha Grunert

**Note Taker: **Rey Lejano

Topics [timebox to 20 min]:

  • Welcome any new members or attendees
    • Welcome to Rishabh Jain! Worked on local up cluster script to have it work on MacOS
  • Subproject updates
    • Release Engineering (https://github.com/orgs/kubernetes/projects/30)
      • [Adolfo] Cherry-picks: master branch & 1.22 branch divergent, in 1.19 stopped fast-forwards and now have any changes in master to cherry-pick in the release branch. There was some confusion and some PR authors are not aware that they should raise to cherry-pick after the PR merged so the master & 1.22 branches diverged. In 1.21, Nabarun filed a chunk of cherry-picks to make sync the branches. Plan to communicate when adding PRs to the 1.22 milestone then file a cherry-pick
      • [Nabarun] For the current set of diffs, should we file cherry-picks on our end since cherry-pick approvers are the release managers themselves as a one-time thing to get the cherry-picks done.
      • [AI] Nabarun volunteers to file cherry-picks
      • [Adolfo] Yesterday, Nabarun created a diff of commits. Adolfo will link the Slack thread to this agenda. There is a problem re-generating the test jobs when we create a new branch, the test generation scripts are outdated and may have a bug. Aaron C. has cleaned up the script but the script is still buggy. Request for others to take a look.
    • Release Team (https://github.com/orgs/kubernetes/projects/29)
      • 1.23 Release Formation
        • Congrats and thank you to Rey for picking up the 1.23 lead role
        • Jeremy will be EA
        • Looking to fill comms still
          • Reached out to a few people
        • Shadow application is open
          • 21 Responses so far
        • [James] There is a PR in flight to update hours for Enhancements shadows. The 1.23 Enhancments lead, Xander, is aware of this PR
          https://github.com/kubernetes/sig-release/pull/1581
  • Recording publish automation
    • Jeremy has been trying to upload videos but it’s not great/efficient
    • We need to reach out to YouTube admins/ContribEx (?) to see if we can get splain configured
    • Probably need zoom creds (Stephen?)
      • [Taylor] Taylor is a YouTube admin, log into YouTube with the creds from Stephen. Splain does break often like have to re-run the webhook, haven’t found an alternative to Splain.
      • [Jeremy] Jeremy has been downloading/uploading manually
      • [AI] Taylor to connect with Stephen

Walk the Board [timebox to 20 min]:

**
Open Discussion [timebox to 5 min]**

July 13, 2021 (recording)

Host: Carlos Panato

Attendees:

  • Rey Lejano
  • Sascha Grunert
  • Stephen Augustus
  • Marko Mudrinić
  • Adolfo García Veytia
  • Jeremy Rickard
  • Chris Negus
  • James Laverack
  • Joseph Sandoval
  • Pushkar Joglekar (PJ)

Note Taker:

  • Rey Lejano

Topics [timebox to 20 min]:

  • Welcome any new members or attendees
    • PJ is from SIG Security
  • Subproject updates
    • Release Engineering (https://github.com/orgs/kubernetes/projects/30)
      • [Adolfo] Main issue going on, seen updates in testing-infra repo but haven’t been able to follow closely
        • [Stephen] Currently in process to move from Google infra to community-owned infra, next thing working on is way we interact with artifacts like version markers (text-based API) that shows where the artifacts are based on the version. In the background, moving from Kubernetes-release-dev bucket (Google owned bucket) to K8s-release-dev bucket which is a community-owned bucket. There are changes from doing the build jobs. Previously had krel CI build jobs and they are running in parallel with new bootstrap jobs. Making sure everything is pointed to new community-owned infra. Cluster API Azure jobs are cleaned up, kops jobs need to be cleaned up
      • [Stephen] go1.16.6 / go1.15.14 security updates
        • Marko on point, Veronica + Mengjia shadowing
        • Slack thread: https://kubernetes.slack.com/archives/CJH2GBF7Y/p1626164119119300
        • [Stephen] Will cut a release, in the tracking issue Marko to add get people access to repo infra. For 1.19, need to bump repo definitions to point to go sdk versions. We’ll continue to bump repo definitions until it’s phased out
      • [Stephen] Tyler / Linus

        • [Stephen] Tyler is an intern at Google, working on quality of life on image promotion. Tyler removed bazel. Since bazel is gone, Stephen will bring back any promotion based things backed into the repo. Proposed repo name is sigs.k8s.io/kpromo.

        • [Adolfo] Saw an issue from Linus about improving tools for image promoter. Stephen brought old tools to a legacy folder to check which tools should still be used.

        • [Adolfo] Yesterday, last building PR for bom tool merge, posted in Twitter about artifacts we are producing. Request to review build of materials.
          https://twitter.com/puerco/status/1414784210800422929
          Please comment on the epic if you have any thoughts: \

          • [Stephen] Compare results of tools, find a new name for bom

        • [Stephen] https://github.blog/2021-06-21-github-packages-container-registry-generally-available/

          • Potential discussion on where we put artifacts like where we put boms
    • Release Team (https://github.com/orgs/kubernetes/projects/29)
      • Tracking 56 Enhancements post Code Freeze
        • Enhancements: Status Yellow
        • CI Signal: Status Yellow
        • Bug Triage: Status Yellow
        • Docs: Status Red (based on two missing placeholder PRs)
        • Release Notes: Status Green
        • Comms: Status Green
      • 1.22.0-beta.2 release cut is happening today!
      • Test Freeze - July 15th (This thursday)
    • Release Engineering - patch releases this week - https://kubernetes.io/releases/patch-releases/#1-21
  • [PJ] Identify contributor(s) to give a deep dive / code walkthrough about container images in k/k during sig-security-tooling subgroup meeting on 07/20 (8:30-9:15 AM PST)
  • [Jeremy] Release Cadence Change blog PR: https://github.com/kubernetes/website/pull/28912
  • (feel free to add any topics you’d like to discuss as part of the agenda)

Walk the Board [timebox to 20 min]:

**
Open Discussion [timebox to 5 min]**

(feel free to add any topics you’d like to discuss, even when they came up during the meeting) \

June 29, 2021 (recording)

Host:

Attendees:

  • Sascha Grunert
  • Marko Mudrinić
  • Carlos Panato
  • Chris Negus
  • Derrik Campau
  • Supriya Premkumar
  • Adolfo García Veytia

Note Taker:

Topics [timebox to 20 min]:

  • Welcome any new members or attendees
    • No new members
  • Subproject updates
    • Release Engineering (https://github.com/orgs/kubernetes/projects/30)
      • [Carlos] No particular update.
      • [Sascha] No issues encountered during recent releases
      • [Adolfo] Finished writing out all of the bugs that surfaced during the 1.22-beta.0 wrt the SBOM work. Biggest was a problem with versioning with Go packages inside Google Cloud Build. During this week and next week, plan to present the final proposal for the architecture of the SBOM work. Contact Adolfo if you want to help.
    • Release Team (https://github.com/orgs/kubernetes/projects/29)
      • Monday-Wednesday-Thursday burndown meetings have started.
      • Tracking 71 enhancements.
        • Alpha: 28
        • Beta: 26
        • Stable: 14
        • Deprecation: 3
        • At risk: 43 (code not complete)
      • Call for Exceptions email was sent yesterday
      • Code freeze is on July 8th
      • Tracking 12 feature blogs. Deprecation announcement discussion is happening here - https://github.com/kubernetes/sig-release/discussions/1606. Please feel free to add your thoughts.
      • Release docs status: GREEN
        • Integration branch is healthy again, PR that fixes the conflicts and syncs the branch has been merged.
        • There are 42 enhancements that need docs, 11 Drafts, 10 ready for review and 5 merged.
  • [Kirsten/Anna/Savitha/Divya]: We’d like to kick off a discussion and gather thoughts: re: exception deadlines. Exceptions can come in at any point after the freeze(specifically enhancements), the release might benefit from adding some more formalized guardrails to the process taking into the consideration of timing, priority and impact of enhancements exceptions that come after the freeze.
    • [Derrik] Concerns around consistency between release teams. This discussion was triggered by a very late exception request in the 1.22 cycle.
    • [Adolfo] Is the problem that things are not well defined?
    • [Derrik] It has knock on effects on teams like enhancements and docs.
    • [James] For enhancements we do a bunch of checks running up to code freeze. A late enhancement misses that. Additionally Is time since the deadline a factor in deciding on an exception request? Would we entertain a request for an enhancements freeze exception the day before code freeze?
    • [Derrik] Community concerns that with a longer release if you miss it, then your work is pushed out quite far (4 months!). Maybe just a perception concern.
    • [Sascha] All exceptions are case-by-case. Will more processes improve things? How long does the release team have to respond to exception requests, should there be an SLA on that?
    • [Adolfo] Where is best to discuss this? Slack? Release retro? GitHub? KEP?
    • [Sascha] Avoid a KEP for now, a lightweight discussion on GitHub is preferable.
  • (feel free to add any topics you’d like to discuss as part of the agenda)
  • [Chris] We’re pinging enhancements to open docs PRs. Not everyone has done it yet.

Walk the Board [timebox to 20 min]:

  • Project board review: https://github.com/orgs/kubernetes/projects/23
    • k/k 102822 — assign to Carlos
    • k/sig-release 1595 — assign to Adolfo
    • k/sig-release 486 —
      • [Sascha] Maybe too broad in scope?
      • [Adolfo] Needs to be developed further before we can take a concrete action
    • k/k 72871 — Move to release engineering
    • k/k 72638 —
      • [Adolfo] We should keep an eye on this, but it’s up to each project to work this out. Should we take this on? Can we add a “parked but keep an eye on” column to the SIG Release board?
      • [Sascha] We can put it into the backlog. We’ve triaged it multiple times.
    • k/k 45506 — Probably not relevant for us, assign to Adolfo to take a look later.
    • k/k 49313 —
      • [Adolfo] We’re more a consumer of those tests and beneficiary of their output. This is more of a SIG testing thing.
      • [Sascha] Agree. Why is it on our (SIG Release) board? Looks like we’re searching for a technical solution, so more of a SIG Testing problem.
      • [Adolfo] Another one to watch and keep track of, but not do anything with. Backlog it for now.
    • k/k 91570 — The issue is closed, so remove it from our board.
    • k/sig-release 1389 —
      • [Adolfo] This is related to branch protection. No effort around that right now to my knowledge. Already stale too. Removing stale so we can work on this in the future.
  • Incoming issue and PR triage

**
Open Discussion [timebox to 5 min]**

  • (feel free to add any topics you’d like to discuss, even when they came up during the meeting)
  • Next meeting - [Savitha]: Collaboration between upstream marketing & RT communications.

June 15, 2021 (recording)

**Host: **Jeremy Rickard

Attendees:

  • Stephen Augustus
  • James Laverack
  • Supriya Premkumar
  • Divya mohan
  • Carlos Panato
  • Joseph Sandoval
  • John Gardiner Myers
  • Sascha Grunert
  • Rajas Kakodkar
  • Rey Lejano
  • Marko Mudrinić
  • Luke Philips
  • Adolfo García Veytia
  • Savitha Raghunathan

Topics [timebox to 20 min]:

Walk the Board [timebox to 20 min]:

  • Project board review: https://github.com/orgs/kubernetes/projects/23
    • In-review:
      • Rewrite milestone maintainer (Max) - Carlos to review
      • Add roadmap and vision - Stephen to work on this
    • In-progress:
      • Add Carlos and Adolfo to Tech Leads - May have a PR missing for k/org and needs top level approval for change to owners alias. Need to change the Slack config
      • Developer guide audit - assigned to Savitha
      • pull-kubernetes-e2e-gce is nearing its timeout - On GH, Jeremy asked reviewer to revisit this
    • [Stephen] If we are releasing with blocking jobs consistently failing then we need to demote the jobs to informing.
    • [Savitha] Max is working on pruning the jobs
    • [Action Item] Marko to get in touch with Max on status of pruning jobs
    • [Stephen] We need to establish a pattern for jobs.
  • Incoming issue and PR triage

**
Open Discussion [timebox to 5 min]**

  • (feel free to add any topics you’d like to discuss, even when they came up during the meeting)

June 1, 2021 (recording)

**Host: **Stephen Augustus

Attendees:

  • Daman Arora (Release Notes - 1.22 Shadow)
  • James Laverack (1.22 Enhancements Lead)
  • Derrik Campau (Release Lead - 1.22 Shadow)
  • Supriya Premkumar(1.22 Enhancements Shadow)
  • Trent Albright
  • Chris Negus (Docs - 1.22 Shadow)
  • Adolfo García Veytia
  • Nabarun Pal
  • Christoph Voigt (Bug Triage - 1.22 Shadow)
  • Jeremy Rickard
  • Joyce Kung
  • Sascha Grunert
  • Joseph Sandoval

Topics [timebox to 20 min]:

Walk the Board [timebox to 20 min]:

**
Open Discussion [timebox to 5 min]**

  • (feel free to add any topics you’d like to discuss, even when they came up during the meeting)

May 18, 2021 (recording)

Host: Stephen Augustus

Attendees:

  • Arsh Sharma
  • Divya Mohan (RT Lead Shadow)
  • Nabarun Pal
  • Subhrodip Mohanta
  • James Laverack (1.22 Enhancements Lead)
  • Sascha Grunert
  • Marko Mudrinić
  • Joseph Sandoval
  • Grace Nguyen (1.22 Enhancements Shadow)
  • Max Körbächer (1.22 CI Signal Lead)
  • Joyce Kung
  • Chris Negus
  • Kunal Kushwaha (1.22 release comms shadow)
  • Rajas Kakodkar
  • (1.22 release docs shadow)
  • Luke Philips

Topics [timebox to 20 min]:

  • Welcome any new members or attendees
  • Subproject updates
  • Roadmap and Vision: https://github.com/kubernetes/sig-release/pull/1529 Feel free to do another round of review [Stephen] This is a culmination from all the feedback to SIG-Release to provide a vision. Goal is to provide a secure release supply chain. How supportable and who is supporting our builds? Dan and Sascha have kicked this work off. There is an image promoter and a staging repository. Part of making artifacts consumable is putting them in a place that is consumable. There is a wider need to make CI more useful to the people testing Kubernetes. Define and collect metrics about the consumables. We need to have data to make assessments to improve. Release cadence survey. Make sure the community is satisfied with what is provided. Simplify the CVE process which depends on the CVE. If it's critical then it needs to happen asap vs low risk. How does the communication happen? Kubetest2 is a replacement for Kubetest. Enhance and simplify version markers. File based api’s to determine where a build is located. Making our work more consumable similar to the release page. Distroless images are now signed by co-sign. Next step is signing our own artifacts. You will continue to hear about software supply chain security. Please add comments to the PR.
  • Triage Party: [Arnaud] Will sync with Carlos on the issues. Application issue or missing secret. [Carlos] Will investigate tomorrow morning. Triage Party to be used over WtB. It's important we get this back up and running. All have permissions to work on it.

Walk the Board [timebox to 20 min]:

**
Open Discussion [timebox to 5 min]**

  • (feel free to add any topics you’d like to discuss, even when they came up during the meeting)

May 4, 2021 (recording)

Canceled due to KubeCon Europe

April 20, 2021 (recording)

Host: Sascha Grunert

Attendees:

  • Sascha Grunert
  • Jeremy Rickard
  • Nabarun Pal
  • Marko Mudrinić
  • Savitha Raghunathan
  • Joseph Sandoval
  • James Laverack
  • Derrik Campau
  • Dan Mangum
  • Luke Philips
  • Joyce Kung
  • Adolfo García Veytia (2nd half)

Topics [timebox to 20 min]:

  • Welcome any new members or attendees

    • [No new attendees]

  • Subproject updates

  • Release Cadence KEP

    [Jeremy] Will transition to 3 release schedules similar to 2020. Lightweight structure to build schedule out. 15 weeks. Finish by mid-December. Timelines have been proposed for 2021 and 2022. Josh and Jordan have provided input with the last release being 14 weeks. The first release will be in Aprili. 2nd will be August. Last release in mid December. Kubecon has been noted and paused during the event. KEP will be in Alpha during 1.22. The new community meetings will have this KEP presented. Lean heavily on mailing list communication with formal write up. Collect feedback in 1.22-1.25 to gauge how this is going. Didn’t want to make a change during 1.22.

    [Josh] When do we do the evaluation in the springtime? [Sascha] We will create metrics around the feedback. Josh will follow up on adding to the survey to help capture sentiment. Reach out to CNCF about how to handle the survey. [Josh] The way to reach end users is have CNCF make to market the survey. Also reach out to vendors to reach their users to provide feedback for the survey. Conflicting surveys need to be taken into considering. So plan in advance. Potentially August 2022 but Kubecon will block out all comms for the month.

    [Jeremy] Collecting end user feedback up to Aug 2022. Then plan for August 2023. [Lauri] When does Kubecon take over the CNCF comms? [Josh] Usually a month out ahead of the event.

    [Sascha] Approvers please provide your input.

  • Policy needs

    • First up for discussion, delivery: Policy regarding backports of dependency updates

    • [Lauri] We learned alot from the cadence KEP. This list is policy needs that have been needed. Tackling highest impact/needs from this list. Release cadence KEP can be crossed out. How to build artifacts in k/k. Providing an outline to build artifacts. Is that still the goal? What is the core related issue today? There hasn’t been any activity on this question. The policy would be general. SIG-release needs to provide the guidance when the source code is not in k/k.

    • [Sascha] This could be a starting point on how artifacts get promoted to the release bucket.

    • [Lauri] We can surface these topics. Can’t prioritize.

    • [Lauri] https://github.com/kubernetes/release/issues/1139. [Marko] Is there something we can do about this issue? Documentation is needed. [Lauri] Who is needed in this discussion? SIG-testing along with SIG-release. SIG-architecture? What would be the message for them? Are there any restrictions with GO versions? What about SIG-security? [Marko] yes. Also should we ask the GO team? [Sascha] Don’t need to add the GO team. [Lauri] What is the first step?

      [Marko] Draft document and share it. Lauri can kick that off. If we don’t do it the risk is we have no documentation and potentially miss a GO release.

      [Adolfo] What was missing was the documentation. Following the template ended up needing some help from Carlos.

      https://github.com/kubernetes/sig-release/issues/486 [Marko] Once we solve the Kubeadm issue we can resolve the other issues. [Lauri] What is a good step to take? Review and next meeting discuss what is being asked of SIG-release. Define lightweight policies will help drive or open more questions with out of tree issues.

Walk the Board [timebox to 20 min]:

**
Open Discussion [timebox to 5 min]**

  • (feel free to add any topics you’d like to discuss, even when they came up during the meeting)

April 6, 2021 (recording)

Host: Sascha Grunert

Attendees:

  • Sascha Grunert
  • Nabarun Pal
  • Carlos Panato
  • James Laverack
  • Joyce Kung
  • Daniel Mangum
  • Marko Mudrinić
  • Jeremy Rickard
  • Wilson Husin
  • Lauri Apple
  • Luke Philips
  • Rey Lejano
  • Taylor Dolezal

Topics [timebox to 20 min]:

  • Welcome any new members or attendees
    • [No new attendees]
  • Subproject updates
    • Release Engineering (https://github.com/orgs/kubernetes/projects/30)
      • [Adolfo] Not much to report.
      • [Carlos] Working to update Go. We're using 1.15.11 in release-branch 1.19. PRs in place.
    • Release Team (https://github.com/orgs/kubernetes/projects/29)
      • 1.21 Release in 2 days!!!
      • Release Signal was NO-GO in Monday’s burndown
        • Today’s signal analysis is async
      • Backup Plan
        • Proactive pushing of release date
        • Options are next week Monday or Tuesday
        • Decision to be taken during today’s Release Signal Analysis
        • [Jeremy/Marko/Taylor] No release Mondays, prefer Tuesday.
      • CI Signal
        • Tests are very flaky
        • master-blocking is RED
        • master-informing is RED
          • Gce-master-scale-correctness failed yesterday. Waiting for today’s run.
          • kubeadm-kinder-* jobs failing since a PR was merged on k/kubeadm yesterday. Author on it for a fix. Mostly it’s a configuration issue.
          • Windows jobs are in better form after some fixes went in recently
        • 1.21-blocking is VIOLET
          • Mostly jobs are flaking due to timeouts
        • 1.21-informing is RED
          • Windows jobs are failing
        • [Daniel] kind-ipv6 is notoriously flaky. Do we think it's an actual issue or just a bad run? [Joyce] We think it's a bad run, hard to get a consistent pattern. [Daniel] Most of the errors look like timeouts, maybe we should evaluate if these are a blocking test in the future.
        • Action Item: Daniel to look at kind-ipv6's future inclusion as a blocking job.
      • Bug Triage
        • Pod timeout flake issue is open
          • Discussions happening to resolve the release-blocker part of the issue
        • A bug fix was filed to resolve an issue due to a feature merged in 1.20
          • Open question about it’s severity and whether it can be merged for the .1 patch release
          • [Nabarun] I'll open a Slack thread in #sig-release to discuss async
          • [Daniel] First-look is that it's cloud-provider specific, which changes how we treat it. It feels like something that should be in a patch release, so that a vendor-specific issue doesn't impact the community as a whole (in delaying the release).
      • Release Notes
      • Docs
        • Integration branch is not healthy
          • PR 27432 is open to fix the integration branch
        • Reference docs generation is in progress
          • [Rey] Waiting for a k/website tag, some generation will happen on the day.
      • Comms
        • All okay on this front
        • PSP Deprecation blog is ready to be shipped before the release blog to prevent surprises
        • [Nabarun] Waiting for some CNCF approval for embargoes wrt the deprecation blog.
        • Release blog and feature blogs are ready
      • [Daniel] Is it realistic to release on Thursday? [Jeremy] That is optimistic given this update. We're better off delaying now until Tuesday because of the number of downstream consumers. [Nabarun] +1 for delay now until Tuesday, especially wrt the CNCF comms about the embargo. Looking to make a decision EoD.
      • [Nabarun] If the pod timeout flake is a big issue, maybe email out to the community (dev mailing list) asking for help? Only useful if we have a lot of flakes. [Taylor] It's a good idea, especially giving k-dev a technical breakdown of the issues leading to release delay. [Nabarun] I was thinking of two emails. One to k-dev with a list of flakes, with request for assistance. Second email EoD PT, about the decision to delay or not.
  • (feel free to add any topics you’d like to discuss as part of the agenda)

Walk the Board [timebox to 20 min]:

  • Project board review: https://github.com/orgs/kubernetes/projects/23
    • Skipping #2992, #908 and #2234 because they’ve been triaged in a dedicated session:
      https://docs.google.com/document/d/1nINF7EEznlhoXDtjHqaMoQUQ71N0Ata2rZD4FDLvKb4/edit#heading=h.fwj4ypzcapo8
    • k/k 99427 Adolfo tagged sig-release 28 days ago, he's not fully sure and will ping later about it.
    • k/enhancements 2567 [Sascha] In review [Lauri] what's our timeline? [Sascha] My plan is to have it merged before the 1.21 release. [Lauri] Who's driving that? [Sascha] Lets re-ping Stephen. I should have some time this week otherwise.
    • k/k 96692 Assigned Wilson and Sascha. [Sascha] Wilson has a PR open. Lets move the ticket to "In review"
    • k/release 1139 assigned to Stephen [Lauri] Carlos was going to work on it. [Carlos] Waiting on Stephen to publish the first draft. [Lauri] How long have you been waiting? [Carlos] Early Feb.
    • k/sig-release 734 Assigned Jeremy and Stephen. Neither on the call so leaving for now.
    • k/enhancements 1424 Discussed on another call. [Lauri] Something that needs discussion after 1.21 ships.
    • k/k 74375 [Sascha] Aaron is working on it.
    • k/sig-release 1257 [Marko] Max is working on it. [Sascha] Move it into in-progress
    • k/kubeadm 1599 [Sascha] Question is if we want a test to be release blocking. Some concerns about doing that. Unsure on the decision process and how to move that discussion forward. [Lauri] Are we awaiting evidence? Do we need more research? [Marko] We'll add that label.
    • [Marko] We have eight untriaged issues. [Lauri] We have in-depth triage sessions on Fridays if anyone would like to join for that.
    • k/sig-release 486 [Marko] Last update in 2020. [Lauri] This is more of an 'idea' post, we need to figure out what the 'ask' is and what the action would be. Still important.
    • k/k 74965 [Marko] Assigned to Daniel, from 2019 so quite an old issue.
      • Action item: Marko to ping Daniel about this.
    • k/k 72638 [Marko] Also from 2019, currently frozen. Is there anything we can do? [Sascha] Related to moving kubeadm out of tree, I don't think we can do anything right now.
    • k/k 72638 [Marko] Also from 2019, Stephen asked if it's still relevant.
      • Action item: Marko to follow up about this issue to find out if it's still relevant.
  • Incoming issue and PR triage

**
Open Discussion [timebox to 5 min]**

  • (feel free to add any topics you’d like to discuss, even when they came up during the meeting)

March 23, 2021 (recording)

Host: Sascha Grunert

Attendees:

  • Sascha Grunert
  • Nabarun Pal
  • Adolfo García Veytia
  • Rey Lejano
  • Carlos Panato
  • Lauri Apple
  • Jeremy Rickard
  • Pavel Malinov
  • Stephen Augustus
  • Wilson Husin
  • Luke Philips

**
Topics [timebox to 20 min]:**

  • Welcome any new members or attendees
  • Slight agenda update:
    • CI Signal report is now part of the “Release Team” update
    • “Walk the Board” section reordered
  • Subproject updates
  • (feel free to add any topics you’d like to discuss as part of the agenda)
    • [Stephen] Possibly push Docs Placeholder PR Deadline before Code Freeze to give SIG Docs an understanding of the workload

Walk the Board [timebox to 20 min]:

Open Discussion [timebox to 5 min]

  • (feel free to add any topics you’d like to discuss, even when they came up during the meeting)

March 9, 2021 (recording)

Host: Sascha Grunert

Attendees:

  • Vlad Gorodetsky (RT Lead Shadow)
  • Taylor Dolezal
  • Marko Mudrinić
  • Dan Mangum (SIG Release TL)
  • Jeremy Rickard
  • Sascha Grunert
  • Kunal Kushwaha
  • Verónica López
  • Joseph Sandoval (RT Enhancement Shadow)
  • Max Körbächer
  • Wilson Husin
  • Adolfo García Veytia
  • Nabarun Pal (1.21 Release Lead)
  • Arnaud Meukam
  • Luke Philips

Topics [timebox to 20 min]:

  • Welcome any new members or attendees
  • Subproject updates
    • Release Engineering (https://github.com/orgs/kubernetes/projects/30)
    • Release Team (https://github.com/orgs/kubernetes/projects/29)
      • 1.21 Updates
        • Code Freeze is today!!!!
          • Milestone requirement PR in place (thanks Adolfo!) - LGTM’ed and Approved. Hold will be removed at 6PM PST
          • The email will be sent at 6PM PST right after the milestone requirement PR is merged.
          • [Nabarun] will send the email out to k-dev tonight. Will detail how things gets merged during code freeze
        • 1.21.0-beta.1 is released today. (thanks Max!)
          • [Nabarun] release went smoothly, thanks Max!
        • Enhancements (thanks Anna and all the Enhancements team shadows!)
          • 62 being tracked
          • 38 code complete or very near to completion
          • 24 are At RIsk of being removed from milestone
            • [Nabarun] PRs are either not open, not close to completion, or haven’t had API review yet
        • Exceptions
        • Bug Triage (thanks to Derrik and his bug triage team!)
          • 32 open issues in v1.21 milestone
            • Around 9 are related to flaking/failing tests
            • [Nabarun] in pretty good shape here
          • 37 open PRs in the milestone
        • CI Signal (thanks to Joyce and their team!)
          • To be covered in the next section
        • Other verticals like Release Notes, Comms and Docs are green.
          • [Nabarun] Docs have a lot of incomplete but will expect it to drop as enhancement number drops
          • [Wilson] Fun fact: there are 108 PRs between 1.21.0-beta.0 and 1.21.0-beta.1 \o/
    • CI Signal (https://github.com/orgs/kubernetes/projects/11)
      • Testgrid dashboard review: https://testgrid.k8s.io/sig-release
        • Master-blocking looks good these days
        • Master-informing still flakes often on the -windows-
      • Overall you see the progress in deflaking master-blocking in the project board, most of the flakes are picked up or resolved
        • In addition not so many new flakes opened the last days
      • [Max] sig-release-master-blocking has gotten much better over the past few weeks
      • [Max] still a lot of red on sig-release-master-informing, especially windows jobs (per usual) -- active discussion in Slack to get these addressed
      • [Max] some of the issues need to be advanced on the board
  • [hasheddan] Flake Finder Fridays #001 this Friday!
  • [Wilson] Self-promotion of my pet project, looking to see if there are interest in collaborating / suggestions moving forward to get this migrated under kubernetes / kubernetes-sigs org
    • Currently lives here: https://github.com/wilsonehusin/k8s-release-notes-data
    • This approach separates the "gather", "edit", "render" section of the release notes
    • The ultimate goal is that folks can submit overrides to release notes without having to do local operations of krel setup
  • (feel free to add any topics you’d like to discuss as part of the agenda)

Walk the Board [timebox to 20 min]:

Open Discussion [timebox to 5 min]

  • (feel free to add any topics you’d like to discuss, even when they came up during the meeting)

Feb 23, 2021 (recording)

Host: Jeremy Rickard

Note Taker: Rey Lejano

Attendees:

  • Wilson Husin
  • Rey Lejano
  • Adolfo García Veytia
  • Max Körbächer
  • Savitha Raghunathan
  • Pavel Malinov
  • Taylor Dolezal
  • Tim Pepper
  • Nabarun Pal
  • Stephen Augustus
  • Lauri Apple
  • Luke Philips
  • Verónica López

Topics [timebox to 20 min]:

  • Welcome any new members or attendees

    • Luke Philips - lurk and learn and looking to see where he can help out

  • Subproject updates

    • Release Engineering (https://github.com/orgs/kubernetes/projects/30)
      • [hasheddan] Krel Config API (https://github.com/kubernetes/release/pull/1926)
        • [Dan] WIP PR for API to configure krel, would like to be more declarative
      • [hasheddan] Using Crossplane to manage k8s community infra (demo)
        • [Dan] Demo video, look at Crossplane to manage infrastructure, scoping out a POC for a mvp, will open an issue on k8s.io
      • [hasheddan] Documenting release-blocking tests
        • [Dan] Part of supported platform, would like to have better documentation around release-blocking tests, the strategy over time has been informal. So people are aware of the implications of job failures. Will try to get a template for people to build on. Asking for contributions to the effort
    • Release Team (https://github.com/orgs/kubernetes/projects/29) * [Nabarun] 14 days from code freeze * [Nabarun] Feature blog freeze on March 1. Only have 1 blog opted in so far, would like to get 4. * [Jeremy] Lots of flaky jobs on testgrid, is the team looking into it or need help * [Nabarun] Joyce is on top of it and the team is on top triaging flakes * [Stephen] Aaron is working on lots of changes on master blocking jobs, one is around using now using k8s release dev bucket to pull artifacts (k8s community bucket) versus using a Google infrastructure bucket.
      • 65 Enhancements being tracked
      • MWF burndown meetings to begin next week
      • 1.21-beta.0 release today
      • 1 feature blog opted-in. Team will be pinging SIG Leads on respective SIG slack channels.
    • CI Signal (https://github.com/orgs/kubernetes/projects/11)

  • (feel free to add any topics you’d like to discuss as part of the agenda)

    • Any guidelines for requesting security reviews? [Savitha]

      • Discussing how to include PRR reviews, don’t want to add more burden on KEP owners. Takeaways: time to request a PRR is when feature is proposed to SIGs, have an opt-in process and it will be up to the SIG leads to request for a security review. Also attached the WIP hardening guide

      • [Stephen] Around enhancements tracking repo is around scope. Trying to determine the scope of an enhancement. Two types of KEPs: KEP that the release team cares about and everything else. Suggest to look at the miro board

      • [Lauri] Link to miro board https://miro.com/app/board/o9J_lbvQp4Y=/

          Lauri will add security reviews

  • [Stephen] Link to scope issue https://github.com/kubernetes/enhancements/issues/2311

  • [Stephen] Meetings around KEPs (need more context) on Thursdays at US 1pm EST

  • [Stephen] Looking at recent releases, we have many more enhancements in the releases and this will lead into the project planning/roadmap and tools that we’re writing now

Walk the Board [timebox to 20 min]:

  • New kubernetes/kubernetes issues review
  • Project board review: https://github.com/orgs/kubernetes/projects/23 * Artifact Management board * [Veronica] Triage Party: url was down, Arnaud fixed the url. Arnaud also sent a PR with a bump for 1.21 and Carlos approved it. It’s been painful behind the scenes for all the downtime root-causes. Arnaud and Veronica discussed with this bump that it should be good-to-go but not 100% sure if this is what you would consider “done”. Call for people to collaborate or if people want to understand Triage Party. Link to Triage Party: https://release.triage.k8s.io * [Stephen] Triage Party is currently pointing at 1.20. We need to create success criteria, ask what people want to see in dashboards, want boards for each sub project and ask what can we do to “close the books” on this. Need to look at automating triage party, can it be a Deployment? * [Lauri] Look at prototype plans and look at feature needs * [Veronica] Open to what the “complete criteria” should be * [Veronica] PR to bump triage party to 1.4.0-beta.1 https://github.com/kubernetes/k8s.io/pull/1700 * [Stephen] Start using triage party for SIG Release and subprojects and get a “wish” list going * [Veronica] Send us your wish list. * [Stephen] Need to have SIG release and subprojects using Triage Party and request Veronica and Arnaud to document gaps * Use docker buildx for the build-image k/k PR #99080 * [Stephen] Have more clarity on what image it's referring to. Needs a review. Add reviewers to the PR * Automate some work for the release-docs/enhancement team * Unassigned but in-progress * Should be on the release-team project * Rewrite milestone maintainer - Max (not on the call) * [Stephen] Let’s get reviewers, add Jeremy * Chair/Technical Lead access for Jeremy * Done but Jeremy will make the template more detailed and Stephen will fix Jeremy’s announce privileges * Create some more CI Signal documentation * [Lauri] Two weeks ago, they were nearly done * [Stephen] Dan and Joyce are on point for review * [Joyce] Rob pushed a second set of changes, will take a look soon * [Stephen] [Action-item] Put this on the release team board * Draft a policy for updating Go versions across the Kubernetes code base/infra * [Stephen] Policy Doc will hand off to Carlos and Arnaud * CVEs for Dependencies * From 2018 * [Stephen] We are doing things differently, we should sync with SIG Security and Product Security committee. Adolfo is also adding CVEs to release notes template but that is a presentation template for disclosed CVEs not so much as the implementation path for CVEs. Need to refine the goal of this issue since the issue is 3 years old. Assign to Dan and Stephen * GitHub PR reviews as /lgtm + /approve for SIG Release repos
  • Incoming issue and PR triage

Open Discussion [timebox to 5 min]

Feb 9, 2021 (recording)

Host: Lauri Apple / Sascha Grunert

Note Taker: TBD

Attendees:

  • Sascha Grunert
  • Vlad Gorodetsky
  • Marko Mudrinić
  • Dan Mangum
  • Arnaud Meukam
  • Jim Angel
  • Rey Lejano
  • Adolfo García Veytia
  • Lauri Apple
  • Pavel Malinov
  • Victor Palade
  • Wilson Husin
  • Joseph Sandoval
  • Luke Philips

Topics [timebox to 20 min]:

Walk the Board [timebox to 20 min]:

Open Discussion [timebox to 5 min]:

  • Ask around for the subproject updates before the meeting that we can ensure we get an update for each one

Jan 26, 2021 (recording)

Host: Stephen Augustus

Note Taker: Sascha Grunert

Attendees:

  • Sascha Grunert
  • Vlad Gorodetsky
  • Joyce Kung
  • Adolfo García Veytia
  • Evelyn Cupil-Garcia
  • Rey Lejano
  • Dan Mangum
  • Jim Angel
  • Lauri Apple
  • Wilson Husin
  • Arun Krishnakumar
  • Pavel Malinov
  • Rin Oliver
  • Seth McCombs
  • Kirsten Schumy
  • Somtochi Onyekwere

Recurring Topics [timebox to N min]:

Open Discussion [timebox to N min]:

  • [Dan] Other hardware arch & OS support? Discussion in SIG Arch
  • [Stephen] SIG annual reports for Steering
    • Steering committee started reporting for working groups (goals, needs, achievements)
    • Now applies to SIGs, too
    • Reach out to Stephen to find out metrics regarding our goals
  • [Jim] Stakeholders discussion on a release page
  • [Lauri/Derrik] Bug Triage wishes to run a grafana dashboard to track Issues/PR’s for milestones. Where should this be hosted (or should we piggyback off of CNCF Devstats?)
  • Release Cadence decision:
    • Follow-up email containing the feedback we’ve got will come soon
    • The next necessary steps have to be defined
    • Likely to write-up a KEP for applying the new cadence
      (targeting enhancements deadline at Feb 9th)
    • Community survey to gather data is also an option right now
  • Back to future topics:
    • [Jeremy] - Merge Blocking after Milestones
    • [Kirsten/Jeremy] Clarify and memorialize criteria for removing unmerged items at Code Freeze;
    • [Taylor] For the release team shadow application responses, since the results contain PII, what is the best way to share out that privacy concern with applicants, and how do we gate access around that point of collection?
    • [Taylor] For people that do not get selected to be a part of the release team in a specific cycle, can we engage them in any other capacity or role(s)?

Jan 12, 2021 (recording)

Host: Sascha Grunert

Note Taker: Verónica López

Attendees:

  • Daniel Mangum
  • Sascha Grunert
  • Nabarun Pal
  • Rey Lejano
  • Verónica López
  • Vlad Gorodetsky
  • Taylor Dolezal
  • Carlos Panato
  • Joseph Sandoval
  • Stephen Augustus
  • Kirsten Schumy
  • Adolfo García Veytia

Recurring Topics [timebox to N min]:

Open Discussion [timebox to N min]: