Fwd: Request: Demo at Kubernetes SIG Apps meeting
Barry Schneider
From: Barry Schneider <bschn...@msih.com>
Date: Sat, Apr 28, 2018 at 2:44 PM
Subject: Re: Request: Demo at Kubernetes SIG Apps meeting
To: Oleg Chunikhin <ol...@kublr.com>
I apologize for delayed response, could not get to it yesterday.
Kublr as a product currently focuses more on Kubernetes cluster lifecycle and operations, rather than on k8s applications deployment.
I would be happy to demo it anyways, I just wanted to make sure that it would be interesting to all the group participants and in scope of the meetings.
Having said that, we at Kublr do touch application lifecycle, because as a part of K8s cluster operations we deploy k8s and kublr components, and application lifecycle concerns apply to them as well.
There are some ideas that we have in this area, that may be worth discussing, for example
1. We use helm to manage applications running on k8s
Helm is a great tool, but one of its shortcomings is the fact that it has both client and server side, so it may be difficult from maintenance and operations standpoint. Helm/tiller have quite strict versions correspondence requirements, it may be difficult to manage access and permissions when helm is used etc.One of ideas that we had and that may be worth discussing is building a fully compatible client-only helm variant. The idea is – if helm can manage k8s metadata objects through tiller (which in turn communicates with k8s API), there is no reason why tiller’s logic cannot be moved into the client so that helm client communicates with k8s API directly and does exactly the same, but without the operational overhead and risks associated with server-side tiller.
2. We see that applications and components running on k8s can be roughly split into two categories:
a. Application running on a fully-functional k8s cluster
b. Applications and components that are responsible for some of cluster functionality – from higher-level, such as monitoring, to lower-level, such as CNI/network plugins and device plugins, to fundmantal capabilities, such as kubelet, host packages, api server etc.
While management tools for the first category are relatively well-defined and common – helm/tiller, ksonnet etc; the second category of applications and components is much more difficult to manage. We do it via combination of k8s addon framework, kubelet manifests, and custom deployment code.
It would be interesting to discuss ideas being developed in this area, although here some of the questions intersect with cluster operations and lifecycle.
Regards,
Oleg
Oleg Chunikhin
202-295-3000 | ochun...@eastbanctech.com
Check out our latest What the Tech? 4 Ways your Organization Can Unlock the Possibilities of Big Data
From: Barry Schneider [mailto:bschn...@msih.com]
Sent: Friday, April 27, 2018 9:42 AM
To: Oleg.Ch...@kublr.com; Oleg Chunikhin <ol...@kublr.com>
Subject: Request: Demo at Kubernetes SIG Apps meeting
I would be very interested to have you demo at the Kubernetes SIG Apps Meeting. The next available slot is May 21. Kubernetes SIG Apps covers deploying and operating applications in Kubernetes. We discuss how to define and run apps in Kubernetes, demo relevant tools and projects, and discuss areas of friction that can lead to suggesting improvements or feature requests.
Please use the document below to sign up for a demo. Thanks
--
Barry Schneider | Chief Technology Officer / Chief Operating Office
M: 240.997.4940 | O: 301.850.4300 x1990 | LinkedInMSiH LLC | www.msih.com
This communication is intended ONLY for the use of the individual to whom it is addressed and contains information that is PRIVILEGED AND/OR CONFIDENTIAL. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copy of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by telephone and/or by email.
M: 240.997.4940 | O: 301.850.4300 x1990 | LinkedIn
M: 240.997.4940 | O: 301.850.4300 x1990 | LinkedIn