Sep 20, 2018
Moderators: Jonas Rosland [SIG-ContribEx]
Note Taker: Josh Berkus, Jaice Singer DuMars and Jorge Castro [SIG-ContribEx]
- [ 0:01 ]** Release Updates**
- Current Release Development Cycle [Tim Pepper ~ 1.12 Release lead]
- We’re down to probably 1 issue pending fix and test soak
- Key upcoming events barring any new test issues:
- Friday Sept 21 “cherry-pick deadline” (non-event given master hasn’t yet thawed)
- Friday Sept 21 cut RC2 and built rpms/debs
- Monday Sept 24 last release-1.12 branch fast-forward from master branch
- Monday Sept 24 thaw master branch
- …final soak: cherry picks only for absolutely critical show stopper bugs…
- Thursday Sept 27 release
- Patch Release Updates
- 1.9.10 released Aug 3
- 1.10.8 released Sept 15
- 1.11.3 released Sept 11
- [ 0:03 ] SIG Updates
- SIG Cloud Provider [Chris Hoge] (confirmed)
- Looking at cloud providers in core code, like Google, AWS, etc.
- Don’t want more in the upstream code
- Want level playing field
- In the process of moving providers to plugins
- Minimum requirements to add a provider, is it documented? Do they post results to testgrid? So that users have some assurance that they’ll have a positive experience.
- In 1.12:
- Added new providers to SIG-CP: Alibaba. DigitalOcean and Baidu in progress.
- Started work on removing the in-tree providers
- In 1.13:
- Continue work to move in-tree providers
- Document external provider usage, need to make sure all requirements etc. are documented. Installation process is more complicated, for example.
- Maybe moving provider SIGs into SIG-CP, likely to take longer.
- Make sure all providers have conformance test results
- SIG-Docs doesn’t want to be in charge of provider docs, that should be up to SIG-CP
- Working with Cluster Lifecycle on install/upgrade
- Q: should provider repos be in the Kubernetes org?
- A: the decision on whether providers should be part of the kubernetes org is an Arch decision, it’s a question of what you think Kubernetes is. We’re trying to provide a level playing field. Right now, they are part of the org.
- SIG Architecture [Jaice Singer DuMars] (confirmed)
- What we do
- Manage and maintain architectural consistency over time
- Manage subprojects:
- Manage policy and governance
- API governance (guidance docs and the review process)
- Deprecation policy
- Code organization
- KEP process
- General issues around Kubernetes scope
- What are we working on right now?
- SIG API Machinery [Daniel Smith] (confirmed)
- Dry run in alpha to see what the predicted outcomes of an action will be
- You can test API to see what it looks like when it runs through the webhooks
- CRD versioning change
- No schema change allowed
- Register a webhook to do a schema change
- All the various API definitions should have the same feature set
- SSH tunnels are going away - this has been deprecated for a year
- Re: server side apply
- In a feature branch
- Allows writing code during freeze
- More complete designs on the way
- “We don’t own your API” - we’re not the API reviewers
- We do own some APIs like metadata format, CRD API, webhook interface APIs, comms between aggregator & APIs, controllers, RBAC API, controller shell (informer, reflector, shared informers, etc.), controller manager binary
- rate limits, flow control - prevent API quota over-consumption ~ de facto prioritization of API requests
- Internal API Server coordination - e.g. how do you know when every API is serving the same version of a CRD
- SIG meeting & agenda ~ if it’s empty the day before, the meeting will be cancelled (there’s an “agenda closed” meeting event)
- [ 0:00 ] Announcements
- Calendar information - subscribe, don’t copy! [Jonas]
>>>>> gd2md-html alert: inline image link here (to images/Kubernetes-Community0.png). Store image on your image server and adjust path/filename if necessary.
(Back to top)(Next alert)
* Google Calendar:
>>>>> gd2md-html alert: inline image link here (to images/Kubernetes-Community1.png). Store image on your image server and adjust path/filename if necessary.
(Back to top)(Next alert)
* Election Update [Jorge]
* [All the info you need](https://groups.google.com/forum/#!topic/kubernetes-dev/0gEdp_xdzEI)
* Total voters: 677
* Actual votes cast thus far: 144
* If you are in [voters.md](https://github.com/kubernetes/community/blob/master/events/elections/2018/voters.md) but have not received a ballot please mail [firstname.lastname@example.org](mailto:email@example.com)
* Election ends on October 3.
- Kubernetes Contributor Summit is happening [Jorge]
Content is in draft, SIG leads and TLs, please review and comment
Register as part of your Kubecon registration (check the box for collocated events); you will get a follow up email about RSVPing for tracks and
Sunday dinner and fun @ garage in Seattle
- Contributor Social Shanghai: 11/13, 6pm, at the convention center
- Will have panel on contributing from China
- Contributor Survey [Jorge]
- [Jorge] October 1st marks the start of Hacktoberfest, a month-long celebration of open source software. This is an opportunity to welcome new Kubernetes contributors to the community. Please help by making an extra effort this month to add more issues with the good-first-issue label. If you have any large tasks that could use help from a lot of contributors, now would be the perfect time to create an issue for it. You can learn more about Hacktoberfest here: https://hacktoberfest.digitalocean.com/
- ContribEx will be generating a 404 report for new users so they will have a place to go.
- SIGs, consider updating your good-first-issue labels.
- SIG Leads, we’ve put together some recommendations for how to give an update for this meeting, the host will be reminding you from now on before your update.
- Last call for Outreachy intern requests!
#Shoutouts!_ (want to say thanks? Use the #shoutouts channel in slack)_
* @vlad Shlosberg: Huge shoutout to @jorge, @mrbobbytables, @paris, @hubt and a bunch of other for helping make @Foqal a success. Working with me on feedback, helping promote the project, submitting helpful answers, and everything else you guys have done!
* @bentheelder: Shoutout to @mrhohn for being eternally responsive to networking issues on everything from PR reviews to sig-network test configs, dns images, the network e2es, and answering questions related to network issues in the infra and helping debug! Thanks for helping get the kube-dns manifest images out the door for 1.12! Zihong is always fixing things for us over in #sig-testing and now over in #sig-release
* @nikhita: shout out to @carolynvs for creating lots of help-wanted issues on service catalog (https://github.com/kubernetes-incubator/service-catalog/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22)…and having an excellent strategy of doing that! - https://twitter.com/carolynvs/status/1042061098101485580
* @dims: big shoutout to @fabrizio.pandini for testing all the things! (v1.12 RC1 kubeadm under various scenarios)