Cloud Native Computing Foundation Kubernetes Forum Sydney 2019, 12 Dec 2019

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Keynote: Getting to Know Helm 3 - Scott Coulton, Principal Cloud Advocate, Microsoft

Description

Join us for Kubernetes Forums Bengaluru and Delhi - learn more at kubecon.io

Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects

Keynote: Getting to Know Helm 3 - Scott Coulton, Principal Cloud Advocate, Microsoft

Helm version 3 was recently released with new features and a new architecture to support those features. The changes to Helm and charts were based on feedback, changes to Kubernetes, and lessons learned in the past couple years. In this session you will learn:

• New features you can leverage in charts
• The new Helm client security model
• How using the command line has changed
• Where the architecture has changed to support new features going forward
• Some insight into upcoming features including an experimental feature available today

A

Good afternoon how's it going everyone. Thank you yeah that great that's awesome awesome. So what we're going to talk about today is a little bit about helm and then how emergent three, which, if you're using home version to go to three now it's stable, it's released and, as you all know, there's no tiller so talking about how yeah we'll get to the nodes of the bid in a second so who he uses helm so pretty much everyone in the room for those people that didn't put their hands up.

A

That's totally fine helm is a package manager, not unlike yam, not unlike apt, but for how specific applications and for the windows people out there. Sorry I should I work at Microsoft on the Linux team chocolaty as well, but it's a way for people to pack up package their applications and let other people use them that equipment it is native.

A

So what does the package mint is really? Actually let you do. It allows one person or a team of people to build one thing that many people can use so back in the day before how in the coop Nidhi's landscape, you could have shared your application by kid and a whole heap of llamó and permit izing. It would have been quite difficult so so how I'm come about and what the?

A

What that actually allowed you to do was take a lot of these packages and deploy your application on top of coupie Nidhi's, which was really really exciting, and then what home also allows you to do is take that through your development lifecycle, so you've got a chart that can be tested in the development, did and then put through QA and fraud, and it allowed you to abstract the sensitive data out.

A

So you didn't have to have in UML files like passwords and and and a lot of things like that, so Helms pretty good and of course we support all the major operating systems, so the hell binary can run on Mac, OS, Linux or Windows, but now, let's get to the exciting bit, which is how version 3, and this is where we should be where we're going to, and this is the future of how.

A

So if we have a look at the command line experience you can see now that you have to actually add this. The the stable repo, it's not added by default, because helm is actually moving towards the distributed system of of charts. So there will be charts and developer cousin can choose where charts are, and you can choose what you want to add and what you don't want to add once you've added it, you can edit the repo you can see there. You can search the repo.

A

So this this is a slightly newer feature than was in how version 2, and then you can just see that you can install it from the name. That looks the same as home version 2 so that there's no difference there and now you can see how lists and you can see there that it's deployed to the default namespace and we'll look at a little bit at namespaces in a second and then, of course, if you want to uninstall it its helm, uninstall you'll notice there that the purge flag is gone, that's been moved out.

A

You don't need to do that anymore. Helm, 3 will clean up after itself, so I alluded to namespaces before. Let's have a look at namespaces, so you can see there if I, as I said before, we didn't actually specify a namespace so to install to the default namespace, but we can actually have a look and install different versions of the charts in different namespaces.

A

So if you want to do things like testing, you can see there that I've got a namespace called foo and it's the same Maria to my memory too, and it could have some differences in it.

A

So you could have your production one running or a Deb version, and you could have different tags with the chart running in different namespaces and you can segment it now in home version 3, and you can see there, you can do the helm LS as well with with with namespace food and of course, when you want to install it, it looks very similar to the cube control command, which is just to end flag for namespace and then the stable chart.

A

So here's the home, helm version 2 architecture. How many paper attila fancy, hey Paul. Thank you. You have to remember for all the people that work on the helm project tiller was around before our back. So that's where we ran into the issue of how to retrofit that into our back and I think the way Ford that we went with version 3 is a lot better.

