GitLab Distribution Team Demos, 24 Apr 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: ChaosKube 2020-04-24

Description

chaoskube periodically kills random pods in your Kubernetes cluster.
https://gitlab.com/gitlab-org/charts/gitlab/-/merge_requests/1296

A

All right welcome everybody to the distribution demo time today, I'm going to try to go through and work with, Mitch's, mr and that is running cube. Ischemic chaos cube keep on saying, cube monkey, but chaos cube against a running instance of get lab. So I've got a latest chart up and running in an environment that you should be able to see through k-9s right now, and next step is to go ahead and deploy cube chaos. So the.

A

Thought I should have been already into that directory.

A

Can deploy the chart by hand and we'll start to see what happens so.

A

That should have been men killed, okay, mostly email. Let me just kill the email there. We go all right.

A

Don't the inversions can't pull the latest version and, let's just make sure it goes on the right, namespace I.

A

Don't want to wait. Ten minutes, I was looking it starting to look at the page, I started. Looking at the configuration cube chaos a little while ago see if there's any interesting things interval. There is an interval. Okay. Let's just update the interval.

A

Okay, that's a lot more rational, okay, so yeah looks like it's already starting terminating the backend, so we got things going on. I have that's that one.

A

And so chaos, monkey of.

A

See you can do all should already have cube system, yeah, sorry, I'm already saying canceling again, chaos, some cube.

A

Right there right very top, so it is running right expected around a little bit more but okay, so that's good!

A

Really the key thing I was looking at is let it start killing things and make sure that the applications still responding. I have, let's see any share that guy. So here's the book just share the wrong window, but it looked like other guys. Now has a green border.

A

Okay, so I have a web browser into that installation and.

A

Now the only thing I have not ever really ever done, I believe there is QA scripts that will do an automated test. Now you can just run manually, I'd, be nice to just slow, sit there and run the test, but I wanted to say if I remember correctly, it runs for 20. While so anybody know how long it typically runs.

B

The runtime of that is generally under 10 minutes. Oh really,.

A

So we could actually run here and see if we get any failures.

A

That killed the task, runner.

A

All right, so that's the case. Won't we go ahead and start sup data switch back to my terminal.

A

So far everything looks fairly decent killing stuff, but we starting, which is what we'd expect.

A

Where abouts is the QA script, I.

A

Was looking through the helm chart stuff earlier, I did not see anything there.

A

There's our QA repo, so not.

A

Like you guys clicked on okay.

A

Sounds like you, a commands on your system. Okay,.

A

Sorry sure, like that, uh this a little bit earlier see if I get set up before the demo.

A

A

C

A

Teachers like I.

A

Think I usually have a lot of problems. You have like ruby version, said and so forth, which drives money, Ruby crazy, wonder if that's what we're seen in here, I'm gonna have to okay good, only constant pain.

A

Cereals well now off Majesty. This looks like.

A

I'll leave that off.

C

A

Agh same thing, right, yeah,.

A

All right, I give a little bit any suggestions from people. Typically Brighton get lab QA.

A

Am I thinking of this wrong or there's something else, I need to add I.

B

Haven't run it by hand in a little while you.

C

B

Far as I know, the steps should still be accurate from the documentation page I'm.

A

B

You're running Ruby 263, which is about the right level, for what is needed here.

B

This shouldn't be giving you a lot of problems wrong, constant name, URL, yeah,.

A

Every time I try to use an option, I would get that option. Yeah so originated out with.

A

Address and that's what Ron's name address.

B

Okay, the documentation and the process of I'm I've always followed is actually just set through environment variables. Okay,.

A

B

They were actually tried to run it with tactic address before the.

A

Nothing, the repo they just, they don't have much they have, and then they run QA test against your gkd GDK setup and I was looking at that a little bit. Okay, they.

B

A

We have a full guide.

B

That at least worked the last time. I tried it. Okay,.

A

A

A

It just takes me back there. We go.

A

Alright, I'm not finding a page on running since I'll, keep looking for this and sounds like something we need to get into our handbook.

B

It's at the bottom of that page.

A

Autumn of that, each other, you have a chance one more there. It is.

A

A

There we go alright.

A

Get the gym loaded.

A

They actually run the talker okay, alright I.

A

Should have got the gym locker now you.

