Reminder: September Community Meeting this week!
eddi...@gmail.com
I’m Eddie, and I’ll be your host for the September community meeting, which is this Thursday at 10 AM PST (see time converter below). We would love to have everyone attend if they can. As part of moving to a monthly cadence, the host will post the draft notes and final notes to this list as a reminder and as a way for the community to easily check out the SIG status updates.
Date and Time: 5pm UTC (Time zone converter) on Thursday, Sept 17th
Zoom: https://zoom.us/my/kubernetescommunity
Draft Agenda: http://bit.ly/k8scommunity
This month, we will be hearing from the following SIGs:
- SIG Windows
- SIG Multicluster
- Code of Conduct Committee (CoCC)
- SIG Auth
If you have any questions about the meeting, you can reach out to the Contributor Experience SIG in Slack under #sig-contribex.
Thanks and see you soon,
Eddie, on behalf of SIG Contributor Experience
P.S. - If you want to host the monthly meeting, we’re looking for volunteers and first-timers! Please reach out to us on Slack or message Jorge Castro for more info.
eddi...@gmail.com
Moderators: Eddie Zaneski [AWS/SIG-CLI]
Note Taker: Josh Berkus [Red Hat/Contribex]
Subscribe to this thread to get these notes in your inbox
[ 0:00 ] Demo -- Warning: Helpful Warnings Ahead [Jordan Liggitt]
It's hard to keep up with kubernetes
Release notes are long
Start with a manifest file -- example v1beta1/RBAC api file
Is that deprecated yet?
When is it going away?
Added ability of the server to return warnings to users as of 1.19
Server sends back headers to the clients (update your client)
This works for any kubectl command
In 1.19, you'll get warnings about all deprecated APIs
In the future, we'll give warnings about other things
Even problematic configurations, like 4millibytes of memory
Also: metrics about upgradability of cluster. Like, are people actually *using* the things that are deprecated?
Check # of calls to deprecated API
output is to STDERR.
Kubectl does not have an option to silence warnings, but client-go does.
Details and examples in the blog post
[ 0:10 ] Release Updates
Current Release Development Cycle [Jeremy Rickard | @jerickar]
Patch Release Updates https://git.k8s.io/sig-release/releases/patch-releases.md
v1.19.2 planned for Wednesday 2020-09-16
Kicked off the release this week, it is now Week 1
Enhancements freeze is Oct 6
Pushed the docs deadline out a little bit because of conflict with Kubecon (Nov 30)
1.20 will be 13 weeks
Planned release date: Dec 8
Shadows are mostly selected
[ 0:00 ] SIG Updates
SIG Windows [Mark Rossetti + Michael Michael]
Did a bunch of work on containerd in the last cycle
Aligning windows with the CRI
CNI is now supported with containerd
containerd has Windows features that you don't get with Docker, like graceful shutdown and namespace mapping
now working on HyperV isolated containers
Also developed CSI proxy, windows service to support CSI
Currently supports Azure disks, GCE
Currently in beta
Adding more providers for 1.20 release
Networking work
Support for endpointslices
sticky sessions
dual-stack support
Antrea and Calico CNIs are supported
Need to promote DSR kube-proxy to stable
Shared tech matrix of windows and kubernetes versions
More plans
More CRI-containerd work
GPU support
Add more storage providers, add Valero support for backup
Dump the in-tree Windows extensions
Add privileged container support, which is a big deal, KEP awaiting approval
If you're reviewing PRs and KEPS that might impact Windows, please ping the SIG
SIG Multicluster [Jeremy Olmsted-Thompson + Paul Morie]
Name for a group of clusters: ClusterSet
Are writing guidelines, starting with Namespace Sameness Doctrine
Next: defining what a ClusterSet means
Membership & registration
Workload placement
Move APIs to beta
Kubefed is working on adding "pull reconciliation"
Currently Kubefed does push
Team is working on multicluster reconciler
Multicluster DNS
Define Cluster ID
Please give feedback
WorkAPI
Different API type than Kubefed
Fed has you create each resource in each cluster
WorkAPI has a single "work" that deploys resources across the multicluster, with status information
But scheduling is still undefined
Initial KEP being drafted, early prototypes
SIG-MC needs input!
What else should be in a CLusterSet?
Have you built an MC thing that you like? Share?
Need help from SIG-network, SIG-apps
Code of Conduct Committee [Aeva Black]
Recently had elections, have 5 members
Folks don't know what the COCC does
Distinct from SC/Contribex
We're here as a resource to help out
We handle incidents
But, you can also ask for info, doesn't need to be an incident
Focused on harm reduction
Were CoCC for Kubecon SD, tested model there for helping with events
Also working on transparency reports
Did some conflict resolution, including between SIGs
Have offered coaching for problematic content
Working on:
SLA for incident response
Report/Triage docs
Formalize relationship with all admins
[ 0:44] 📣 Announcements 📣
Kubernetes Steering Committee Elections!! VOTE!! [Josh]
Didn't get your ballot? Request a replacement
We have passcodes for zoom now!! (zoom’s rules!) 77777 - pass it on.
PK will host next month
[ 0:46 ] 👏 Shoutouts this month 👏
See someone going above and beyond? Mention them in #shoutouts channel so that we can recognize their work in front of the community.
@sraghunathan shoutout to @karenb for her support with 1.19 k/website release process so far. She is dependable and goes an extra mile to help and constantly on the lookout for improvement. Thanks for your help @karenb
@liggitt shoutout to @knight42 for tireless work tracking down and fixing test flakes (and real bugs the flakes were trying to alert us about!)
@aojea big, huge shoutout to @liggitt , not only due to his work, also for sharing his knowledge and expertise
@inductor shout out to @kakts and @oke-py for creating good first issues in Japanese localisation
@spiffxp Big big shoutout to @aojea who helped track down DNS as the culprit of recent kubernetes/kubernetes CI woes
@Lauri Apple Shoutout to @xmudrii for driving efforts to firm up the roles and responsibilities for our Release Manager Associates!
@jerickar K8s 1.19 retro is happening, shout out to @Lauri Apple for digging into previous retro to-do items and prioritizing things that had fallen by the wayside and helping to make releases better going forward!
@sftim Shoutout to @zacharysarah for a wealth of positive, valuable contributions to SIG Docs
@ehashman Shoutout to @jvanz for this excellent first PR. I helped backport the fix to 1.17-1.19. Cross-checking this against the production clusters I support, I discovered this bug is producing a full 2% of our production logs, so the fix will save a lot of wasted volume! :)
@dholbach @SomtochiAma has done great work in her GSoC internship this year
@SomtochiAma Shout out to my awesome mentors throughout the GSoC internship @justinsb @stealthybox and the #cluster-addons community! They were really amazing
- Next months host is @PK!