A

So this is how, in version 3, you got the helm, pliant and the kubernetes api. The good thing about this is it uses a normal user credential. So you don't need tiller with a super user or a route to you or a cluster admin. Account in our back, you just have the user credentials and you can deploy what the same way you could with coop control. So if you look at different cloud providers, they've got different iam roles and things like that that will actually black back into the helm in version 3 and the release.

A

Information now with the chart is the secret in a namespace which is completely different to the way it was done in home version 2 and.

A

Combo is now the xdg spec when it comes to storing configuration, keishon and plugins, which is completely different to the way it was done in how version 2. In some cases, we need a way for our systems administrators to install plug-ins and manage configurations, because users may not have permissions, and the following is the XD XD g specification to enable that, among other things, so that's all in the new documentation, home version, 3 I, think a lot of people will run into the issue where you have a developer.

A

That wants to install suddenly, but maybe it needs super level privileges. So this is the way around that to give them not give them super level privileges but install the plug-in on their behalf. A lot of people in the past as well tried to build tooling on top of how version 2, which some people had certain amount of success. Some people didn't to make this a lot more easier going forward.

A

You can see that we've got a go package there and you can use that to use the go API to build packaging, build applications on top of helm. The good thing about this actual SDK is: it's actually used from helm version 3, where some of the stuff in hand version 2, wasn't actually used by helm itself.

A

So this is well tested inside the home client.

A

When it comes to upgrade the new and old Menace press, the new and old, as well as the live state, did not a home version. 2 sorry didn't account for the live state, so it was just the different manifest reconcile. There's a three strip way strategic merge here in helm version 3. So you can see that old manifest the new manifest it creates a patch and it changes the live state.

A

So here's an example: you can see that the sidecar container has been injected by the service mesh. The live State was not taken in the count Inc, the King accounting home version 2 and it would have been lost. So that's just one example of how home version 3 will look at the live State.

A

So here's some addition to charts. So you can see now there's a few extra things being added. One of the one of the things is the API version. 1 is still still supported in helm version 3, so things are all backwards compatible for the most and you can see now that the the dependencies are now in the chart ammo and the there's no requirements Damo. So it's in the chart um and they're in instead of a requirement log file, there's a chart, a log file.

A

So there's some of the idiosyncrasies that you'll see when creating home version, 3 charts.

A

Well, this so there's also adjacent schema that can be used. So the the Jason scheme we can be used to provide details on what's a valid set for the chart, the helm will validate against the Jason. The schema and commands will install upgrade and run, and the the future of the actual Jason format is that you can start to build, build tooling against it.

A

The other thing now that CDs are in the CR D directory inside a chart, so the they are they are not templated and helm knows how to find them here. So this is a. This is a major difference to helm version 2 and.

A

If you want to move your CD IDs across from helm version 2, you have a similar experience by just moving them across and moving from the template directory into the new CRD directory.

A

There's some experiments going on. We've we've helm at the moment the major one is pushing helm charts to OCI registry, so this is. This is really exciting that you'll be able to push a chart into the in into an OCR registry. So this is exciting from the point of view that you would be able to not have this table chart repository, you could push things into docker registry, your own docker registry and and bits and pieces like that watch this space.

A

There's multiple projects working on this at the moment, the other one is scene AB that working on looking at sending descriptors or bundles up to the OCI registry.

A

So if you want to upgrade to I'm running out of time so, but if you want to upgrade to helm version 3, there is actually a plug-in to help you do so. So you can install the plugin. You can then move the config. Of course. Do a dry run.

A

Don't do this in production and just go, how you have upgraded form and deploy it and hope everything works should work in most cases, but did you do to do the dry run and if you want to learn any more about home or version 2 or version 3 he's the docs and the mailing list and jump on the CNC up slack?

A

If you want to get involved, if you want to contribute they're, always looking for people, whether it be darks with a recode features, you found something in town version: 3 does not working, let us know, but that's it and enjoy the rest of your conference for a couple. More tops.