Cloud Native Computing Foundation KubeCon + CloudNativeCon Europe 2021, 14 May 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: SIG CLI: Intro and Updates - Maciej Szulik, Red Hat; Katrina Verey, Apple & Jeff Regan, Google

Description

Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon North America 2021 in Los Angeles, CA from October 12-15. Learn more at https://kubecon.io The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.

SIG CLI: Intro and Updates - Maciej Szulik, Red Hat; Katrina Verey, Apple & Jeff Regan, Google

During the introduction section of the presentation, the leadership of the SIG CLI will give an overview of the projects hosted by the SIG. The presenters will describe the current state of these projects, including such popular ones as kubectl and kustomize. The introduction will also cover the contribution process for the SIG, including specific steps on how new contributors can successfully on-board. In addition to this introduction, the leaders will provide several short educational presentations, such as a deep dive into kubectl debug. The final part of this presentation will include a live Q&A.

A

Hi, my name is mache, and today I'm going to talk to you about 6, cli, intro and updates, but before jumping into further discussions, let me quickly introduce you what sig cli is and what's our mission, so six cli or special interest group devoted to command line interfaces accessing kubernetes cluster.

A

Is a group of people devoted to making clies better?

A

Our main project is cube, ctl, cubecontrol or cubicuddle, no matter how you prefer, naming it. It's still our main goal to ensure that working with any kubernetes cluster is easy and fun.

A

Cubecontrol allows creating plugins and, as such, we provide you with libraries cli run time and a sample cli plugin, which shows how to implement plugins.

A

We have three sub projects, customized, which allows you to customize row, pre-template yums, leaving the original yum untouched and usable as is, and work with kubernetes resources, crew, which is a plugin manager for the aforementioned cli plugins crew, also has a crew index where you can register your own plugins, so that other consumers can ease easier, easily find them. Finally, kui koi is a graphical wrapper around cubic cubic control.

A

It allows it provides. Sortable tables and much more uh graphical, rich user interface than the usual qb control, which you have in the command line.

A

6Cli has four people that are working on. Ensuring that the sick is in is going in the right direction. We have two tech cleats that will be philip witchrock and myself, and we have three chairs eddie sean and myself.

A

The three of us are responsible for organizational stuff for the sick, whereas the tech leads are responsible for the technical direction of the six cli.

A

Our meetings are happening on wednesdays, every other wednesday at 6, 00 pm european time at noon. U.S, eastern and 9 00 a.m. Pacific time, on top of that, we have monthly bucks crops happening at the same time.

A

It so happens that the next meeting is the next six cli meeting is on may 19th, whereas the monthly box crop will be happening. The next week, which is may 26th, you can find all of us in the 6cli kubernetes slack channel.

A

On top of that, we also have our mailing list group, where you can reach us, ask for help or provide suggestions for improvements.

A

Now, let's jump into the main changes that happened over the past couple of months to the sixth cli. First of all, welcome kui, which completed the transition up to kubernetes 6 repository koi was originally started by ibm. Folks, big shout out goes to paul nick mengting and mark who diligently spend couple of months of their work.

A

Moving the kui repository under kubernetes 6 organization organization.

A

The next important milestone that we just recently reached was upgrading customize in the kubernetes repository name specifically in the cube cuddle. So if you're familiar couple releases back, we included customize by default in cube control.

A

It was accessible either as a sub command for cube cuddle or it was accessible through dash k, which was which could flag, which could be used to many different commands in cube cuddle.

A

Unfortunately, due to dependencies issues in customize, we were stuck with a very old version, two of customize in cube control for a very long time. Jeff and the entire community gather around customize work diligently over the past couple of months to ensure that the upgrade was possible.

A

Finally, in march of this year, we've completed the transition and cube ctl ships, the latest customize available. We don't expect too many significant changes, so.

A

Your pre-existing customized file should still work. The api hasn't changed between the previous version and the current version of customize in cube ctl.

A

Although some some of the bug fixes technical depth was addressed in the meantime, most likely, the only changes that we are expecting or problems will be coming from the fact of improper usage of the past version of customize.

A

We do hope that a broader community will be able to provide us with feedback, as well as provide some suggestions, how to better improve this situation in the future.

A

The next important development that is happening in the six cli community is observability couple months ago, or even years, phil created a proposal to send cube control commands as headers through requests.

A

This way, we would be able to identify which commands are being used, the most, how people are using cube control and on top of that, ensure that the people are using the most.

A

The latest possible version sean spent couple of weeks this year and put together a alpha implementation of this functionality.

A

