kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
community/communication/meeting-notes-archive/q1-2_2018_community_meeting...

189 KiB
Raw Blame History

This is an archive document

July 26, 2018 (recording link)

  • Moderators: Chris Short [ContribEx]
  • Note Taker: Solly Ross, Josh Berkus
  • Demo: EKS - Bryce Carman - [Amazon EKS] (confirmed)
    • Managed Kubernetes on https://aws.amazon.com/eks/
    • Provisioning
      • Control plane is hosted/managed by EKS, worker nodes are under control of users
        • No outside communication with the control plane besides via the load balancer in front of the API server
        • Can use security groups to limit control-plane-worker-node interaction
      • Can set role used to create various AWS resources (like loadbalancers) so that you don't have to give EKS full permissions in your account
      • Can just use VPC and subnets already present in account
    • Networking
      • CNI plugin
      • Usines IP addresses from VPC that the nodes are already part of (integrated with AWS networking)
      • No overlay network
      • Can integrate with Calico network policy as well
      • Designed to isolate control planes from nodes as well
    • Interaction
      • Using Heptio authenticator and 1.10 for external authentication for kubectl in order to authenticate against AWS IAM
      • Just uses the same creds as the AWS CLI -- no separate auth to manage
    • Demo'd using Helm to create a wordpress site
    • Questions
      • Can users scale control plane?
        • No
  • Release Updates
    • 1.12 - Tim Pepper - Confirmed
      • Feature Freeze Tuesday July 31 - next week
        • see email on k-dev for more info
        • After Tuesday features not captured by the release team must go through the exception process.
        • SIGs should be thinking about their release themes (major work focuses) for the 1.12 release, insuring those are represented in feature issues and have plans for documentation and test coverage.
        • Not code freeze (that comes later)
    • 1.11.x - Anirudh Ramamathan - Confirmed
      • Nothing to report
  • **KEP o' the Week **- KEP 17 - Jordan Liggitt - Confirmed
    • KEP 17 - Moving ComponentConfig API types to staging repos
    • Taking config for core kube components from loose flags to structured config
      • Kubelet currently has a config file format that's in beta
      • Makes it easier to look at exactly how a particular component is configured, warn about deprecated config, missing config, etc
    • Want to put configuration types in separate repo
      • Tools like kubeadm should be able to import config to manipulate and generate, without pulling in all of Kubernetes
    • Want to make sure common configuration aspects can be shared, referenced, and reused
      • client connection info
      • Leader election
      • etc
    • Look over if you are involved in developing the Kube components, or have tooling that sets up the various components
  • SIG Updates
    • Auth - Jordan Liggitt - Confirmed
      • https://docs.google.com/presentation/d/1MAIypro-bcLC7wNEnIazYqmCL6ILBN69uUWIBw7QBIY/edit?usp=sharing
      • Usability
        • Multiple Authorizers (e.g. GKE)
          • Now honor superuser permissions from other authorizers, so if you're a superuser, you can create policy without first explicitly granting yourself those permissions
          • Now show the error message from all authorizers, instead of just the error from the first authorizer
          • Show a much cleaner, more succinct and readable error message for failures due to escalations
      • Features
        • Kubelet Certs
          • Better support for delegating to an external credentials providers (e.g. AWS IAM)
          • Requesting and rotating certs with the CSR API (still requires external approval process for the CSRs)
        • Scoped service account tokens
          • Moving towards beta for time-limited and audience-scoped tokens
        • Audit improvements
          • Heading towards v1 audit event API
          • Work ongoing on dynamic audit webhook reg
    • Instrumentation - Frederic Brancyzk - Confirmed
      • Heapster deprecation (https://github.com/kubernetes/heapster/blob/master/docs/deprecation.md)
        • Setup removal in 1.12, completely removed as of 1.13
      • Node metrics work still ongoing, in collaboration with SIG Node
        • Improve monitoring story around node monitoring
        • Chime in if you maintain a device plugin or node component
      • Metrics-server rework (https://github.com/kubernetes-incubator/metrics-server/pull/65)
        • call for testing in non-production servers, should make things more stable, has several fixes to communication with nodes
      • k8s-prometheus-adapter advance configuration merged
        • Allows more precisely controlling how metrics in the custom metrics API map to Prometheus queries, and how metrics show up in the custom metrics API
      • A number of third party service involving e2e tests have been put behind a feature flag in the test infrastructure
        • should improve flaking tests from sig-instrumentation, especially around components that we can't control
  • Announcements
    • **Shoutouts **(mention people on #shoutouts on Slack)
      • Manjunath Kumatagi for patiently working through issues that will help us run conformance tests on other architectures (say arm64). It's taken a really long time to get this far and the end is in sight. Thanks for your hard work across multiple repos and sigs.
      • Jordan Liggitt for always knowing the answer to ... everything ... and being so available to answer questions. You're an incredible resource and I'm always grateful to lean on you when I need to!
      • Quinton Hoole for including a "how you can contribute" slide in the SIG Multicluster update in today's community! Way to model SIG leadership in growing the k8s team by facilitating new/increased participation!

July 19, 2018 (recording link)

  • Moderators: Tim Pepper [ContribEx, Release, VMware]
  • Note Taker: Solly Ross
  • Demo: Microk8s - Marco Ceppi (confirmed)
    • https://microk8s.io / #microk8s on Slack / https://github.com/juju-solutions/microk8s
      • Lightweight kubernetes cluster install
      • Installed, uninstalled with snaps
        • works across different linux distros, other OSes coming eventually)
      • Still a bit in beta
        • Different releases installed with different channels (beta channel is 1.11.0, edge is 1.11.1)
    • Commands installed namespaced by microk8s.
      • kubectl is microk8s.kubectl
      • Can enable different addons like dns and dashboard with microk8s.enable
        • Cert generation, ingress, storage also available
      • kubeconfig is scoped just to microk8s.kubectl, doesn't interfere with normal kubectl
      • microk8s.reset resets to blank state
    • Kubernetes run as systemd services
    • Service Cluster IP addresses available as normal on host system
  • [ 0:09 ]** Release Updates**
  • [ 0:13 ] **KEP o' the Week **- none this week
    • If you want to get a broader audience for an up-and-coming KEP, you can get it discussed here!
  • [ 0:14 ] SIG Updates
    • SIG Big Data (Anirudh Ramanathan, Yinan Li, confirmed)
      • Deal with big data workloads on Kube
        • Specifically: Spark, Spark Operator, Apache Airflow, HDFS
      • Code freeze for Spark coming up, so lots of work there
        • python support, client node support for things like Jupyter notebooks talking to Spark on Kubernetes)
        • Stability fixes - better controller logic
          • Making sure to be level triggered and not edge triggers
        • Removing some hacks with init containers
      • Spark (link)
        • Working towards 2.4 release.
        • 2.4 code freeze and branch cut on 8/1
        • Major features
          • PySpark support
          • Client mode - support for notebooks
          • Lots of testing, merged integration tests
          • Removal of things like init-containers (getting us closer to GA)
          • Stability fixes - controller logic
          • Improvements on client side
        • Future work
          • Customize pod templates
          • Dynamic allocation/elasticity
          • HA driver - might need help from sig-apps to make it work
          • SparkR and Kerberized HDFS support
      • Spark Operator new features (link)
        • Mutating admission webhook to replace initializer used before
        • Python support
      • HDFS support (link)
        • Assessing demand, making progress
        • Chart exists in link above
      • Airflow (link)
    • SIG Multicluster (Quinton Hoole, confirmed)
      • Slides
      • Goals
        • Solving common challenges releated to managing multiple clusters
        • Applications that run across multiple clusters
      • Subprojects
        • Cluster Federation (v2) [https://github.com/kubernetes-sigs/federation-v2 ]
          • Work across different clusters, same or different cloud provider
          • V1 was a POC, won't be developed further
          • V2 focuses on decoupled, reusable components
          • V2 has feature parity with v1, is alpha
          • Highlights
            • CRDs for control planes, installed in existing cluster
            • Generic impl for all kube types (including CRDs) for propagating any types into all clusters, with basic per-cluster customization
            • Several higher-level controllers, for example:
              • migration of RS and deployments between clusters
              • Managing federated DNS
              • Management of Jobs
              • Management of HPA to manage global limits
            • Uses cluster registry
          • Next steps
            • Federated status
            • Federated read access (e.g. view all pods across all clusters)
            • affinity/anti-affinity for bunches objects or namespaces to a particular cluster
            • RBAC enforcement
          • Please comment if you have suggestions for API, before moves to beta
            • Contributions to code also welcome
        • Cluster Registry [https://github.com/kubernetes/cluster-registry ]
          • Fairly stable and complete
        • Multicluster Ingress [https://github.com/GoogleCloudPlatform/k8s-multicluster-ingress ]
          • Look at repo for more information
        • Questions
          • Cluster registry vs cluster API?
            • Cluster API is to create clusters, cluster registry is for using already-existing clusters
            • Maybe could disambiguate the terms better, manage overlap
    • SIG Scheduling (Bobby Salamat, confirmed)
      • 1.11 Update
        • Pod Priority and Preemption to beta, available by default
          • Improved the feature, restricted a bit to avoid allowing untrusted users to create high-prio pods, only allow super-high-priority pods in kube-system namespace
        • DaemonSet scheduling in default scheduler (alpha)
      • 1.12 Update
        • Focus on performance
          • Improved equivalence cache (pod with similar spec probably fits on same node unless the node has changed)
            • 3x performance improvement now
            • Helps with scheduling large replica sets, etc
        • Working on proposal for gang scheduling [link here]
        • Proposal for scheduling framework, direction might change a bit [link here]
        • Moving to beta
          • Taint by condition, taint-based eviction
          • Equivalence cache
          • DaemonSet scheduling in default scheduler
        • Want to graduate descheduler out of incubator
  • Announcements
    • **Shoutouts **(mention people on #shoutouts on Slack)
      • Jeremy Rickard: Shout out to @mbauer for really pushing to make service catalog use prow and to improve out PR reviewing and testing process
      • Christoph Blecker: Two shoutouts I wanted to get out this week:
        • First, shoutout to @matthyx who has been very active in k/test-infra recently and has been making a number of different contributions from fixing bugs, to adding new features to our automation. He's been eager to help and has stuck with some of the more complex changes that require many comments and interactions (sig-bikeshed ftw :bikeshed:)
        • Second, shoutout to @nikhita! I could easily stop right there, as her many contributions to the project really speak for themselves. I want to call out though the little chopping wood and carrying water tasks she does that may not be as obvious.. like ensuring that stale issues are reviewed and either closed or marked as still relevant, or welcoming new contributors with an emoji or two. It's these kinds of things that exemplify what the Kubernetes community is all about.
      • Benjamin Elder: shoutout to @Quang Huynh for continuing to send k/test-infra fixes and push through to flesh out the PR status page (especially https://github.com/kubernetes/test-infra/pull/8612) long after his internship! :simple_smile: Hopefully we can hopefully start using the Prow PR status page more widely now thanks to all the hard work there 🎉
      • Aaron Crickenberger: shoutout to @bentheelder for helping push kubernetes v1.11.1 images out (fixing the symptom), and getting the appropriate folks within google involved to ensure there is now a team owning a better solution to the problem (fixing the problem); this is continued progress toward decoupling google.com as a requirement for releases
    • Kubernetes wins most impact award at OSCON!!! (-paris; Tim to read)

July 12, 2018 (Recording)

  • Moderators: Paris Pittman [ContribEx, Google]
  • Note Taker: Josh Berkus [Release]
  • Demo: No demo today - see you next week!
  • [ 0:01 ]** Release Updates**
  • [ 0:07 ] KEP o' the Week (Janet Kuo)
    • https://github.com/kubernetes/community/pull/2287
    • For cleanup of frequently created & dropped objects
      • We don't have a good way to garbage collect items which no longer have an owner.
      • Often people update-and-replace instead of modifying
    • Proposal for new GC for these objects.
      • Will be discussed in next API-machinery meeting next week (Wednesday) if you care about the KEP
      • Will give detailed presentation there.
  • [ 0:00 ] SIG Updates
    • SIG API Machinery David Eads
      • Link to slides
      • Delivered in 1.11:
        • Improved dynamic client, easier to use for CRD developers. Everyone should switch to this because the old client will eventually go away.
        • "Null CRD conversion": you can promote a CRD from one version to another, even though there's no API changes. No data transformation, no changes to schema. So very limited for now.
        • Work on feature-branch for Server-side apply.
        • Prep work for making controller-manager start from a config
      • 1.12 work
        • Server-side apply dry run being merged into Master
        • Path to more advanced CRD conversion, field defaults, advanced versioning (design phase).
        • Controller-manager moving to running from config
        • Generic initializers as alpha. May be superseded by admission webhooks. If you need something in Generic Init that isn't satisfied by webhooks, speak up in their meeting to save it.
    • SIG Testing [Steve Kuznetsov] (confirmed)
      • Link to slides
      • Implemented caches for test runs, which is a big performance boost
        • Reduced GH API hits by 1500/hr
        • Bazel build cache lowered test times
      • UX improvements for the k8s bot
        • Now can LTGM and approve in review comment
        • Robots now validate OWNERS files
      • Easier administration
        • Using Peribolos for GH API management
      • Automated branch protection now on all repos
        • Only bots can merge to branches
      • Simpler test Job management: now just needs a container with an entrypoint
      • Merge workflows using Tide are implemented
        • Plan to rollout for 1.12
        • Will include PR status page, yay! Makes it easier to see why your PR is stuck.
      • Testgrid dashboard for conformance tests
        • Including openstack
      • Prow is now being adopted by other orgs
        • Google, Red Hat, Istio, JetStack …
      • Future work:
        • Better onboarding docs
        • Fix tech debt that makes getting started hard
        • Better log viewer, esp now that we have scalability presubmits
        • Clean up config repo
        • Framework for writing bot interactions
        • API for cluster provisioning
      • Questions:
        • What about archival stats on PR status dashboard?
          • Will discuss at sig-testing meeting
        • What about doc on how to write a test?
          • Also really critical, needs help
    • SIG ContribEx Paris
      • Link to slides
      • Contributor Guide
        • Umbrella issue is now closed
        • non-code guide in development - meets on Weds
      • Developer Guide
        • Tim Pepper now taking point on this
        • Reach out to him @tpepper if you can help
      • Contributor.kubernetes.io web site is under early design
        • Different from general community, this one will be just for contributors
        • More modern calendar
        • Prototype up, check it out (link from slides)
        • goal to launch in 90 days
      • Community Management
        • All talking all the time, it's time consuming
        • Contributor summits, first one (run by contribex) in Copenhagen
          • Rolling out new contributor workshop + playground
          • Will have smaller summit in Shanghai (contact @jberkus)
          • Started planning for Seattle, will have an extra ½ day.
            • Registration will be going through kubecon site
          • Manage alacarte events at other people's conferences
        • Communication pipelines & moderation
          • Clean up spam
          • Reduce number of pipelines
          • Some draft moderation guides
          • Also run the Community Meeting
          • Zoom has a bad actor problem, so we're not locking down Zoom permissions, trying not to take away public meetings, looking at new security together with Zoom execs.
          • Moderating k-dev and k-users MLs now
          • If you need to reach moderators quickly, use slack-admins slack channel
          • Slack: 40K users, a lot less moderation required
          • Discuss.kubernetes.io
            • Been successful for tips & tricks and user advice
            • Will be "official" RSN
      • Mentoring
        • Meet Our Contributors is doing well
          • Yesterday's special edition had Steering Committee members
        • Outreachy, only participating twice a year
          • September deadline for winter intern, planning on 1
          • Participating companies can pay for more
        • Group mentoring: the 1:1 hour
          • If your SIG needs to move people up to approver, please contact @paris
        • GSoC, being done by API-machinery
      • DevStats
      • Github Management proposed subproject
  • Announcements
    • Shoutouts - enter yours in #shoutouts slack channel!
      • (jberkus) - @jdumars for inventing, then running, really effective retros for releases.
      • (paris) - shouts to @liggitt @stevekuznetsov and @munnerz for a jam packed, informative, #meet-our-contributors session yesterday! (watch the recording; good info!)
      • (paris) another shout to @arschles @janetkuo for being mentors on the second great episode of #meet-our-contributors yesterday. (also to bdburns, pwittroc, and philips but I will spare their notifications for doing our first AMA with steering committee members)
      • munnerz - shout out to @stevekuznetsov for immediately jumping to spend time debugging and fixing issues with our Prow deployment and tide (not) merging our PRs! looking forward to finally rolling the fix out 🙂 it has caused us issues for 1-2 months now 😄
    • Office Hours is next Wednesday - volunteers to help answer user questions are always appreciated, ping @jeefy or @mrbobbytables if you want to help, otherwise help us spread the word!
    • Next week's meeting won't be streamed, so expect a slight delay on publishing it to YouTube

July 5, 2018

NO MEETING

June 28, 2018 - (recording)

  • Moderators: Jaice Singer DuMars [SIG PM/Release]
  • Note Taker: First Last [Company/SIG]
  • [ 0:00 ]** Demo **- containerd - Phil Estes - estesp@gmail.com
  • [ 0:00 ] Announcements
    • SIG IBMCloud, Autoscaling, and GCP will be updating in August
    • Github Groups [Jorge Castro]
    • Shoutouts this week (Check in #shoutouts on slack)
      • jberkus: To Jordan Liggitt for diagnosing & fixing the controller performance issue that has haunted us since last August, and to Julia Evans for reporting the original issue.
        • Maulion: And another to @liggitt for always helping anyone with a auth question in all the channels with kindness
      • jdumars: @paris - thank you for all of your work helping to keep our community safe and inclusive! I know that you've spent countless hours refining our Zoom usage, documenting, testing, and generally being super proactive on this.
      • Nikhita: shoutout to @cblecker for excellent meme skills!
      • Mrbobbytales: Just want to give a big shout out to the whole release team. Thanks for all your effort in getting 1.11 out the door 🙂 Seriously, great job!
      • Misty: @chenopis for last-minute 1.11 docs-related heroics!
      • Misty: @nickchase for amazing release notes!
      • Misty: @jberkus for being a very patient and available release lead as I was on the release team for the first time
      • Jberkus: @liggitt for last-minute Cherrypick shepherding, and @nickchase for marathon release notes slog
      • Jberkus: and @misty @AishSundar @tpepper @calebamiles @idvoretskyi @bentheelder @cjwagner @zparnold @justaugustus @Kaitlyn for best release team yet
      • Tpepper: shoutout to @jberkus for his leadership of our team!
  • [ 0:00 ]** Release Retrospective for 1.11**
    • Retro doc
      • SIG Release will do deep dive on retrospective details, but today this meeting focused on the high level cross-project topics like:
        • Release timeline evolution and deadlines
        • How to better track major features and changes that are in need of docs, test cases, release noting
        • How do we get user/distributor/vendor testing of betas and rc's. Consumption is harder when docs and kubeadm upgrade path aren't there yet.
    • Retro Part II (detail retro): Tuesday, July 3rd, 10am, https://zoom.us/j/405366973

July 15, 2018 - recording

June 21, 2018 - (recording)

  • Moderators: Arun Gupta [Amazon / SIG-AWS]
  • Note Taker: Chris Short and Jorge Castro [SIG Contrib Ex]
  • [ 0:00 ]** Demo **-- Agones - Dedicated Game Server Hosting and Scaling for Multiplayer Games on Kubernetes [Mark Mandel, markmandel@google.com] (confirmed)
  • [ 0:00 ]** Release Updates**
    • 1.11 [Josh Berkus - Release Lead]
      • Code Thaw on Tuesday, held changes from Code Freeze have now cleared the queue.
        • All 1.11 changes now need to be cherrypicked.
      • RC1 was released yesterday, please test!
      • Status is currently uncertain. Probability of a release delay is 50%, will make call at Burndown meeting 10am tomorrow.
      • CI Signal Issues:
      • Release notes collector is still broken, please check the release notes to make sure all of your changes represented! An estimated 20-30 release notes are missing. Contact (@nickchase / nchase@mirantis.com) if you find something missing.
    • 1.12 [Tim Pepper - Release Lead]
    • Patch Release Updates
      • 1.8.14
      • 1.9.9 release schedule
      • 1.10.5
  • [ 0:00 ] KEP o' the Week (Yisui)
  • [ 0:00 ] Open KEPs [Kubernetes Enhancement Proposals]
  • [ 0:00 ] SIG Updates
  • [ 0:00 ] Announcements
    • Please pin your SIG meeting info and agenda doc in your SIG slack channel. Now that the main calendar is not on https://kubernetes.io/community/ meeting info is less discoverable without these links.
      • **SIG Chairs/TLs - please check your email (sent to k-sig-leads@). New zoom settings and moderation controls. Let's keep our meetings safe and transparent. **
    • All SIGs - please take time to look at the "help wanted" and "good first issue" labels, available across all Kubernetes repositories. They're meant to highlight opportunities for new contributors. Please ensure that they're being used appropriately (the "good-first-issue" especially has fairly specific requirements for the issue author): https://github.com/kubernetes/community/blob/master/contributors/devel/help-wanted.md
    • Shoutouts this week (Check in #shoutouts on slack)
      • Jason DeTiberus: @neolit123 (Lubomir Ivanov) for all of the docs contributions for kubeadm v1.11
      • Jason DeTiberus: @jrondeau (Jennifer Rondeau) for the relentless work on improving our docs and helping bring some more structure to the docs process for sig-cluster-lifecycle
      • @neolit123 (Lubomir Ivanov): @jdetiber (Jason DeTiberus), @liz (Liz Frost), @cha (Chuck Ha), @timothysc (Timothy St. Clair) and @luxas (Lucas Kladstrom) for the relentless grind trough kubeadm 1.11 backlog potentially making it the best release thus far.
      • @austbot (Austin Adams): To @lukaszgryglicki (Lukasz Gryglicki) for DevStats, which is Awesome!!
      • Stealthybox (Leigh Capili): shoutout to @oikiki (Kirsten) for being very welcoming to new contributors
      • Nikhita: shoutout to the whole test-infra community for actively using emojis in issues, PRs and slack. It's pretty subtle but it goes a LONG way in making the project and community more friendly and welcoming to new contributors!! cc @fejta (Erick Fejta) @bentheelder (Benjamin Elder) @cblecker (Christoph Blecker) @stevekuznetsov (Steve Kuznetsov)
      • @misty (Misty Stanely-Jones): @Jesse (Jesse Stuart) for fixing CSS relating to tab sets in docs! 🙌
      • @fejta (EricK Fejta): @krzyzacy (Sen Lu) and @bentheelder (Benjamin Elder) for being ever diligent about reviewing PRs in a timely manner
      • JoshBerkus: to @kjackal (Konstantinos) for actually beta-testing 1.11 and spotting a bug before RC1
      • @oikiki (Kirsten): shoutout to @gsaenger for always generously helping new folks get started contributing to k8s! (and also for completing her first major technical PR!) WOOP WOOP!
      • @gsaenger (Guinevere Senger) Um... no, really, I couldn't have done it without so much help from @cblecker (Christoph Blecker) and @cjwagner (Cole Wagner) and @fejta (Erick Fejta)and @bentheelder (Benjamin Elder). Everyone was super nice and patient and helped me learn. ❤️ So, shoutouts to them. I'm so grateful.

June 14, 2018 - (recording)

  • Moderators: Zach Arnold [Ygrene Energy Fund/SIG Docs]
  • Note Taker: Jorge Castro [Heptio/SIG Contribex] and Solly Ross [Red Hat/SIG Autoscaling]
  • [ 0:00 ]** Demo **-- Building Images in Kubernetes [Priya Wadhwa, priyawadhwa@google.com] (confirmed)
    • https://github.com/GoogleContainerTools/kaniko
    • https://docs.google.com/presentation/d/1ZoiQ3cuQNJJciKq_JvqTty_tcoaRKNyYRzgCBbTumsE/edit?usp=sharing
    • Tool for building container images without needing to mount in Docker socket
      • Extracts base image to file system
      • Downloads build context tarball from storage (e.g. S3, more on the way)
      • Executes commands listed in Dockerfile
      • Snapshots in userspace after each step
      • Ignores mounted directories during snapshots
    • Can be run in gVisor as well
    • Questions:
      • do you have to use dockerfiles, or can you use other instruction sets
        • Only dockerfiles right now, but file issues if you want other things
      • Which dockerfile verbs are supported?
        • All of them
      • Can the bucket be S3 or DO Space?
        • Working on a PR right now to support other solutions
      • Feature parity with docker build?
        • Yes
    • Link to slides.
  • [ 0:00 ]** Release Updates**
    • 1.11 [Josh Berkus - Release Lead]
      • Next Deadline: RC1 and branch on June 20th
      • Less than a week of code freeze left!
      • Docs are due and overdue; if you have a feature in 1.11,_ you should have already submitted final docs_. Contact the docs team.
      • CI signal is good, a few tests being flaky, especially alpha-features.
      • Only 2 issues and 6 PRs open; currently more stable than we've ever been! Thanks so much to everyone for working to get stuff in the release early.
    • 1.12 [Tim Pepper - 1.12 Release Lead]
      • Tim Pepper as Lead
      • Almost finished building 1.12 team, contact @tpepper on Slack to join.
        • Needed:
          • PR triage (tentatively adding role separate from issue triage)
          • Branch manager
    • Patch Release Updates
      • 1.10.4?
  • [ 0:00 ] KEP o' the Week
    • SIG Cloud Provider KEP: Reporting Conformance Test Results to Testgrid [Andrew Sy Kim]
      • Formerly WG-Cloud-Provider
        • Standards and common requirements for Kubernetes cloud provider integrations
        • Improving docs around cloud providers (how to work with different integration features)
        • Improving testing of cloud providers
      • KEP is basically "Why we want conformance tests reported by the cloud providers"
        • We didn't have a formal way to do this without KEP
        • SIG Testing infra wasn't available back then, so now we have testgrid and a way to report tests, etc. Gives providers instructions to follow to contribute results.
        • SIG Openstack has been pioneering this work
        • We want all providers to do this eventually, we'll be reaching out to all the cloud providers to give them visibility that this KEP exists.
        • Still missing some details, will address those as more experience is developed in how to do better test
      • Q:
        • Coverage is listed as out of scope, but is a benefit, will coverage improvements be a follow-on KEP?
          • Eventually, but currently not necessarily an immediate priority
    • https://github.com/kubernetes/community/pull/2224
  • [ 0:00 ] Open KEPs [Kubernetes Enhancement Proposals]
  • [ 0:00 ] SIG Updates
    • SIG Windows [Patrick Lang]
      • Trello board - maps K8s features to Windows release needed
      • Releasing twice a year in the Windows Server Semi Annual Channel
        • Like 18.03, 17.09, etc.
        • We've had to make changes to Windows Server to make Kubernetes work well. For example, symbolic links in Windows v. Unix.
        • Board is tagged with the right version of Windows to use to get a particular Kubernetes feature working, but in general, use the latest release if possible
      • Kube 1.11
        • Lots of features with Windows, e.g. Kubelet stats
      • For the future
        • Currently using dockershim, trying to figure out how to support other CRI implementations
        • Working with other CNI plugins (Flannel, OVN, Calico)
        • Trying to get support for showing test results via Prow, Kubetest, TestGrid
        • Want to move to GA eventually, with 2019 Windows release (extended support cycle)
      • Questions:
        • Q: Unix-style symlinks in Windows?
          • Have something similar to unix-style symlinks and hardlinks, needed to make some symlink changes to make sure you can't traverse in an insecure way. Code either in Kubelet or Go winio library
          • Hardlinks not recommended, stick to the symlinks.
        • Q: is windows currently dockershim+embedded EE
          • Currently uses Docker EE Basic for Windows (as published by Docker), used for testing
          • Potentially switching to crio eventually, or containerd
    • SIG Apps [Kenneth Owens]
      • Helm
        • Helm moved to a separate CNCF project (see last meeting)
        • Helm 2 stability release
        • Helm 3 proposal merged, work continuing
      • Application Resource
        • Seeks to describe application as running
        • Controller soon
        • WIP
      • AppDef WG
        • Winding down
        • Proposal for common labels and annotations will be merged in partial form
      • Ksonnet
        • New release
      • Decentralized charts repo coming
      • Skaffold: kustomize support
      • Workloads API
      • Questions:
        • Why didn't charts go with Helm to a separate CNCF project
          • Current Status: Charts are listed as a subproject of SIG Apps.
          • Chart maintainers aren't necessarily Helm maintainers
          • Trying to figure out the right model for maintainership
          • Is the charts tooling part of the charts subproject, or Helm?
            • Unsure, currently part of the charts subproject, but points to the kubernetes/helm repo
    • SIG Docs [Jennifer Rondeau]
      • Zach is out sick today, fulll update Augustish, feel better Zach!
      • 1 minutes Jennifer update
        • We're making great progress on fixes for the hugo migration, we've plowed through a bunch, thanks to all the new contributors who have been diving in.
        • Thanks to all of you who have submitting 1.11 docs
        • If you're behind on 1.11 docs, please submit them asap!
  • [ 0:00 ] Announcements
    • K8s Office Hours Next Week, Wednesday 6/20
      • Volunteers always sought, ping @jorge or @mrbobbytables on slack
      • Users who participate will be entered in a raffle to win a k8s shirt!
    • SIG Leads, if you haven't uploaded your meeting videos to the youtube channel recently, please try to catch up. Ping @jorge if you need help.
    • SIG Architecture has a new meeting time at 11PST every other Thursday after this meeting. Also, there is a new Zoom link you can get from joining the mailing list. Check out the SIG Arch readme for more information.
    • Shoutouts this week (Check in #shoutouts on slack)
      • (Josh Berkus) @liggitt and @dims for pitching in and doing a ton of work on PRs for 1.11, across all of Kubernetes.
      • (Jennifer Rondeau) @misty for stepping in to help with ALL things docs no matter how crazy they get or how much else she has on her plate 🎉
      • (Aish Sundar) @justaugustus for giving us a huge head start and herding all the cats to get a stellar 1.12 release team already in place. Thanks a lot!
      • (Misty Stanley-Jones + Aish Sundar) @jberkus for herding 1.11 release cats! 🐱
      • To echo what @misty said, HUGE shoutout to @jberkus for being an awesome patient leader throughout 1.11 cycle. It was such a learning experience seeing him work through issues calmly, all the while encouraging the RT team to lead in our own little way.
      • Jason DeTiberius
        • @neolit123 (Lubomir Ivanov) for all of the docs contributions for kubeadm v1.11
        • @jrondeau (Jennifer Rondeau) for the relentless work on improving our docs and helping bring some more structure to the docs process for sig-cluster-lifecycle

June 7, 2018 - (recording)

  • Moderators: Jaice Singer DuMars [SIG Release/Architecture]
  • Note Taker: Austin Adams [Ygrene Energy Fund]
  • [ 0:00 ] Demo -- YugaByte ~ Karthik Ranganathan [karthik@yugabyte.com] (confirmed)
    • Karthik Ranganathan
    • Answers from Q&A:
      • @jberkus - For q1 - YB is optimized for small reads and writes, but can also perform batch reads and writes efficiently - mostly oriented towards modern OLTP/user-facing applications. Example is using spark or presto on top for use-cases like iot, fraud detection, alerting, user-personalization, etc.
      • q2: operator in the works. We are just wrapping up our helm charts https://github.com/YugaByte/yugabyte-db/tree/master/cloud/kubernetes/helm
      • q3: the enterprise edition does have net new DB features like async replication and enforcing geographic affinity for reads/writes, etc. Here is a comparison: https://www.yugabyte.com/product/compare/
      • q4: You cannot write data using redis and read using another API. Its often tough to model across api's. Aim is to use a single database to build the app, so support common apis
      • The storage layer is common
      • So all APIs are modeled on top of the common document storage layer
      • The API layer (called YQL) is pluggable
      • Currently we model Redis "objects" and Cassandra "tables" on top of this document core, taking care to optimize the access patterns from the various APIs
      • We are working on postgres as the next API
  • [ 0:00 ]** Release Updates**
    • 1.11 [Josh Berkus - Release Lead]
      • Next Deadline: Docs Complete, June 11
        • All listed features have docs in draft -- Thanks!
        • However: non-listed (minor) changes, please make sure you have docs!
      • Currently in Code Freeze
        • Only 1.11 patches, must be approved and critical-urgent
        • Down to 11 PRs
        • Still using the old Milestone Munger, so expect the same annoying behavior, sorry.
          • Particularly: can't take back-branch PRs.
        • No New Features/Cleanups Now, please
          • All new features have draft documentation, however, there are lots of small patches not big enough to be a feature but we don't know if we have documentation for those.
          • Please make sure your 1.11 small patches have documentation.
        • Code freeze ends June 19th.
        • Docs need to be complete by June 11th
      • CI Signal looking good
        • Recent GKE breakage fixed.
          • Only upgrade/downgrade tests failing, PR in progress.
        • Thanks everyone for responding to test fails quickly!
      • Scalability/Performance
        • Currently passing all performance tests
          • Thanks to everyone who worked on this early in the cycle!
        • New performance presubit test
          • Kudos to SIG-scalability for getting this done.
    • 1.12
  • **[ 0:00 KEP Highlight ] **- Kustomize [ Jeff Regan ]
  • [ 0:00 ] SIG Updates
    • **Multicluster **- Quinton Hoole (confirmed)
      • Sig Intro
        • Focused on solving challenges with running multiple clusters and applications therein.
        • Working on Cluster Federation, Cluster Registry(cluster registry for k8s for cluster reuse) and Multi cluster ingress.
      • FederationStatus
        • Development has split between federation v1 and v2.
        • Federation v1 is a POC and no further development planned, users showed they needed something different.
        • Moving forward Federation v2 will focus on reusable components, federation specific apis and implementations of higher level apis and federation controllers.
        • v2 Alpha is planned for June.
        • Behind the effort is RedHat and Huawei.
      • Cluster Registry Status
        • Grew out of Federation v1. Allows reusable clusters and discovery. Google Cloud is supported for now, but more coming. Implementation is based on CRDS.
        • Apis/CRDS in beta.
      • Link to slides
    • Network - Tim Hockin - (confirmed) (or dc
      • Sig Intro
      • In-progress Network Plumbing CRD Spec doc:
      • Network Service Mesh proposal slides
      • DevicePlugins (from Resource Management WG) have some intersection with networking, there have been many demos/PoCs but so far no consensus on how DPs should interact with existing CRI networking APIs
      • CoreDNS is now GA in 1.11
      • IPVS Proxy mode is now GA in 1.11 (anyone have a link?) but not default
      • Looking at breaking out ingress into a bunch of individual route resources instead of one monolithic list.
      • IPv6 discussions around how to support dual-stack are ongoing
      • We are working on test flakes, we don't have a fix yet but HELP WANTED
    • VMware - Steve Wong (confirmed)
      • Vmware Cloud Provider
        • The target is 1.12.
        • Working through some process level things. This project is retained as a SubProject.
        • Creating a working group to handle testing
      • Link to deck, 4 slides, estimated 5 min:
  • [ 0:00 ] Announcements
    • Happy birthday, Kubernetes!
    • Shoutouts - _powered by slack #shoutouts _- if you see someone doing great work give them a shoutout in the slack channel so we mention those here!
      • "@jrondeau for working on the weekend to get 1.11 doc builds working again!!" -mistyhacks
      • "@andrewsykim for all the effort in getting SIG Cloud Provider off the ground!" -fabio
      • "@neolit123 for really stepping up lately to help with user facing issues for the kubeadm 1.11 release. we really appreciate your contributions to the sig" -stealthybox
      • "@cblecker who is everywhere keeping tabs on things and people on track." -gsaenger
    • Help Wanted
      • [Stephen Augustus]** **1.12 release team is forming, see #sig-release for more info. Roles & Responsibilities info here. Volunteers needed!
      • Help wanted on Sig Network Test Flakes reach out to #sig-network on slack
      • Anyone Interested in learning prow and helping with the transition from. Munger to prow will be helpful. See @jberkus

May 31, 2018 - (recording)

  • Moderators: Jorge Castro [SIG Contributor Experience]
  • Note Taker: First Last [Company/SIG]
  • [ 0:00 ]** Demo **-- Aptomi - application delivery engine for K8S [Roman Alekseenkov]
  • [ 0:13 ]** Release Updates**
    • 1.11 [Josh Berkus - Release Lead]
      • Next Deadline: Draft doc PRs due June 4th.
      • Currently in Code Slush. Requiring milestones, sorry for lack of warning on that.
        • Were not able to move to Prow milestone maintainer or Tide for this release.
      • Code Freeze Starts Tuesday, June 5th
      • If your feature won't be ready, now is the time to update your issue in the Features repo.
      • CI Signal -
        • Almost green, last few fixes merged.
        • 1 open tracking issue - Scale Density test for 30 pods
        • Conformance tests results (GCE and OpenStack) now in Release blocking dashboard
        • @misty on slack for release docs issues
    • Patch Release Updates
      • x.x
      • y.x
  • [ 0:00 ] Introduction to KEPs [Kubernetes Enhancement Proposals] [Caleb Miles]
    • We'll be highlighting KEPs in community meetings
    • tracking how decisions are made: identify the problem + find a sig for motivation agreement + documenting it for everyone
    • Slides
  • [ 0:00 ] SIG Updates
    • SIG OpenStack [David Lyle and Chris Hoge]
    • SIG Node [Dawn Chen]
      • Made a steady progress on all 5 areas in Q2: 1) node management including Windows, 2) application / workload management, 3) security, 4) resource management and 5) monitoring, logging and debuggability.
      • On node management
        • Promoted dynamic kubelet config to beta
        • Refactor the system to use node-level checkpointing manager
        • Proposed a probe-based mechanism for kubelet plugins: device, csi, etc.
        • Proposed a design to address the scalability issue caused by large node object and approved by the community. Had a short-term workaround in v.11, and plan to work on the long term solution in v1.12.
      • Together with sig-windows, we made many progress on Windows support which including stats, node e2e for Windows Container Image. More works on SecurityContext, storage and network in next release.
      • Both CRI-O and containerd are GA in this release.
        • More enhancements on CRI for container logs
        • Many enhancements to crictl, the tool for all CRI-compliant runtimes. Expecting to be GA in v1.12
        • Announced CRI testing policy to the community, and introduced node exclusive tags to e2e.
      • On security
        • For 1.11, making all addons use default seccomp profile. Expecting to promote it to beta and enable it by default.
        • Proposed a design and alpha-level Kubernetes API for sandbox. Working closely with Kata community and gVisor community on integration of CRI-compliant runtime.
        • WIP for user namespace support
        • Made progress on node TLS bootstrap via TPM.
      • On resource management side, we made the progress on promoting sysctl to beta and proposed ResourceClass to make resource support extensible.
      • Made the steady progress on debug pod, but unfortunately due to backforth review from the different reviewers on API changes, we couldn't have alpha support in v1.11. Escalate it to sig-architecture.
      • On the logistics side
        • Sig-node holds weekly meeting on Tuesday, 10am (Pacific Time)
        • Please join kubernetes-sig-node googlegroup to have access to all design docs, roadmap and emails.
        • Derek and I are working on sig-node charter, which is still under review and discussion.
  • [ 0:00 ] Announcements
    • Deprecation Policy Update (Important!)
    • SIG Leads - check the top of this document for a link to the SIG Update schedule.
    • Shoutouts - Someone going above and beyond? Mention them in #shoutouts on slack to thank them.
      • Aish Sundar - Shoutout to @dims and OpenStack team for quickly getting their 1.11 Conformance results piped to CI runs and contributing results to Conformance dashboard!
      • Aish Sundar - Shoutout to Benjamin Elder for adding Conformance test results to all Sig-release dashboards - master-blocking and all release branches.
      • Josh Berkus and Stephen Augustus - To Misty Stanley-Jones for aggressively and doggedly pursuing 1.11 documentation deadlines, which both gives folks earlier warning about docs needs and lets us bounce incomplete features earlier
    • Help Wanted
      • Looking for Mandarin-speakers to help with new contributor workshop and other events at KubeCon Shanghai. If you can help, please contact @jberkus / jberkus@redhat.com
      • KEP-005 - Contributor Site - ping jorge@heptio.com if you can help!
    • Meet Our Contributors (mentors on demand)
    • Stackoverflow Top Users
    • Thread o' the week: How has Kubernetes failed for you?

May 24, 2018 - (recording)

  • Moderators: Josh Berkus [SIG-Release]
  • Note Taker: Tim Pepper [VMware/SIGs Release & ContribX]
  • [ 0:00 ]** Demo **-- Workflows as CRD [ Jesse Suen (Jesse_Suen@intuit.com)]
    • Link to slides: https://drive.google.com/file/d/1Z5TMIr6r4hC7N5KeVqajC3c3NcYqK4_z/view?usp=sharing
    • Link to repositories: https://github.com/argoproj/argo
    • Argo: a fancy job controller for workflows, DAGs implemented as CRD. Originally intended for CI/CD pipelines, but is seeing usage for other workflows like machine learning.
    • Used with kubeflow
    • Component architecture interfacing wsith k8s api server and leveraging sidecars in pods for workload artifact management
    • Argo command line gives validation of commands, but is effectively a kubectl wrapper
    • Workflows can be defined as a top down iterative list of steps, or as a DAG of dependencies
  • [ 0:16 ]** Release Updates**
    • 1.11 Update [Josh Berkus, Release Lead]
      • Next Deadline: Docs Placeholder PRs Due Tomorrow for feature list!!!
      • Code Slush on Tuesday
      • Current CI status and schedule
        • CI Signal : Tracking 3 open issues, all are test issue being actively worked on.
        • Code freeze coming June 5, make sure your issues/PRs are up to date with labels and priorities and status
      • Changing Burndown Meeting Schedule, please comment..looking for less conflicted times and ones friendlier for more timezones
    • Patch Release Updates?
      • 1.10.3 released monday
  • [ 0:21 ] SIG Updates
    • SIG Service Catalog [Doug Davis] (confirmed)
      • Beta as of Oct 2017
      • Key development activities
        • New svcat cmd line tool (similar to CloudFoundry's way of things)
        • NS-scoped brokers - still under dev
        • Considering moving to CRDs instead of dedicated apiserver
      • Finalizing our v1.0 wish-list
        • NS-scoped brokers
        • Async-bindings
        • Resolve CRD decision
        • Generic Broker & Instance Actions
        • GUIDs as Kube "name" is problematic
      • SIG has recently been actively mentoring and onboarding newcomers
    • SIG Auth Tim Allclair
      • Pod TokenRequest API and ServiceAccountTokenProjection improving for 1.11
      • Client-go gaining support for x509 credentials and externalizing currently in-tree credential providers
      • Scheduling policy design thinking happening ahead of 1.12
      • Audit Logging: improved annotation metadata coming around auth and admission for logs
      • Node Isolation: nodes no longer able to update their own taints (eg: exploit to attract sensitive pod/data to a compromised node)
      • Conformance: KEP PR open on security related conformance testing to give better assurance that best practices are in use or validate a hardened profile is active. Likely not 1.11 rather 1.12.
      • Bug bounty is WIP
    • SIG Storage Brad Childs Slides
      • Had SIG face-to-face meeting last week. ~40 people and 19 companies present
      • Storage functionality is moving out of tree by way of the CSI interface
        • CSI spec moving from 0.2 to 0.3 soon
        • Lots of CSI related features coming in k8s 1.11
        • Aiming for out-of-tree feature parity relative to existing in-tree
      • Feature areas: Snapshots, topology aware (scheduling relative to location of PV) and local PV, local disk pools/health/capacity, volume expansion and online resize
      • Testing: multi-phased plan to inventory and improve test coverage and CI/CD, including test coverage on other cloud providers beyond GCE. VMware committed resources, looking for commit from others.
      • Operators: external provisioners, snapshot and other operator frameworks underway. Currently not looking to do a shared operator library to span SIG-Storage repos.
      • Metrics: there are a lot. Some are cloud provider specific. Goal is to assist SRE's in problem determination and corrective action.
      • API Throttling: api quota exhaustion at cloud provider and api server are frequently causing storage issues. Looking at ways to streamline.
      • External projects: SIG has something like 20 projects and is breaking them apart, looking for owners and out of tree locations for them to better live. Projects should move to CSI, a kubernetes-sigs/* repo, a utility library, or EOL
  • [ 0:00 ] Announcements
    • Shoutouts this week (Check in #shoutouts on slack)
      • Big shoutout to @carolynvs for being welcoming and encouraging to newcomers, to @paris for all the community energy and dedication, and to all the panelists from the recent Kubecon diversity lunch for sharing their experiences.
      • Big shoutout to @mike.splain for running the Boston Kubernetes meetup (9 so far!)
      • everyone at svcat is awesome and patient especially @carolynvs, @Jeremy Rickard & @jpeeler who all took time to help me when I hit some bumps on my first PR.
    • Help Wanted
      • SIG UI is looking for new contributors. Check out their issue log to jump in; also listen to their SIG UI call today where they explained more and answered questions. #sig-ui in slack for on-ramp help. Notes from the call
      • Looking for more mentors as we kick off our contributor mentoring programs. Fill out this form (works for looking for mentorship, too). Pardon the dust as we do a mentor recruiting drive.

May 17, 2018 - (recording)

  • Moderators: Paris Pittman [SIG Contributor Experience]
  • Note Taker: Solly Ross
  • Demo: Gardener Demo (vasu.chandrasekhara@sap.com and rafael.franzke@sap.com)
    • [occurred towards end of video instead]
    • Open Source: https://gardener.cloud/
    • Mission
      • Manage, maintain, operate multiple k8s clusters
      • Work across public and private clouds
    • Architecture
      • Self-hosted
      • Kube-centric
      • Steps
        • Boot initial "garden" cluster using kubify (https://github.com/gardener/kubify, open source)
        • Deploy Gardener to "garden" cluster + dashboard (Gardener is extension API server)
        • Run/use "seed" cluster to run control plane components, terraformer for each cluster "shoot" cluster (1 seed per hosting platform, region, etc)
        • Each set of control plane components corresponds to a "shoot" cluster with actual nodes (machine controller + machine API objects control this)
        • VPN between "seed" cluster and "shoot" clusters so that API server, monitoring can talk to node
    • Secrets are created for each shoot to easily download kubeconfigs, etc
    • Declarative config for each cluster ("shoot") with status info as well
    • Uses cluster API machine resources, working with Cluster API WG
    • Q: is it stable, or in development?
      • A: used internally, but still in development
    • Q: baremetal support?
      • If there's an infra API that can be used to control baremetal, then that can be used
    • Detailed Blog describing Gardener's architecture: https://kubernetes.io/blog/2018/05/17/gardener/
  • Release Updates:
    • **1.11 **[Josh Berkus, RT Lead / Aish Sundar CI Signal Lead] (Week 7)
      • Next Deadline: Docs, Open Placeholder PRs Required, May 25th
      • 1.11.0 Beta0 released yesterday.
      • We are delaying/shortening Code Freeze as discussed. See new calendar for current deadlines.
        • Stable passing tests, low bug count → small code freeze periods → more development time
        • Code slush: May 29th
        • Code freeze: June 5th
      • Many thanks to dims, liggit, timothysc, krousey, kow3ns, yliaog, k82cn, mrhohn, msau42, shyamvs, directxman12 for debugging fails and closing issues, and AishSundar, Cole Mickens, Mohammed Ahmed, and Zach Arnold for working with the SIGs to get attention on issues and test failures.
      • Help wanted to on scalability and performance
    • **1.10 **[Maciek Pytel, PRM]
  • SIG Updates:
    • Scheduling** **[Bobby Salamat]
      • Priority and Preemption
        • Have gotten good feedback over the past quarter
        • Moving to beta/enabled by default in 1.11
      • Equivalence Cache Scheduling
        • Caching predicate results for given inputs as long as conditions don't change in cluster
      • Gang Scheduling
        • Schedule a bunch of pods together, don't schedule only a subset
        • Kube-arbitrator has a prototype that seems to work well
        • Need to collect more requirements
        • Q: Can we use batch scheduling to improve throughput?
          • A: Maybe use a Firmament-like approach?
          • Q: is this a step along the way for perf optimization on the current schedule?
          • A: Engineers from Huawei are working on this, but ran into issues with things like pod-antiafinity, actually binding the pods
      • Taint based eviction to beta
      • Scheduling framework
        • Still in design framework
      • Pod scheduling policy
        • Lots of opinions, progress has been slow
        • Existing design proposal with lots of opinions
    • Scalability [Bob Wise]
      • Slides
      • Schedule for large runs of perf is even-odd day
      • Different Per Axes (there's not just one axis, e.g. "number of nodes")
        • Nodes, Pod Churn, Pod density, Networking, Secrets, Active Namespaces
      • Pro Tips
        • Lock your etcd version
        • Test your cluster with Kubemark
      • Recommended reading in slides
        • Perf regression study
        • Scalability good practices
      • WIP Items
        • Better testing of real workloads (cluster-loader)
        • More scalability testing in presubmit tests
          • Concerns around run time issues
        • Sonobouy per testing
      • Q: Limitations on scalability come down to etcd perf, do we work with etcd engineers?
        • A: Perf is generally not an etcd issue wrt bottlenecks
        • A: Etcd tends to be regressions across etcd versions, not etcd as bottleneck
        • A: Range locking issues being improved in 3.3,3.4
        • A: talk to Shyam about this for more info
    • API Machinery [Daniel Smith, confirmed]
      • New Dynamic client with better interface!
        • Old is under "deprecated" directory
        • Clientside QPS rate limit behavior changed
      • CRD Versioning
        • Design issue with versioning priorities found, but no-op conversion will still land in 1.11
      • Apply WG
        • Feature branch for apply, trying to put things in master when possible
        • Won't reintegrate before 1.11 (feature branch work will continue through code freeze)
  • Announcements:
    • Shoutouts!
      • Warm welcome to @liz and @cha for their journeys in joining the k8s org! Both of you have been having a big impact in #sig-cluster-lifecycle - stealthybox
      • @chancez and @danderson for a great conversation on bare metal options and concerns! - mauilion
      • shoutout to @liggitt, master wrangler of e2e test bugs. Jordan has fixed many "fun" bugs. Thanks for helping keep things green! 😄 - bentheelder
      • As a new contributor, I can 100% endorse @carolynvs for being REALLY GOOD at bringing in new contributors, and dedicating a lot of time and effort to make sure they are successful. -teague_cole
    • Help Wanted!
      • SIG UI looking for new contributors to go up the ladder to maintainers. Start with an open issue and reach out to the mailing list and slack channel.
      • SIG Scalability is looking for contributors!
      • We need more contributor mentors! Fill this out.
        • The next Meet Our Contributors (mentors on demand!) will be on June 6th. Check out kubernetes.io/community for time slots and to copy to your calendar.
    • Kubecon Follow Ups
    • Other
      • Don't forget to check out discuss.kubernetes.io!
      • DockerCon Kubernetes Contributor AMA during Community Day - June 13th. 3 hour window; specific time TBA

May 10, 2018 - (recording)

  • Moderators: Tim Pepper [SIG Contributor Experience, SIG Release]
  • Note Taker: Jorge Castro / Christian Roy
  • Demo: Ambassador API Gateway built on Envoy/K8S (https://www.getambassador.io) (richard@datawire.io)
    • https://github.com/datawire/ambassador
    • Link to slides
    • Kubernetes only, simple architecture
      • Apache licensed
      • Declarative configuration via kubernetes annotations
      • Built on Envoy - designed for machine configuration
      • Operates as a sidecar to envoy, async notified of config changes and configures envoy accordingly
      • Concept of shadowing traffic - takes all the incoming requests and sends it to another service but filters the responses, good for debugging in production.
  • Release Updates:
  • SIG Updates:
    • Architecture [Brian Grant]
      • Working on our charter
        • Improving conformance tests
        • Provide technical expertise/advice/overview across SIGs
        • Formalizing proposal processes into KEPs, more structure, make it more obvious
        • API review process. Used to be informal, we want to formalize that.
      • Weekly meeting with alternating full meeting (decisions) and office hours (discussions)
        • Office hours are available for people who want to ask questions on how to best implement incoming ideas (API review, etc.)
      • Meeting and note information
    • Contributor Experience [Paris Pittman]
  • Announcements:

    • Shoutouts!

      • See someone doing something great in the community? Mention them in #shoutouts on slack and we'll mention them during the community meeting:
      • Ihor Dvoretskyi thanks @justaugustus, who made a GREAT job as a Kubernetes 1.11 release features shadow
      • Josh Berkus to Aish Sundar for doing a truly phenomenal job as CI signal lead on the 1.11 release team
      • Tim Pepper to Aaron Crickenberger for being such a great leader on the project during recent months
      • Chuck Ha shouts out to the doc team - "Working on the website is such a good experience now that it's on hugo. Page rebuild time went from ~20 seconds to 60ms" :heart emoji:
      • Jason de Tiber would like to thank Leigh Capili (@stealthybox) for the hard work and long hours helping to fix kubeadm upgrade issues. (2nd shoutout in a row for Leigh! -ed)
      • Jorge Castro and Paris Pittman would like to thank Vanessa Heric and the rest of the CNCF/Linux Foundation personnel that helped us pull off another great Contributor Summit and Kubecon
      • Top Stackoverflow Users in the Kubernetes Tag for the month
        • Anton Kostenko, Nicola Ben, Maruf Tuhin, Jonah Benton, Const

    • Message from the docs team re: hugo transition:

      • We've successfully migrated kubernetes.io from a Jekyll site framework to Hugo. Any open pull requests for k/website need to be revised to incorporate the repo's new content structure. (Changes in docs/ must now change content/en/docs/.)
      • More about the framework change: https://kubernetes.io/blog/2018/05/05/hugo-migration/

    • KEP Section for the Community Meeting? [Jorge Castro]

      • Lots of KEPs coming in via PR, should we have current KEPs in flight as a standing agenda item in the community meeting?
      • When starting a KEP, send an email FYI to the appropriate SIGs and Arch as github notifications are noisy and missed.
      • Would be good to help us bootstrap the KEP processes for people if we got some visibility on them, but still need a site of KEPs

    • Kubernetes Application Survey results [Matt Farina] WG

      Help Wanted?

April 26, 2018 - (recording)

  • Moderators: Jorge Castro [SIG Contributor Experience]
  • Note Taker: Christian Roy
  • Demo: Gitkustabe: Build and deploy docker images to Kubernetes using git push (shahidh@hasura.io, tiru@hasura.io)
  • Release Updates:
    • **1.11 **[Josh Berkus, RT Lead]
      • Features are now frozen!
      • 44 filed features
      • Test Status is Red
        • Master-upgrade: 11 out of 12 jobs failing
        • Master-blocking: 5 out of 26 jobs failing
        • Issues filed
          • Some SIGs not responding to issues
          • SIG responsible to debug why test failing, please look at your issues and start to prioritize them!
      • Next Deadline: Beta Release May 15th
        • Will currently be blocked by failing tests.
    • 1.10 [Maciek Pytel, PRM]
      • Branch frozen for 1.10.2, release planned for April 27th or Monday April 30th
  • **Graph of the Week: **Slack Stats [Paris Pittman]
    • Slack Stats
      • 35k users with 5k weekly active users
      • Produced Quarterly
  • SIG Updates:
    • Thanks to test infra folks for labels
    • Cluster Lifecycle [Tim St. Clair]
    • Autoscaling [Solly Ross]
      • HPA v2 improvements (https://github.com/kubernetes/community/pull/2055)
        • Label selectors for metrics
        • Support for averages on object metrics
        • Slight changes to structure of object (Unify metrics sources)
      • Better e2e tests on all HPA functionality
        • Movement along the path to blocking HPA custom metrics e2e tests
      • VPA work coming along, alpha soon (demo at KubeCon)
      • Come say hi at KubeCon (Intro and Deep Dive, talks on HPA)
    • PM [Jaice Singer DuMars]
      • Working on mechanisms to get feedback from the user community (playing with something like http://kubernetes.report -- in development, not ready for distro yet)
      • Presenting at KubeCon 16:35 on Thursday ~ Ihor and Aparna
      • Working on a charter draft
        • We actually represent three 'P' areas: product, project, and program
        • Help SIG focus on implementations
        • We're trying to look a
  • Announcements:
    • **Kubecon next week, no community meeting! **\o/
    • **Last Chance to Register for the Contributor Summit - **
    • Shoutouts!
      • See someone doing something great in the community? Mention them in #shoutouts on slack and we'll mention them during the community meeting:
      • Timothy St. Clair would like to thank Peter Zhao (@xiangpengzhao) for "steadfast PR-review and contributions to SIG Cluster Lifecycle"
      • Chuck Ha would like to thank Leigh Capilo (@stealthybox) for "being welcoming to new folks in SIG Cluster Lifecycle. You are welcoming and helpful and it keeps our community healthy. Thank You!"
    • Normalization of Kind Labels [Josh Berkus]
      • Updating list of kind labels, how they are used
    • Cloud Foundry wants to welcome folks to their Summit on May 1st (day before KubeCon/CloudNativeCon)
    • You can now use Kubernetes to water your lawn.
    • No Meeting next week!
    • Help Wanted?
      • Add to this section when you have something you need help with! Issue, contributors, etc.

April 19, 2018 - (recording)

  • Moderators: Paris Pittman [SIG ContribEx]
  • Note Taker: Jaice Singer DuMars (Google)
  • [0:01] **Demo **- Skaffold Matt Rickard - Google (mrick@google.com)
    • https://github.com/GoogleContainerTools/skaffold
    • Tool for developing applications on Kubernetes
    • Allows you to step into CI/CD
    • skaffold-dev / skaffold-run are the two primary components
    • [ 0:03 ] - Demo
    • Q: What is the plan around integration for new Kubernetes releases?
      • Pinned to 1.10, have integration testing but not version skew
      • Want to follow the Kubernetes support process of ~2 releases
    • Q: Why would this not be in CNCF/part of k8s?
      • Trying to keep it unopinionated
      • If a community project makes sense, we will examine that
      • MFarina: Ecosystem projects are the preference to avoid contention
    • Q: So what are the non docker image formats this tool supports?
      • Only supports bazel
      • Working on java support
      • This is the other build tool we're working on integrating next for skaffold. https://github.com/google/jib
      • Minimal arbitrary support, but requires a file to query and parse to determine SC dependencies, currently in-tree but might move to a plugin model
  • [0:14]** Release Updates**
  • [0:00]** Graph o' the Week**
    • YouTube Channel Stats!
      • ~7000 subscribers and growing
      • Old videos and high engagement videos get the most attention
      • SIG recordings are typically used as a sleep aid
      • 4:45 average view time on videos
      • If you are posting videos, use descriptive titles, tags
      • Desktops primary viewing device, also TVs
      • You can turn the video speed up to 1.5 if you want to get through the material faster
  • [0:23] SIG Updates
    • **CLI **(Maciej Szulik - confirmed)
      • Printing of objects being moved to server - currently in beta, in 1.10 users were able to opt in to it
        • You can opt out via flag, but it is on by default in 1.11
        • No user-facing impact, but if there are, contact sig-cli
      • Different patterns across the repo, and trying to unify by providing identical flags and output
        • unified flag handling will unify the code base, ux, and simplify the code base
    • **AWS **(Justin SB - Confirmed)
      • Our first sig repository: aws-encryption-provider ~ encryption at rest in etcd
      • Justin SB is now a Googler
      • CP breakout is blocked by non-technical issues
        • From Micah Hausler (EKS) to Everyone: (10:29 AM): Small correction: We are actively working on the CP breakout here at AWS (we've had a ad-hoc community-based meeting to get it going) - meeting notes
      • Need help working on this
    • **GCP **(Adam Worrell - confirmed) (bit.ly/k8s-sig-gcp)
      • Not thriving, 3 meetings total but having a lack of topics
      • There's only one lead, but someone has expressed interest
      • Organizationally important, but there don't seem to be externally-interested parties
      • There are lurkers, but not a specific community
      • Community, please use this opportunity
  • [0:00] Announcements
    • Shoutouts!
      • Join #shoutouts to add yours to the weekly announcements
      • @maciekpytel for providing some nuance and clarity around node autoscaler
      • @cblecker for fielding so many issues and PRs.
    • Help Wanted?
      • SIG UI is looking for more active contributors to revitalize the dashboard. Please join their communication channels and attend the next meeting to announce your interest.
    • KubeCon EU Update
      • Current contributor track session voting will be emailed to attendees today!C
      • RSVP for Contributor Summit [here]
      • SIG Leads, please do your updates for the 5 minute updates
    • CNCF meet the maintainers group is organizing ~ please sign up for attending the CNCF booth

April 12, 2018- (recording)

  • Moderators: Josh Berkus [SIG-Release]
  • Note Taker: Clint Kitson [VMware]
  • 69+ participants
  • [ 10:00 ]** Demo **-- CRI-O [Antonio Murdaca, runcom@redhat.com] (confirmed)
    • https://github.com/kubernetes-incubator/cri-o
    • Support for k8s 1.9/1.10 and tracking changes consistently
    • Planned support for clearcontainers/kata-containers
    • Demo on K8s 1.10
    • Support for kubeadm and minikube
    • Create issues on crio project on github
    • sig-node does not have plans to choose one yet
      • Working on conformance to address implementations which should lead to choosing default implementation
      • Choice is important since it would be used under scalability testing
      • Test data? Plan to publish results to testgrid, will supply results ASAP
        • Previously blocked on dashboard issue
        • Can get to point to make crio a blocking job-- multiple releases at this status before graduation
    • Request for containerd update to group -> contribex
  • [ 10:18 ]** Release Updates**
    • 1.11 [Josh Berkus ~ Release Lead] (confirmed)
      • Week 2 of 12 (see schedule)
        • Currently collecting features [Ihor]
        • Discussion about changing the Freeze/RC schedule
      • Been difficult to get all tests passing, so code freezes have been lengthening
        • Less time to work on development
        • In 1.11 trying to shorten code freeze conditionally
          • If last 3 week days if all test passing then will make code freeze shorter to enable more development time
            • All 3 dashboards (1.11-blocking, master-blocking, master-upgrade in testgrid)
              • 1.11 dashboards don't exist until 7 days prior
          • Sending out update to k8s-dev 4/13
          • Could get freeze to 7 working days (goal)
          • Up to release lead if this works out
          • Questions to sig-release mailing list/slack
    • Patch Release Updates
      • 1.10.1 Maciek Pytel
        • Issues with flakey tests, triaged, reviewing and hopefully green by 4/13
      • 1.9.
        • No info
  • [ 10:24 ] **Graph o' the Week **Aaron Crickenberger
  • [ 10:32 ] SIG Updates
    • SIG-VMware Steve Wong
      • 1st meeting, charter defined, meeting notes are published and shared
      • 31 google group members, 11 people on first meeting, 50 slack members
      • Support kubernetes users who are deploying at scale on VMware platforms, support development relating to cloud providers
        • Working on aligning cloud provider to cloud provider WG strategy
    • SIG-Windows Michael Michael
      • Busy since 1.9 on getting people using and deploying windows containers
      • Been fixing bugs
      • Added support
        • Resource controls
        • File system stats
        • Flexv
        • Hyper-v isolation (experimental), similar to kata
        • e2e automation and tests for sig-windows (eta 1 month)
        • Hoping for GA around Windows Server 2019
        • Join on slack or directly
    • On-Prem announcement (jb)
      • Demoted to working group
        • Forum for discussion for people with on-prem deployments
        • Possibly formally recognized group in future (waiting decision from steering committee)
          • Committee is clarifying what a WG is, why, rules
          • Also clarifying a sub-project
        • Doesn't have formal meetings/structure yet
  • [ 10:40 ] Announcements
    • Shoutouts this week:
      • @robinpercy@mike.splain @rdrgmnzs for graduating the mentoring program. @paris for leading it.
      • @maciekpytel for "providing clarity" around the node autoscaler
    • We're going to disable the cherrypick-auto-approve munger [aaron]
    • SC update: subprojects and SIG charters [briangrant]
      • Help SIGs create charters
      • Explain to SIGs what sub-projects are and how they can be used
      • Split SIGs among steering committee members
      • 6 charters in flight working on charter, then going to other SIGs
    • r/kubernetes: Ask Me Anything - thanks everyone for participating, lots of user feedback, please have a look.
      • We'll likely do more of these in the future.
    • Kubernetes Contributor Summit @ Kubecon - May 1 (jb)
      • You need to register for this even if you already registered for Kubecon! Link to the form in the link above.
      • New contributor/on-going contrib in morning and general tracks in afternoon
    • New CNCF Interactive Landscape: https://landscape.cncf.io/ (dan kohn)

April 5, 2018 - (recording)

  • Moderators: Jose Palafox [ContribEx]
  • Note Taker: Solly Ross
  • **Demo **
  • Release Team
    • 1.11 [Josh Berkus, Release Lead]
      • We are in Week 1
      • Release team roles almost filled
        • Still need a docs shadow (ask in #sig-release or #sig-docs if interested)
      • Schedule posted (last chance to raise issues is right now)
        • Feature Freeze: April 24
        • Code slush: May 22
        • Code Freeze: May 28
        • Doc Deadline: June 11
        • Release: June 26 (yes, we know it's right before July 4th, there's not a good way around it)
      • Feature Gathering has started
    • 1.10 [Maciek Pytel, patch manager]
      • 1.10.1 on April 12th (next Thursday)
        • Contains kubectl fixes
        • Will send email with release notes and pending PRs later today
        • Contact Maciek if you need to cherry-pick anything not in the email
    • 1.9
  • **Graph o' the Week **(Josh Berkus)
    • PR Workload: shows weighted workload for each SIG in the form of PRs. Primarily there to check up on which SIGs are heavily loaded.
      • Includes ONLY PRs against kubernetes/kubernetes because other repos don't use SIG labels consistently.
      • "Absolute Workload" == PR count * PR Size
      • "Relative Workload" == (PR Count * PR Size) / Number of Reviewers
      • Calculation in issue (docs later)
      • PRs that were open during that period, not PRs that were created during the period. Old PRs are important for workload.
    • Chart:
    • Table:
    • Questions
      • Assumes proper labeling
        • Yes, things without sig labels aren't included
        • Size labels have a lot of fudge factor
        • Don't compare small increments ("10% more PRs than last week") but compare heavily loaded/lightly loaded ("is SIG-API overwhelmed for 1.11?")
      • Overall graph takeaway?
        • Determine if one SIG has a bunch of PRs suddenly, or does everyone have a bunch of PRs due to a particular place in the release cycle
      • What do we do based on these charts?
        • We're still exploring, seeing what people think, are these helpful to people?
        • Join #devstats if you're interested in collaborating, discussing
        • Need to find charts that are actually useful vs just shiny
  • SIG Updates
    • SIG Cluster Ops - Rob H.
      • Updated Mission - more focused on building operator community
      • We have been having trouble with quorum and need some help
      • Chris McEniry and I believe strongly in the need for an vendor neutral place for operators to gather around K8s. Neither of us are vendors, so we're good neutral hosts, but we need help getting speakers.
      • We'd be happy to host long format demos by vendors.
      • Questions:
        • Consolidate with OnPrem?
          • Sure!
          • It's good to consolidate SIGs if it's relevant
    • SIG Docs - Zach
      • 2 new maintainers, 5 new contributors
      • Coming soon: improved contribution guidelines: https://kubernetes.io/editdocs/
      • Migrating the Kubernetes website from Jekyll to Hugo: we've met with the contractor, gotten an initial estimate, and are proceeding with a target completion date of April 30
      • Blog migration: Formerly at blog.kubernetes.io (Blogger), the Kubernetes blog now resides at kubernetes.io/blog (GitHub). The main reason for migrating was to resolve increasing technical debt and make life easier on the blog contribution team.
        • Thanks to test-infra for the automation that make it possible to have blog-level ownership of PRs and approvals!
      • Questions:
        • Tidying up contributor guidelines just for SIG docs, or Kubernetes in general?
          • Kubernetes in general
          • Collaborate with ContribEx
        • Have blog posts pending review been migrated to GitHub, or do they need to be manually migrated?
          • They will be migrated, with blog manager opening PRs as needed
    • SIG Service Catalog - bumped to 5/24
  • Announcements
  • Shoutouts

March 29, 2018

  • Moderators: Paris Pittman [ContribEx]
  • Note Taker: Solly Ross
  • [ 0:00 ]** Demo - **KubeAdmin Self-Config - Rob Hirschfeld (rob@rackn.com)
  • [ 0:00 ] Announcements
    • Meet Our Contributors is Apr 4th @ 330p and 9p UTC
      • Like office hours, but contributor question focused
      • Looking for contributors to answer questions, 2 slots
      • Reach out to @paris on Slack if you're interested in participating
    • Contributor Summit in Copenhagen May 1 - registration is live
    • KubeCon Copenhagen (May 2-4) is on track to sell out. Register
    • Shoutouts this week (from #shoutouts in slack):
      • @nabrahams who picked the 1.10 release notes as his first contribution. We literally could not have done this without him!
  • [ 0:15 ]** Kubernetes 1.10 Release Retrospective**

March 22, 2018 - recording

  • Moderators: Chris Short [Contribex]
  • Note Taker: Sanket Patel [Egen Solutions]
  • [ 0:00 ]** Demo **-- 03/22: Ark - a backup/disaster recovery tool for k8s - Andy Goldstein (andy@heptio.com)
    • https://github.com/heptio/ark
    • "Heptio Ark is a utility for managing disaster recovery, specifically for your Kubernetes cluster resources and persistent volumes."
    • Looking for help on code and documentation
    • Link to slides
  • [ 0:00 ]** Release Updates**
    • 1.10 [Jaice Singer DuMars ~ Release lead]
      • Code thaw happened
      • rc1 is out, please take a look!
      • release due Monday 3/26 ~ 6PM Pacific time
      • release retrospective the last 45 minutes of the community meeting next week
      • You can see our progress in videos and in the burndown meeting notes
      • We're looking for a Release Lead for 1.11, code name "Everything Croissant" - read the role description and requirements here, and contact @jdumars in Slack if you are interested in knowing more
        • Josh Berkus has volunteered, but the more the merrier!
      • Release retrospective in this time slot, in 2 weeks: 3/29
    • Patch releases out now
      • 1.7.15
      • 1.8.10
      • 1.9.6
  • [ 0:00 ] **Graph o' the Week **[N/A]
    • Back Next Week After 1.10 Release
  • [ 0:00 ] SIG Updates
    • SIG Azure [Cole Mickens] (confirmed)
      • #sig-azure on Slack
      • Azure backlog is public
      • cloudprovider is moving to independent repo
      • Lots of work around Azure integrations
      • Kal Henidak is leading Azure's upstream release efforts
      • Many fixes in the 1.10 release
      • More great things in the pipeline
    • SIG Node [Derek Carr] (confirmed)
    • SIG Network [Casey Davenport] (confirmed)
      • Feature alpha -> beta
      • IPvs kube-proxy staying in beta - outstanding issues
      • Ingress requirements gathering.
      • Network plumbing group discussing adding networking interfaces for pods - specification doc
      • Traffic shaping moved to a CNI plugin - proposal
      • Designing service routing to be topology aware - proposal
  • [ 0:00 ] Announcements
    • Shoutouts this week:
      • Vlad Ionescu: Shoutout to @yomateo and @foxie for how much they are helping in #kubernetes-users! Matthew has a lot of examples on his Github and Ashley is amazing regarding on-prem and general k8s questions( learned so much by reading their answers).
      • Jaice DuMars: I know I keep saying it, but @cblecker @dims @liggitt ~ The POWER TRIO of release-assist awesomeness!! THANK YOU!!
      • Josh Berkus: Shout out to Pavel Pospisil, for pitching in to close a PVC blocker bug despite being between jobs this week and not having his normal dev machine.
      • Josh Berkus: Shoutout to Klaus Ma for leading the closure of several storage bugs, including staying up until 1am his time to attend meetings
      • Jordan Liggitt: Shoutout to the branch managers: @wojtekt, @jpbetz, @mbohlool for dealing with unending cherry-picks over the last couple weeks
    • Meet Our Contributors is looking for contributors to come on Apr 4th at 330 and 9p UTC
      • Join the slack channel (same name)

March 15, 2018- (recording)

  • Moderators: Solly Ross [SIG]
  • Note Taker: Kris Nova
  • [ 0:00 ] Demo -- Kuberhealthy presentation (sandbox project applicant) - Eric Greer (eric.greer@comcast.com)
    • https://docs.google.com/presentation/d/1tL80i7VTBUlDs5KXy7TBZcHVX45lFST2cmmE3oyjYWc/edit?usp=sharing
    • Repository TBD (may be open sourced via corporation or go direct to sandbox if applicable)
    • Tool for checking cluster health by standing up pods on each node, checking status of components in kube-system, etc
      • Designed to check cluster health beyond normal logs, monitoring, metrics -- make sure you can actually run applications
    • Currently deployed internally in production, but should generally be considered alpha at the moment
  • [ 0:00 ] Release Updates
    • 1.10 Update [Jaice Singer DuMars ~ Release lead]
      • Release team is in a meeting right meow
      • Due to the security releases, and some scalability testing issues we decided to push the release from 3/21 to 3/26, and lift code freeze by EOD Monday assuming all goes to plan
      • You can see our progress in videos and in the burndown meeting notes
      • We're looking for a Release Lead for 1.11, code name "Everything Croissant" - read the role description and requirements here, and contact @jdumars in Slack if you are interested in knowing more
      • Release retrospective in this time slot, in 2 weeks: 3/29
    • Current Release cycle (e.g. 1.7) [First Last ~ Release role]
    • Prior Release cycle (e.g. 1.6.6) [First Last ~ Release role]
  • [ 0:00 ] Graph o' the Week
    • No graph this week, tune in next time!
  • [ 0:00 ] SIG Updates
    • SIG Auth [Eric Chiang]
      • Notes: [link]
      • Overview
        • Betas: PodSecurityPolicy, Auditing
        • Alphas: TokenRequest API, client-go external credential providers, encryption-at-rest external KMS integration
        • Considering Bug Bounty for Kubernetes
    • SIG Instrumentation [Piotr Szczesniak]
      • Introduced external metrics API
        • Metrics will come from other systems other than k8s
        • Integrates with Prometheus and other monitoring systems with adapter
      • Graduated metrics API to beta
        • Inspired by heapster
        • By default applied to all kubernetes clusters
      • Started discussion around securing instrumentation endpoint
        • Cross SIG effort between sig-auth and sig-instrumentation
      • Master metrics API, Custom metrics API
        • Plans to graduate these to GA
        • Deprecate Heapster
      • Plans in the works for a historical metrics API
      • Agreement to have logging on architecture and vision
        • Similar to metrics architecture, which was a foundation for many design decisions
      • Discussion on exposing kubelet health status
        • Useful for monitoring the state of Kubelet
        • Different than the metrics endpoint
        • Still figuring out how to do this
      • Would like to move sig-instrumentation projects to a new home
  • [ 0:00 ] Announcements
    • Registration for the Contributor Summit is now live:
      • See this page for details
      • Please register if you're planning on attending, we need this so we have the correct amount of food!
      • Just registering for Kubecon is not enough!
    • Office Hours Next Week!
      • Volunteer developers needed to answer questions
    • Helm Summit Videos are up.
    • Shoutouts this week
      • Someone doing great work out there that you'd like to highlight? Let us know in #shoutout on slack and we'll mention them here:
      • @shyamjvs - diagnosing 2 critical performance problems which could have blocked the 1.10 release
      • @verullt - taking on most of the open storage issues and resolving them as quickly as possible
      • Quang Huynh for all the shiny new looks he's given prow.k8s.io during his internship!
      • Jaice wants to say "Release mvps: @dims @cblecker"
      • Thanks to the ever-helpful Andrew Chen (@chenopis) for getting me through merge conflicts and branch merges in preparation for the 1.10 release. (From Jennifer Rondeau)
      • Stefan Schimanski would like to thank:
        • Nick Chase (@nickchase) - for editing down 92 pages of release notes into something consumable by humans!
        • Mik Vyatskov (@crassirostris) - for doing an awesome job driving and owning the auditing feature
      • Josh Berkus would like to thank Jordan Liggitt (@liggitt)
      • And finally congratulations to Brad Topol (@bradtopol) for joining the maintainer team on docs.

March 8, 2018 - (recording)

March 1, 2018 - (recording)

  • Moderators: Solly Ross [SIG]
  • Note Taker: Chris Short - chris@chrisshort.net
  • [ 0:00 ]** Demo **-- Sonobuoy - diagnostic tool for k8s - Chuck Ha (chuck@heptio.com)
  • [ 0:00 ]** Release Updates**
    • 1.10 Release Update [Jaice Singer DuMars ~ Release lead]
      • Week 9 of 12, full schedule and some important information is here
      • We're in code freeze
        • Why do we have code freeze?
          • Provides opportunity for SIGs to focus on bugs/cleanup
          • Allows time for technical debt elimination while we have a quiet submit queue, e.g. this
        • How does it work?
          • Isolate release-relevant items (issues and PRs) by use of the **status/approved-for-milestone label
          • If it's in the milestone with that label, we pay close attention, otherwise it is assumed not impacting the release
          • Bot will nag you about labels so we can focus on what's really important
        • Check out that beta, please
      • Collecting known issues in a single place so we can properly document it as part of the release notes
      • Release notes and user-facing documentation should be close to complete ~ PRs for docs need to be ready for review by tomorrow (6 PM PT unless otherwise stated)
    • 1.8.9 should be out today
    • 1.7.13 is out
  • [ 0:00 ] Graph o' the Week [Josh Berkus]
  • [ 0:00 ] SIG Updates
    • SIG Big Data [Anirudh Ramanathan]
      • Acting as a bridge to external projects, sometimes work on forks, and then upstream it.
      • Apache Spark - (now tracked in JIRA & mailing lists)
        • Graduated from a fork and merged back into project - released as Spark 2.3 yesterday!
        • Top billed feature - k8s support (link)
        • 3 new ASF committers from our SIG
        • Spark-submit with operator semantics (WIP)
      • Apache Airflow (link)
        • Trying to make a k8s-native DAG scheduler
        • Currently upstreaming the k8s executor.
        • Airflow v1.10 will be first release with k8s constructs in it.
      • HDFS (link)
        • Hardening existing work
        • Added HA namenode and fault tolerance to running within k8s/containers
        • Demo coming soon in SIG Apps
        • Success = performant and secure HDFS.
      • Kube-arbitrator (link)
        • Joint work with sig-scheduling.
        • Ongoing discussion, MVP coming soon.
    • SIG Storage [Saad Ali] - Slides
      • Primary work for 1.10 is moving alpha features to beta including: CSI, Local storage, mount propagation, volume protection, ephemeral storage, etc.
      • In 1.11 will be working on topology-aware storage and moving beta features to GA
    • SIG Multicluster [Christian Bell]
      • FederationV1: Low interest in fixing open bugs; bots are auto closing issues
        • Top-level docs need to update/reflect reality that at the current pace of development, FederationV1 will not reach the maturity as single-cluster Kubernetes.
      • Most work on federation has moved to a WG FederationV2
        • Currently in "brainstorming" phase
        • Moving away from having a completely consistent api with non-federated Kubernetes API
      • Cluster Registry: An API for maintaining a list of clusters and associated metadata. Move to beta this quarter. Being consumed by Kubernetes (Kubemci) and non-Kubernetes projects (istio multi-cluster).
      • Kubemci: A command-line tool (and eventually controller) to configure ingress across multiple clusters.
  • [ 0:00 ] Announcements

February 22, 2018 - (recording)

  • Moderators: Jorge Castro [SIG ContribEx]
  • Note Taker: Jaice Singer DuMars
  • [ 0:00 ]** Demo **No demo this week
  • [ 0:01 ]** Release Updates**
    • 1.10 [Jaice Singer DuMars ~ Release lead]
      • Week 8 of 12, full schedule and some important information is here
      • We're in code slush (Josh Berkus)
        • Trying to filter out issues that are not critical to 1.10 release health
        • SIGs must take ownership of issues with "Approved-For-Milestone" labels + Priority + type + status
      • CODE FREEZE ON MONDAY ~ 6PM PST
        • No new commits to the release-1.10 branch unless:
          • SIG approved and tied to an existing issue
          • Bug fixes (critical)
          • Test flake fixes (or other release-specific code)
        • If you have an exception, please contact @jdumars / jdumars@gmail.com
      • Release appears on track for 3/21 delivery, but don't count on it
      • https://github.com/kubernetes/sig-release/issues/86
      • If a release team member asks for something (e.g. docs), please make your best effort to help them.
  • [ 0:07 ] **Graph o' the Week **[Josh Berkus]
    • Weekly update on data from devstats.k8s.io
    • New and occasional contributors: Issues and PRs
      • Shows volume of contributions/contributors from community members who are NOT full-time
      • Important measure of how "welcoming" a community is.
      • Also important because we've added a lot of process and need to be sure that's not a major blocker for new contributors.
  • [ 0:00 ] SIG Updates
    • SIG Cluster Lifecycle [First Last]
      • Not happening
  • [ 0:00 ] Announcements
    • Reminder: Contributor Summit happens 1 May, day before Kubecon
    • Shoutouts this week
      • Zhonghu Xu - @hzxuzhonghu for many high quality apiserver APIs PRs
      • Mario & Ilya Dmitrichenko for helping out with user office hours this week!
        • Volunteers still needed!
      • Someone doing great work? Give them a shoutout in #shoutouts and we'll mention them during the community meeting.
      • Meet Our Contributors!!
        • March 7th at two times
        • #meet-our-contributors in slack for questions and more details
        • We'd like to do live peer code reviews, too!
    • Need SIG volunteers to say what is new in 1.10 in a webinar. Minimal time investment. -- contact nchase@mirantis.com or @nickchase

February 15, 2018 - (recording)

February 8, 2018 - (recording)

  • Moderators: Paris Pittman [SIG ContribEx]
  • Note Taker: Josh Berkus [Red Hat/SIG-Release]
  • [ 0:00 ]** Demo **-- stork, storage orchestration runtime for Kubernetes - Dinesh Israni (disrani@portworx.com)
    • Administrative support for Hyperconverged Storage (that is, Kube storage running in pods).
    • Has health monitor for storage nodes with automated failover.
    • Supports the (currently alpha) snapshot provisioner.
    • Live demo involving Stork storage with MySQL on top.
    • Currently only supports Portworx storage, but want contributions from other storage drivers.
    • Slide
  • [ 0:14 ]** Release Updates**
    • **1.10 **[Jaice Singer DuMars ~ Release lead]
      • Follow along in the official schedule, we're in week 6 of 12
        • Please follow the schedule, we will enforce it
      • Feature Freeze has passed, but we are accepting exceptions on a case-by-case basis using the process found here
      • If you're curious about what is on deck for 1.10 planned work, pay a visit to the Features Tracking Spreadsheet
      • Next week, we will be cutting our first beta release, as well as assembling the release branch
      • Release team meetings are in the weekly cadence on Mondays at 10am Pacific until February 26th. If you join either the SIG-Release or kubernetes-milestone-burndown groups, you should get an invite
        • Meetings may or may not include puppies
      • please remember that code freeze begins on** February 26th**
        • Trying to make sure that nobody is surprised by the schedule!
  • [ 0:18 ] Graph o' the Week [Tim Pepper; 1.10 release issue triage shadow]
    • Release cadence and feature activity: what is an "issue" or "bug" or "feature" in kubernetes and Github? We all know GitHub has an "issue" object and there are lots of k8s labels in them, but for feature it's complicated:
    • Does the "complicated" show up in the stats? Are features efficiently created earlier in the cycle and closed as the cycle progresses?
  • [ 0:23 ] SIG Updates
    • SIG Architecture - [ Brian Grant, co-lead ]
      • Working on identifying subproject owners
        • Related to SC decision
        • Need to map existing code subprojects to SIGs
        • A lot of the work done by Aaron Crickenberger
        • Have done a few directories, such as for Workloads APIs
        • Check SIGs.yaml for what's been identified, make sure that it's correct.
      • Reviewing architectural issues as they arise
      • Still working on implementing the KEP
        • A formalization of the design proposal process
    • SIG Scalability - [Bob Wise]
    • SIG Scheduling - [Bobby Salamat]
      • A major work item for 1.10 is to move priority and preemption to Beta
        • New feature in 1.9 alpha.
        • Very useful for multiple very different workloads
        • Example: allow production workload to push dev workload aside
      • Performance improvements
        • Enable equivalence cache and move it to Beta
        • Optimize Affinity/Anti-affinity
          • These are much slower than other predicates (like 10X)
      • Design a new extension model for scheduler and build a scheduling framework
        • Currently, the extension model communication is too slow for some plugins.
      • Three incubators
        • Kube-arbitrator
          • "Gang scheduling" so that all pods of a group get scheduled, or not.
          • Supporting quota for hierarchical namespaces
        • Cluster capacity tool
          • Checks if a pod can be scheduled in a certain cluster based on resources
        • Descheduler
          • Automated removal of pods to free up resources
  • [ 0:41 ] Announcements
    • Steering Committee Update [Brendan Burns]
      • New Repository structure proposal
        • Sunsetting kubernetes-incubator, won't accept any new projects
        • 3 classes of repositories: (a) associated repos, (b) sig-owned repositories, (c) kubernetes repositories (approved by sig-arch)
        • This is about new repos going forward, not a mandate for existing repos anytime soon.
          • Except for a few things like Owners files
          • SIGs who want to move from incubator to sigs repos, stay tuned for details
        • Question [Matt Farina]: associated repos: who would want one of these? Why do this?
          • Brendan: as a prerequisite for submitting a feature to Kubernetes. CLA is gateway here. Also, even for external things a consistent process is good and makes it easier for contributors.
          • Example: Kube-sanity project. Doesn't belong to a SIG, but all Kube contributors.
    • Intel Intro [Jose Palafox]
      • Jose is the program manager for Intel's Kubernetes efforts.
      • They have a team of 16 engineers on Kube.
      • Reach out to Jose if you want to collaborate with them.
    • #shoutouts [Jorge Castro]
      • Duffie Cooley, Stefan Schimanski, Craig Tracey, Timothy St. Clair, Chuck Ha, Liz Frost, Nikhita Raghunath, Aaron Crickenberger, Ilya Dmitrichenko, Ihor Dvoretski, Ellen Korbes and Tim Pepper
    • SIG Schedule for this call for the next few months: SIG Update Schedule (always posted at the top of this document)
      • Schedule is fixed, please check it.
    • Meet Our Contributors - first weds of the month

February 1, 2018 - recording

  • Moderators: Solly Ross [SIG Autoscaling]
  • Note Taker: First Last [Company/SIG]
  • [ 0:00 ]** Demo **-- generator-kubegen, a Kubernetes config generation tool - Sergio Sisternes (ssistern@everis.com)
    • Link to slides
    • Link to repositories
    • Yeoman-based wizard for generating Kubernetes YAML
      • Asks basic questions, generated Kubernetes object definitions
      • Can create everything for a basic app, or just individual objects
    • Questions:
      • (not a question) Anybody interested in common patterns for should join the App Def WG
  • [ 0:00 ]** Release Updates**
    • 1.10 [Jaice Singer DuMars ~ Release lead/Ihor Dvoretskyi ~ Features lead]
      • Follow along in the official schedule, we're in week 5 of 12
      • Features freeze has passed, and looking good!
      • Alphas have been cut successfully
      • Marketing activities (e.g. blog preparation) are beginning
      • Questions:
        • (not a question) Lots of issues without labels, please go in and make sure 1.10 issues have labels
        • How do we go in and try out the latest alphas, e.g. cluster provisioning tool?
          • Kubeadm supports alphas, as long as they've been pushed to GCS buckets
  • [ 0:00 ] **Graph o' the Week **[Aaron Crickenberger]
    • Weekly update on data from devstats.k8s.io
    • Actually a table! What a twist!
    • https://k8s.devstats.cncf.io/dashboard/db/developers-summary?orgId=1
      • Collects GitHub events (e.g. comments, commits, etc), and associates them with GitHub users
      • Can break down by releases, time
      • Not yet broken down by repositories
    • Questions:
      • Does it include incubator
        • Yes, includes all kubernetes-associated repos (kubernetes, kubernetes-incubator, helm, kube-clients)
  • [ 0:00 ] SIG Updates
    • SIG Cluster Ops [Rob Hirschfeld] - http://bit.ly/k8sclops
      • New time! 1 hour earlier (12 am Pacific)
        • Next meeting one hour from now (every two weeks)
      • Change in format to be more "meetup" style
      • Looking to bring in more demos & discussions
      • Specifically want to hear from operators
      • Fine w/ longer format vendor demos to get feedback
      • Want to hear more about different deployment patterns
    • SIG Autoscaling [Solly Ross]
  • [ 0:00 ] Announcements
    • Steering Committee update
      • Formalizing subprojects
        • Part of proposal from sig architecture
        • Want to make sure everything is owned by some group (SIG or subset thereof), sometimes things are owned by a group within a SIG
        • Issue
        • Initial implementation PR
          • SIG leads should look at PR and sanity check it
        • This is a non-binding first pass, goal was to make sure every repo had an owning sig, would like help iterating on what subprojects exist and who should own them
        • Seemed easier to do in one place vs. distributed across all repos
        • Next steps involve building automation to consume/enforce, making individual repos source of truth via additions to OWNERS files
        • Examples:
          • sig-apps owns the "charts" subproject, which corresponds to the "charts" repo
          • Sig-apps also owns "Workloads API" subproject, corresponding to the API types, clients, etc for the workloads types
          • Could have a project containing all kubernetes client repos, for instance
        • Questions
          • If there's a new subproject that needs a repo, who decides what gets a repo in kubernetes
            • Answer: see below :-)
      • Upcoming
        • Repositories proposal (aka "the incubator problem")
          • Moving towards 3 classes of projects (how formal things are)
            • Core kubernetes repos (everything in kubernetes/kubernetes + staging, more-or-less), fairly formal, has process, lots of testing, etc
            • SIG repos (encourage SIGs to create repos as they see fit, maybe create subproject repos, either stuff outside of core, or stuff that is a prototype before going into core)
            • Associated repos (needs CLA bot turned on, code-of-conduct but that's about it)
          • Doc forthcoming
        • Expectations of SIG charters and template charters
          • A checklist/template will come out eventually
          • Feel free to discuss and submit before then
        • CNCF graduation
          • Looking to graduate Kubernetes through the CNCF, making it the first project to do so
    • Amazon participation update [Bob Wise]
      • Increasing/ramping up direct involvement
      • Expect to see more contributions around testing in the short run, AWS experience
      • Participate in SIG AWS (both EKS and non-EKS)
      • Can be found on Slack as well, feel free to reach out with feedback, ideas, etc
    • SIG Testing Commons subproject announced [Tim St. Clair]
      • Focus on
        • tests are written
        • contributing tests
        • cleaning up tests
        • what things are tested
        • e2e framework
        • Conformance
      • Please come participate
    • Kubernetes Documentation User Journeys MVP launched [Andrew Chen]
      • Please give SIG Docs for feedback, still adding things later
        • Can contribute normally (join SIG docs for more information)
      • New landing page incorporating personas (users, contributors, operators)
      • Levels of knowledge (foundational, advanced, etc)
      • Can also just browse docs directly
    • SIG Arch Announcement [Joe Beda]
    • Contributor Summit for Kubecon EU [Jorge and Paris]
    • #shoutouts - [Jorge Castro]
      • New channel in Slack
      • Someone do something great for the community? Give them a shoutout here and we'll take the time to thank them for their work at the end of each community meeting.

January 25, 2018 - (recording)

  • Moderators: Mario Loria [Meetup Organizer / Liquidweb] (confirmed)
  • Note Taker(s): Jorge Castro [SIG Contributor Experience]
  • [ 0:00 ]** Demo **-- kube-toolkit - toolkit for creating gRPC-based CLI and web tools for Kubernetes - Radu Matei ( radu@radu-matei.com ) (confirmed)
  • [ 0:00] INDEX Conference [Jeff Borek]
    • https://developer.ibm.com/indexconf/
      • Offering space at the Moscone on 20 Feb for communities to hold face to face meetings. Attendance on the 20th is COMPLETELY FREE, but you must register, you'll get 50% off the rest of the conference if you want to stay!
      • Please contact jborek@us.ibm.com if you're interested in claiming some space for your SIG.
      • "Meet the SIGs" community day will be on the 20th, with Sarah Novotny delivering the keynote.
      • SIGs interested in participating:
        • SIG Contributor Experience
        • SIG Docs
        • … add yours
  • [ 0:00 ]** Release Updates**
    • 1.10 [Jaice Singer DuMars ~ Release leader]
      • Follow along in the official schedule, we're in week 4 of 12
      • Feature freeze pushed to 1/29 [Ihor Dvoretskyi, Features Lead]
      • Shooting for Alpha next week on Tuesday
    • 1.9.2 is out (thank you Mehdy!)
    • 1.8.8 - no ETA
  • [ 0:00 ] **Graph o' the Week **[Aaron Crickenberger]
  • [ 0:00 ] SIG Updates
    • SIG Service Catalog [Paul Morie] (confirmed) *
    • SIG CLI [Sean Sullivan] (confirmed)
      • Moving apply and merge to the server side
      • Breaking up the monolithic kubectl.
  • [ 0:00 ] Announcements
    • SIG leads: register to offer intros and deep dives in SIG track at KubeCon Copenhagen (May 2-4): overview, signup (1/31 deadline)
    • SIG Contributor Experience news: new lead, new meeting
    • Meet Our Contributors - Feb 7th [Paris]
      • 730a PST/ 3:30 pm UTC & 1pm PST / 9pm UTC
      • Need contributor volunteers for 1pmPST/9pmUTC session -> Sign Up [WIP] on m-o-c tab
      • 30 mins AMA; 30 mins live peer code review
      • Part of larger mentoring initiatives -> GH repo ; Issue
    • New SIG-Release lead, Jaice Singer DuMars replacing Phil Wittrock
    • A new SIG Scheduling lead has been scheduled via Bobby Salamat

January 18, 2018 - (recording)

  • Moderators: Tim Pepper [VMware/SIG Contrib-Ex]
  • Note Taker: Jaice Singer DuMars [Microsoft/SIG-breakfast]
  • Chat Transcript
  • [ 0:00 ]** Demo **-- Kubernetes on Docker for Mac - Jenny Burcio (jenny@docker.com), Arun Gupta (arun.gupta@gmail.com) (confirmed)
    • Link to slides
    • Link to repositories
    • Not slated for Linux atm, but Windows might be sooner than later
    • Uses a CRD where Docker command talks to CRD, creates a new service objects to translate compose files
  • [ 0:00 ]** Release Updates**
    • 1.10 [Jaice Singer DuMars ~ Release lead]
      • Follow along with the schedule
      • Alpha delayed - requires individual access on Google side so waiting for Caleb's onboarding, also bicycling can be dangerous
      • Features update
      • Feature freeze is coming, 1/22 [Ihor]
    • 1.9.2 Should be today (thanks Mehdy!)
    • 1.8.7 is out (thanks David!)
  • [ 0:00 ] **Graph o' the Week **[Jorge Castro]
  • [ 0:20 ] SIG Updates
    • SIG Docs [Devin Donnelly, Andrew Chen]
      • K8s Docs Structure
      • Link to slides (see video for narrative)
    • SIG Network [Dan Williams]
      • 1.10 features and work
        • IPv6 single and dual-stack
        • IPVS proxy to Beta/GA
        • Move more kubenet to CNI
        • Windows proxy and networking
        • Multiple pod IP addresses (necessary for IPv6 dual-stack)
        • Continue exploring new Service API
        • Topology aware ingress and proxies
      • Continued work on more flexible pod networking through informal Network Plumbing Working Group
    • SIG Service Catalog [Paul Morie]
      • Paul is out sick today and sends his regrets, he'll do an update next week
      • Feel better Paul! +1
  • [0:37] (Steering Committee) Sig Governance Update [Phillip Wittrock]
    • Goals: help community to self organize by providing a template charter for SIGs
    • Complete: reached out to SIG leads with a long form questionnaire to get detailed insight into how various SIGs are structured and function
    • In progress: developing a template which defines SIG structure and governance within a SIG charter
    • Important: to contribute your insight and experiences to the process, answer these questions https://goo.gl/Zm81Ly
  • [ 0:39 ] Announcements
    • GSoC [Ihor D]
    • SIG Intros & Deep Dives sessions registration at KubeCon & CloudNativeCon will be announced shortly (stay tuned!)
    • Changes to this meeting's format [Jorge Castro]
      • SIGs scheduled per cycle instead of adhoc
      • Demo changes
      • Note takers (+1)
    • Meet our Contributors - Ask Us Anything [Paris]
      • Feb 7th - 8:30am
      • [adding link]

January 11, 2018 - recording

January 04, 2018 - (recording)