Upgrade to Pro — share decks privately, control downloads, hide ads and more …

SIG-Apps update 05-11-17

SIG-Apps update 05-11-17

for the Kubernetes Community meeting

Michelle Noorali

May 11, 2017
Tweet

More Decks by Michelle Noorali

Other Decks in Technology

Transcript

  1. SIG-Apps Update Michelle Noorali, SIG-Apps co-lead

  2. We’re growing up so fast!

  3. Time flies when you’re having fun... • May 9th -

    initial meeting about creating SIG-Apps • May 18th - 1st SIG Apps meeting • 42 SIG-Apps meetings, 2 in-person • 42 technical demos • Many discussions, presentations, surveys
  4. Why SIG-Apps? • Up until now, ◦ Understand how to

    define, install, and manage applications in Kubernetes ◦ Talk about & iterate on higher level tools for Kubernetes ◦ Keep up with Kubernetes workloads features & improvements ◦ Provide feedback on apps experience ◦ Friendly place to start k8s journey
  5. • Workloads features and improvements ◦ Done ▪ Daemon Set

    Update functionality in 1.6 ▪ Deployment/Replica Set bug fixes 1.6 ▪ Moved Deployment to Apps API Group ◦ Current or In progress ▪ Switch Deployments to new hashing algorithm w/ collision avoidance ▪ Moving CronJob to beta ▪ Fixing flaky tests ▪ Stateful Set • Update functionality (similar to Daemon Set Update) • Roadmap for GA • Bug fixes
  6. SIG-Apps houses several umbrella projects.

  7. • Helm ◦ Kubernetes package manager ◦ Officially graduated from

    Kubernetes incubator in February 2017 ◦ Latest release 2.4.1, growing community ◦ Gifted 2 slack channels: #helm-users, #helm-dev ◦ Growing pains (note: these should sound familiar) ▪ Keeping up with answering questions • Kudos to the community for jumping in ▪ Contributing process • Pairing with new contributors • How do you allow community members not on the core team assign issues to themselves? ▪ CircleCI woes ▪ Figuring out core team processes ▪ Outgrowing documentation: efforts to make this better
  8. • Kompose ◦ Tool for moving from docker-compose to Kubernetes

    ◦ Latest release 0.6.0, monthly releases ◦ Making progress with implementation of docker-compose 'build' ▪ Might be ready for next release ◦ Still in incubator, close to graduation
  9. • App Registry (previously CNR) ◦ Initially a spec for

    push, pull, discovering Kubernetes Apps ▪ Designed to be integrated into different platforms ◦ Officially released by CoreOS at CloudNativeCon/KubeCon EU in March ◦ Push, pull, and discover Kubernetes apps through Quay ◦ Helm plugin available ▪ Login to Quay ▪ Push charts to Quay ▪ Install charts from Quay ◦ Working on Quay UI Integration ◦ Working on Kompose integration
  10. • Official Kubernetes/Charts repository ◦ 70 stable charts, 9 incubator

    charts, 70+ open PRs for new or improved charts ◦ Facing & figuring out scaling challenges ◦ Focusing on and highlighting best practices ◦ KubeApps.com for searching through charts ▪ Built using github.com/helm/monocular
  11. • AppController ◦ Install/upgrade/delete Kubernetes resource in pre-defined order, with

    parent-child hierarchy ▪ Creating resource graphs ◦ Focus is on complex deployment ◦ Led by Mirantis ◦ Working on Flow - way to reuse subgraphs as atomic components in multiple releases ◦ Adding more examples ◦ Improving documentation ◦ Helm integration moving forward ▪ Created ability to have pluggable release backends in Tiller (called Rudder) ◦ AppController demo + Q&A at SIG Apps May 22
  12. • OpenCompose ◦ Higher level abstraction for Kubernetes resources

  13. Key Interests & Activities • Still doing short technical demos

    of tooling • Umbrella Projects ◦ Mentioned on previous slides • Kubernetes workloads features & improvements • Writing less YAML ◦ OpenCompose ◦ Common Chart (Helm) ◦ kube.libsonnett
  14. Logistics • Alternate between two meeting formats ◦ demo +

    standups ◦ demo + discussion topic • Still meeting weekly
  15. Going forward...

  16. Adnan Abdulhussein Newest SIG-Apps co-lead; Engineer @ Bitnami; Charts repository

    maintainer; Todo app demo expert
  17. Adding and Iterating • More discussion around best practices &

    patterns • Set better context around demos and discussions • Good solid feedback loops • More detailed notes • Feeling out meeting formats
  18. EOF