Currently, if you invoke cube control with a specific flag with a specific environment variable the commands that you're executing along with the flags, are being passed through headers to the api server, where we can then investigate what's going on and how clients are clients or users are using cubecontrol.

A

We hope that this will allow us to improve, keep control and the user experience in the upcoming months.

A

The feature is still alpha, so you have to explicitly up in, as I mentioned before, there's a cube control underscore command, underscore headers environment variable that you need to set to true to enable this functionality.

A

Sean will most likely will be working on this functionality over the next couple of months. If you're interested in working on this feel free to reach out to strong and ask him for work to be done as well as suggestions so that we can improve this situation.

A

One last mention that I wanted to include here is a change coming from paco who created a default container annotation. This way the commands were the commands such as exec, logs and similar, that are working with multiple containers in a pod can pick a default container.

A

Normally, the default container is always the first one in the yaml file, but if you want to explicitly state which default container a command should pick, you can do so by annotating your particular pod, with a cube control that kubernetes dot io slash default container annotation this way when you invoke either logs or exec you'll, get information directly from the default container.

A

Finally, I wanted to make a to shout out to zao and a bunch of other people that gather around a task that we had, which was about removing generators from cube, cuddle, create commands this spans several months or even releases. If I'm correct, and thanks to the hard work of the community and zao who took the leadership in driving this future forward, we are able to say that 90 we're about 95 there.

A

Most of the generators have been removed and the code in cube, color, create commands is much more tested and much more readable. So big thanks to all that are involved in this effort.

A

At this point in time, I would like to focus on the future of q six cli.

A

There is many things that we would like to work on, but there's only so few of us if you're interested in working on any of the features that I'm going to talk about, feel free to reach out to us.

A

One of such developments that we would like to undertake in the upcoming months is the return code. Normalization currently keep control only provides two return codes in their commands. There's a zero and non-zero exit codes.

A

If you're familiar with many of the linux clies, you are aware that the commands are returning different error codes depending on what the situation was.

A

We would like to be able- and there were many requests from the community- that the cube cultural commands sub-commands are returning further information about what went wrong, not only through a description, but also through an error code that helps with scripting and including cube cuddle in further optimization automation, so ricardo put together a enhancement, we're looking for interested in contributors who will put together a proposal walk through all the existing commands and figure out. What is the possible outcomes that we could get?

A

What are the possible return codes that we could have from the cube cuddle command? I have several suggestions: I'm pretty sure that others in the community have suggestions as well.

A

This topic was discussed several times during our past meetings, and I know that there will be many opinions when developing this topic, if you're interested in feel free to reach out to us, join one of our six cli calls and talk to us about your proposal.

A

We would like to hear from you and we would like to be able to work on this further.

A

There is one another development that I would like to bring to your attention.

A

Over the past couple of releases, we've been consistently trying to unify how the commands work. You probably are familiar with the option structure and the flow which includes three methods: complete, validate and run.

A

If not, I recommend to you to watch our previous recordings or our meetings where we describe how the those three methods provide a consistent flow across all of the commands.

A

We've managed to get to 95, maybe 99, even percent of the commands transformed into this flow, but we're not there yet we're slowly addressing the remaining commands. But at this point in time we would like to decouple the current business logic of every single cube cattle command from the cobra cobra library is the library that we are using for providing the entire command line interface.

A

Unfortunately, the decision that we've taken in the past cost that the copyright library is very tightly coupled with every single command, like I've mentioned before the previous effort, simplified commands and unified how they work. Currently, we want to go one step further and decouple them so that other consumers of cube, cuddle or parts of cube cuddle can easily get the same. Behavior that the cube cuddle provides at this, especially that there was a lot of requests for moving certain cube cuddle functionality to the server which is not always possible.

A

So we're hoping that, with the help of the community, we will be able again to address those issues, sean volunteered, to create a template which basically means creating apr showing how this should be addressed. As soon as the template is available.

A

We are more than welcome to see prs from other people in the community, even new contributors addressing and solving this problem, we're hoping that this will even more allow reuse of cucurl functionality across the community.

A

This is basically all I wanted. I have prepared for you today. I encourage you again to join our six year line bi-weekly meetings and our monthly box crops.

A

The latter are very good for newcomers as well, because during our box crops we go through issues and pull requests and we allow newcomers to pick a very easy task to work on.

A

Our bi-weekly meetings are very good place to raise issues about feature, requests, plug interesting, cube, cdl plugins or in general, about your feedback about cube, ctl or any of our sub projects.

A

We are more than happy and welcome any feedback and any suggestions either through our six eli slack channel or our mailing group. Thank you very much for your time have a great of the rest of the kubecon.