Skip to content

Latest commit

 

History

History
203 lines (131 loc) · 9.17 KB

meeting-notes-2015.md

File metadata and controls

203 lines (131 loc) · 9.17 KB

sig-node weekly meeting

Dec. 9

Dec. 2

kubernetes/kubernetes#14216

rkt prs:

https://github.com/kubernetes/kubernetes/pull/17968

https://github.com/kubernetes/kubernetes/pull/17969

rkt fly

rkt/rkt#1825

Disk Accounting Proposal - kubernetes/kubernetes#16889

Nov. 18

  • kubelet + systemd?

  • design of cgroup hierarchy ideal (Vishnu)

  • Nalin to send out volumec branch and design doc

  • Discussion on logging (Vishnu to paste link to existing issue)

    kubernetes/kubernetes#17183

    • rkt team to measure overhead of running the journal in container

  • Discussion on PID1 being systemd in the infrastructure container or not and different strategies; sounds like measuring needs to happen here rkt/rkt#1788

Just to be super clear it seems like we have three divergent paths for running a docker container that are likely to exist in the kubelet:

  1. Docker engine mode

  2. rkt mode

  3. runc+systemd mode

Nov. 11

  • Cancelled as people are in the kube-con

Nov. 4

  • From google: 1.2 releases focuses on testing
  • Node conformance test, e.g. including testing the kernel version, kernel config, docker runtime, rkt runtime, systemd version, etc. Such testing makes the node is validate to join the cluster.
  • coreos side: yifan working on converting the gce master to use coreos image. also need to work together with node team on the node conformance tests for rkt.
    • question on setting up the master node : what's the best practice to maintain those pod templates (e.g. kube-apiserver, logging, dns addons) kubernetes/kubernetes#16760 (comment)
    • dawn chen said we can run a script that's in the saltstack dir on the node, which evaluate the pod templates.
  • vish asked about the status for the rkt after our last discussion about the pod lifecycle
    • not much progress, mentioned jonboulle's rkt fly pr rkt/rkt#1416 (what's the status for that? @jonboulle)
  • dawn chen asked about what's rkt's currently developing direction? https://github.com/coreos/rkt/blob/master/ROADMAP.md#rkt-roadmap
  • Also she would like to know our OKRs in the next quarter. (rkt, etcd, tectonic?) Can we share that with her? @jonboulle
  • mics: vish talked briefly about the latest updates in OCI, splitting starting of a container to create and start. yifan mentioned we have recently put efforts on acbuild (an appc image build tool) https://github.com/appc/acbuild

Sept. 30

Date: Sept 30, 2015

Attendees: YiFang, Jonnathan from CoreOS,

               stclair@, yjhong@, vishnuk@, dawnchen@ from Google

Agenda

What is a Pod:

  • Shared namespaces excepting mount
  • Restart policies will be at pod level
  • Per-container restart policies are required for certain volumes git pull?
  • Life cycle hooks at the container level are needed. Pre-start hooks at the container level.
  • Privileged pods require access to host

Why pod updates?

  • Pod updates are needed for updating image names - misspelled image names and in-place image updates.
  • In-place updates are very useful when containers cannot tolerate restarts. For example, applications that load a lot of data from volumes before functioning.
  • Auto-scaling requires updates to pods.
  • Adding/removing containers - in-place updates using a hot-swap mechanism - start a new container and remove the old one. Adding/Updating side-cars (logging, monitoring, etc)
  • Updating volumes to pods are also a very useful feature for users.
  • logging: yifan to check fluentd, how can it integrate with rkt/journal