B

Can follow that? Okay.

A

This should be 1210 right.

B

Unless you specifically said deploy, you know, global dot get live version. 12.10, it's not gonna, be 1210, it's gonna be master, so you're gonna want to use, get live version nightly. Oh.

A

All right, I mean I deployed the latest chart which is 12 10.1, okay,.

B

If you deployed that, then sure, if you explicitly need 2.8 an actual tagged version, then yes you're going to want to set.

C

B

Whatever that version is.

B

You've got a space yep.

A

All right so we've installed the job.

A

A

Need username password, okay,.

B

Future improvement scripting. This would be handy, yeah.

A

He handy would be nice installed in the scripts of the charts.

A

You know generate a token.

B

You don't necessarily have to use the github fortune. You can just skip that. Okay,.

A

Oh, they get how about time. I suppose I still got things on the server, not the running instance.

B

Yeah, in that particular case, just means that when it doesn't have that access token QA will skip the github importer tests makes.

A

A

Yeah I think you'll see a I'll be NMR bigger today, with a new script.

A

License, and that should be good. Okay,.

A

We're pretty out at time, but I'll, let this continue running see if we can find anything.

A

I'm actually thinking maybe chaos cubes should be set to one minute when it just like really just bang on the itness I would.

B

Generally agree: we need to test it by at least reducing it to one or even two minutes. Yep.

A

B

Happening more often well.

A

It's at two minutes right now.

A

I've lost my page, I had had the settings on it again. I have to go find this thing see. If there's anything else, we can turn up out there. That's power level.

A

A

Would be nice to see if there's.

A

Something I would really just bang on it hard where we got close.

A

That's all these coded honors as approvers.

A

So let's get a rap.

B

Yeah that'll be inside the container fairly certain you don't have home gitlab uh yeah.

A

So I get machine. Okay, yeah I want to think about that. You said yes, I'll triple export or heavy load, East temporary directory and store the results in okay.

B

So Miami a question is, is: can we see any logs coming from the unicorn containers, sure yep stern, installed, I thought I did at one point: I, don't typically use stir, but I can give it a try.

B

Well, the other way is you can actually use k-9s and watch.

A

B

From the entire deployment right.

A

That's what I was gonna do okay,.

B

A

Was just rendered us now, the entire deployment is that, just if.

B

You go to the deployments page yeah.

A

B

Colin deployment yeah.

A

Okay and then just logs there, we.

B

Go they pull that up, go down to unicorn and press L yeah.

B

Effectively, if we get actual errors, we should see application level. Errors from these pots is the idea.

B

Now the errors that happened earlier are.

A

Way up there, yeah yeah.

A

This I guess this would be all the ones I started. I want, isn't it well.

B

It automatically follows so it's just going well.

A

It's following now that yeah there's a was it autoscroll today? No, what was it? Oh?

A

B

Right up there at the top Oh.

A

Above I was looking at just the window itself, yeah.

B

The quick help yep.

A

At as far back as it goes,.

A

We should have a lot more than that and there.

B

Is a lot more, it's just. He just doesn't pull at all I.

A

Thought it all.

B

Of it, it probably money. Oh.

A

Okay, I, or is it just when you first go into it, starts from there when.

B

You do it from deployments, it will to control. The API will only hand you so much, because you asked for all the logs of all the containers. I. Don't.

A

B

So we will only hand you so many lines. If you went to an individual container and hit logs, it will give you more yeah.

A

But we don't know which container had the failure in it yeah right. Okay,.

A

All right well we're pretty much at times. They've I get questions or anything else. I want see.

B

I, don't have anything off the top. My head and I don't see questions being raised so yeah.

A

I would say we call it yep click.

C

A

I will plan on putting a script together to run the QA suite against the help chart get into the helmet boss story, easy to run so.

B

Let's make sure we get that tacked into the notes from today and actually create an issue to follow that we may have other priorities. First.

A

Yeah but should be off, I mean yeah, I was gonna, say it should be a pretty straightforward, simple thing to do.

B

Should but it's it could be anywhere up to three hours and we have deliverables. So we need to make sure we get to.

A

C

For now and then we can decide when to work on hey, okay,.

B

Cool next drug I'm gonna stop the recording. It's.

A

Not a good one.