GitHub Open Source Friday, 1 Jun 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Cloud Native Dev-To-Deploy Pipelines with GitHub Actions

Description

Cloud Foundry is joining us for Open Source Friday to show off using GitHub Actions to start automating your deployments to Kubernetes.

Join +bdougie and coder_blvck in learning how to get a Cloud Foundry instance connected to a GitHub repo.

https://www.cloudfoundry.org/event/how-to-setup-continuous-pipelines-to-depoloy-to-kubernetess-with-cloud-foundry/

As always, feel free to leave us a comment below and don't forget to subscribe: http://bit.ly/subgithub

Thanks!

Connect with us.
Facebook: http://fb.com/github
Twitter: http://twitter.com/github
LinkedIn: http://linkedin.com/company/github

About GitHub
GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Millions of people use GitHub to build amazing things together. For more info, go to http://github.com

A

Welcome to open source friday uh opens friday is. It is, of course, friday, but it's a day that we get to sit and chat with open source, maintainers contributors of the like to talk about just that which is open source, and today we got a special guest today, which is shedrack coderblack on twitter. uh Welcome, shedrag, how you doing hey brian nice to be here: hi, everybody yeah, so cloud foundry. What uh what are we working with today.

B

Yeah, um so um class launcher is basically an open source platform service. That's you, basically, installing your on your infrastructure so um think heroku, but probably um open source, and uh this time you have so much control over it and it's on your on whatever infrastructure of your choice. So that's! Basically what cloudflare is it's a cloud native, um open source um platform, service, yeah.

A

If you don't mind, could you uh walk us through what you're working with and what cloud foundry has to offer.

B

Yeah yeah yeah, um so I'm basically going to be um deploying a simple application. So this application is from um it's from one of mdm to mozilla document um network. So I'm going to be playing one of their sample tutorials on cloud foundry um with github actions, so we're basically going to automate the whole deployment process so that whenever we make a push to that particular repo, um it triggers a github action and it deploys the application superintendents through um cloud 400.

B

Now this is possible because of the cloud funding for kubernetes projects, which is um basically bringing the cloud from the developer experience to kubernetes. It's basically an abstraction over the cloud foundry on provide kubernetes and making it easier for developers to know the to for developers to deploy stuff to kubernetes. So that's, basically what I'm going to be showing today and um currently I have um my cloud foundry for kubernetes cluster deployed on google cloud.

B

um So it's basically has some setting um requirements, so I think if phone node cluster, um eight gig of ram um etc. So I currently have that installed and um yeah. So let's just get started. um I don't know if you can see my screen, yep yeah. We're definitely yeah as well okay, so you can see my screen yeah, okay, so um so basic. Currently I have um my cloud foundry for um kubernetes cluster installed on google cloud and I've also connected the github container registry.

B

As my preferred container registry, you can also use docker if you want, but for this particular demo I am using um on the github container registry, so I'm just going to log into that cluster. um So I've also connected so there's an api endpoint that you can connect to from. um It's basically um going to be generated for you whenever you um deploy whatever infrastructure that you desire to use and for this demo, I'm using the google cloud and um the.

A

Gk generally yeah, I was going to ask if, um if this was cloud, foundry was hosting your stuff in the cloud for you or, but you actually mentioned. um Google cloud is uh you're using google cloud under the hood to be able to have this hosted.

B

A

B

You can install whatever infrastructure that you want. We also have our um specific. um We have a bunch of distributors um distributions generally that are using cloud foundry um under the hood, so yours there's ibm cloud foundry, there's on susa, there's also um vmware tanzu. So if you want to like deploy on something that kavanji has to do with um generally without you know going to digitization, google cloud etc, so you can just decide to use those um over um distributions.

A

Okay, excellent yeah, because I I've got some uh some things I deploy to azure and uh I'm not using kubernetes, I'm actually deploying to one one cloud uh and one um one server. But I'd love to have that deployed to multiple servers for the benefit of the cdn.

B

Yeah yeah sure you can do that, um so I currently have um this application running. I'm just going to show my um share my um vs code. So can you see my vx code? Yep yeah? We got that yeah yeah, so it's the purchase is really really simple. That's the beauty of like having car foundry on your infrastructure using california in general.

B

It's really really simple, um so you the basically the way it's to basically create the way you're, creating random action, a random github action, so um the github profile um on folder, then inside the workflows folder then do a main dot yaml. Now the name of this action is deploy using um actions. Then you know on push branch. These nodes are all like um the gate of actions.

B

Lingo now the job we just have one job, which is, um we need the action to always um to trig, so basically, deployment should trigger whenever we make it push that part to the repo that um this project is on, so um we're using, of course ubuntu as our preferred um system. Now this particular action uses.

B

Is he already published github action which was created by my um colleague, so um this is going to be called the cli action, we're going to be using that you can, you can decide to clone it and use it yourself or you can decide to just create copy and paste it somewhere and use it. So that's really really um there's an mit line, sense project, so you really don't there's no um privacy or whatever or intellectual property on it, and um so it's simple. The action has um to use this action.

B

You just need to provide certain details like a bunch of details, so the cf api, which is the api endpoint that I showed you um oden. Sorry about that. So I showed you here so some this is what we are using, but this is not exactly what I'm using because I changed it before the demo.

B

um So, of course we cannot specify setting secrets on our foot on our project because of security reasons, so um in so of course, the cf api, like I specified in my engineer in the secrets in my github project, then the username then the password. Then these organizations are basically um um um ruby's access. Control protocols like just how it sees in kubernetes but as sort of like different, so we have orgs organizations and species just like the way um um kubernetes regulators have like rules and name species etc.

B

So that's how it is here, so the organization I have here is, of course, sample organization and space which is specifically for just me, um is um dev, then um the command.

B

So what's basically, what cloud foundry offers use is you push you can deploy to kubernetes with a single command, which is the cf push, then your application name, so the command here would push our application to a criteria cluster and deploy it on kubernetes and as easy as that. So this is basically every single thing you need to do to actually create a kit of action that can help you to deploy your stuff to your project, to cloud foundry as easy as it is. That is really that easy.

B

So um let me just see if I can trigger a deployment, so I'm just going to you know, make a simple change to this rep um to this project. So um for the benefits of the viewers, this is actually a project from the mod for mozilla. It's um it's been one of their tutorials and I just cloned it and deployed this cloud foundry. It's that simple. I don't know if I can show how the um it looks like. So this is how it's just basically a library. It's a local library view to express a node.js.

B

So you can see all books, you can see um authors, you can see um general, you can also add, etc. So that's how the application looks like now. If I come here, if I come to my um get, my ps gonna make a simple change to maybe change, maybe add a new color or something so um let's come to views and maybe do something really really simple.

B

um So, let's just say: let's give this a h3 tag. Let's see if it's a history tag then save it now, whenever we push this to github, it should, according to what we specify in our action, it should automatically start the deployments to um to cloud foundry. So if I come here- and I do my gate status and see okay, this this- um what this has been modified according to gates- then I do a git add. Then I do a decommit, then let's say updates. Let's just call this an update name is an update.

B

Then we do um get push so when we do a good push this should um so. These are like aliases I created to oh my.

A

B

When I do a git push, it should automatically study deployments fingers crossed. So if I go to my github, um if I go to github, if I go to github here, I should see um one of the actions triggered on the actions yeah yeah yeah. So, as you can see here, it has automatically triggered the the action. So, let's check what the action is doing, let's walk through that. Let's see um the whole process so the whole. The action is actually three jobs and four jobs, so it basically uses.

B

um I would explain this as when it finishes running, and so it basically uses the effect stats with installing the cloud foundry on cli based on. What's um the action that my colleague has created that we're using then, of course, checks out basically makes the project available on this um on this environment, then we do a safe push. So it's that simple. So the first thing the action does is set up.

B

The job, which is like same thing for all case of actions, then build ram demos, which is basically creating a container based on the docker file. In that um action that I'm using that my colleague has created um that you can also use, so it's just like a docker file and doing exactly what the docker file has like specified, which is basically to install um the cloud foundry cli version 7 to make it available here so that we can do a safe push. That's why we need on the cliff and cellar in this particular environment.

B

So it basically does that. Then. The next thing, of course, is to check out so make this repository available. For you know for reading and writing in this particular environment then um next would be to now you see, as you can see, our job is completed already.

B

Now I don't know it took a minute and 3 seconds to you know, deploy the whole thing to check out for the entire job, to run and deploy to um to cloud foundry, so yeah, um that's how fast it can actually do um deploy any actually any application, if I'm not mistaken any application. So um the next thing is to look at how what this particular um action is doing the action where you are using our project, what it's doing so. The first thing it does here is to um export all this.

B

All these things we've specified in our github um in our github secrets. It basically matches its b2 um um to the command you specifier, so the cf api, it checks and gets it from the cf secrets um that we specified the username, the org, the um space etc. Now the command. So, let's walk through the whole process. So the next the thing the first thing it does here is to connect to the api endpoints. So it can have access to the cluster we've created, which is really really important.

B

It cannot do anything if, if this particular step fails, the entire job will fail. So it has to connect the api endpoint, so you can have access to the class that we've installed on gke now.

B

The next thing would, it would be, is to package the files now so cloud foundry um has a way of detecting the type of application you deployed, using what we call build packs, so buildback's basically created an application runtime for your project, so whatever um dependencies you may need whatever um different environments you may need to deploy for um the dependencies of your application to install successfully cloud foundry helps you with that. So for this project um a node.js project, you do not need to upload your node modules folder to cloud foundry. It does not.

A

B

That yeah, it does no need. That's why your deployment is fast, so immediately it um your you, do a cf push and the butte pack is triggered. Why, which is the node.js built back? It then checks for setting files, for example, if you use yarn it checks for um your yarn lock on file, and it also checks for your package.json. These are the two things it needs to complete your entire build for the entire view to.

A

Happen, if that's the.

B

uh Cloud foundry side, not in the docker.

A

B

Yeah, the cloud foundry site- this is done by the cloudfront which build packs yeah, so um when he does them does darwinians found those particular when crowdfunders found with the help of buick has found those two, those two files. It then begins to. You know, specify certain things that are needed for it to run. For example, it installs um npm um uses the mp and built packages also on nbn, build pack and a young duke pack under the node.js buildback.

B

So if you use the and uses the and buildback, if you use npm uses the npm build pack and begins to upgrade, commands do like wrong commands like npm brown, um dev npm, start npm, build, etc. Just so based on what is in your packet logistics and that's why all these checks for your package using some file now. The next thing you to do here is to upload package your file and upload it to the cloudflare on the api for deployments.

B

Now. This is where the github container registry comes into place. So I, if you've, used the github container registry, you would know that this particular um url here belongs to the github container registry. So it basically pulls every single thing needed uh in the github container from the github container registry and uh makes it available in this environment. So we don't need to do. um We just need to configure the github container registry for this, and um it would happen.

A

B

Can real quick.

A

B

When I explained.

A

That the github container registry is a it's a feature on github that uh we've shipped uh in the last year or so, and uh I just wanted to point out that folks, if you are using containers or building packages, it isn't a future.

B

A

You that we'd love your feedback, yeah.

B

Yeah, it's a it's a really really um great step for github to be honest, and um it's been really really easy to use and it's really really easy to get fired a bit. So um I have specified this so for this particular situation. I could decide to use docker container registry or, but I'm specifically using github, and this particular thing can be set whenever you're, installing, um um whenever you're installing stuff, okay, that's covered for kubernetes or any infrastructure of your choice.

B

If I, if this time, I would show a a file where you see how I specified you know this particular um where I specify okay use the github container registry here. So if there's time so, um the next thing it does is, since it has discovered the package.json file and maybe my package log deduction file, it has now instructed the built pack. Okay, this is the build packs we want to use so the node engine build party, um the npm installed. You can npm stack because you are using npm.

B

So the next thing you need to do now is to start the whole process. The next thing. After starting the process, it detects our node version. Now you nodes version is very very important because it's, the certain types of features are not available in a particular node version, that's available in this node version.

B

So if you have specific needs for a particular node version, you need to specify your engine, the node engine in your package.json file, so cloud1 you can use that notation, otherwise, crowdfunding will use the defaults, um its default node engine, which is probably the latest most of the time. So we don't really need to see this most of the time now, as you can see here, the build is successful.

B

After the building successful the command specified here will now be used to start our application, which is what the fundraiser is doing here now waiting for app express library, the local library tutorial to start now. The instances here are starting then immediately. The application starts this all of this here becomes available to for you to see so the name of our application, the requested um states, which is started the um um this isolation segment.

B

You do not necessarily need to fill it, then the routes here now this route system is very, very important, because this is where we can find our application running live on on the internet, so we need a link to see a preview of application. This is where we can find it now. If you've noticed this here is our api endpoint. So this is the api endpoint we connected to when we're like starting the whole process. So.

A

B

Itself is it's generated by.

A

Is this also generated by google cloud and added no.

B

But cloud foundry by cloud foundry, okay, gotcha, is cloud foundry doing.

A

The handling, the routing or being sort of the consumer of that yeah yeah, it's doing the routine. It's doing the right thing, gotcha.

B

Yeah, so um the next thing here is, of course, specify you know you if you are using any specific grid, packets or specified and, of course, the type the process type is a web. It's a web version, then um the start command, which is the command you use to start the application. This is also the amount of memory it's using. So it's like. I think this is a one gig um it's using. Basically one you can specify the type of amount of memory.

B

You actually want your application to use in what we call a manifesto yml file. So if you, if you are setting specific needs, you need for your application to run well. Maybe you need to is to deploy a particular folder in your application. You can use the manifest. The well mail file then specify um the folder um that you wanted to actually deploy from. Then, if you also have a specific buildback that you are using, maybe you have um um you wanted to use immediately use the bit packet.

B

You can also specify it in the white manifest the wiremail file, but the aim really is to I'll make sure that you do not have to write a um yaml file for your deployment. Now, as you can see, the application here is um currently running and um to see this application running live. We need to copy this, so I'm just going to copy. This then come to my um a new tab and just paste it yeah. So this is basically application deployed, live on cloud foundry, it's that simple.

B

So whenever I make a change whenever I make any single change, whenever I make any single change here, it automatically triggers a build and that build would um create um trigger the date of actions and from gate of actions. Just working with episodes to you know, deploy applications to um cloud foundry. So that's how the whole um process works. This is how you can automate your um deployment um to kubernetes purchase with github actions. It's that simple!

B

You do not need to do any specific, and you know any stressful hundred lines of yamaha to do this. To do these things yourself.

A

B

You push to github, you can automatically trigger a deployment to um cloud foundry, so yeah.

A

I like that, because it's democratizing the sort of knowledge based around kubernetes, like I, I don't have enough skill sets or even knowledge to be able to do this, build this myself yeah. What about uh community? Is there a yeah.

B

A

If you want to join.

B

The cloud from your community, the best way to get involved, is actually to you know, go to the platform slack, which is um slack.cloudfoundry.org, and you can just easily create an account and get different channels based on what you want to do and, um for example, now, for if you have like the specific tutorial that you want to talk about, you can go to the channel crowdfunding tutorial, so slack.org would um make give you access to the platform it's like, where there's like a ton of people and that's sharing ideas and like answering you ask questions.

B

So that's really the best place that um you can get um involved in the cloud foundry, I'm community and there's also, um if you also want to like get more ideas, there's um the cafe on your summit is coming up. So, if you want to like join the cloud from your community, you want to learn more about people in the community. Like breakthrough, I break into ideas like happening in the platforming community. You can easily just go to um join the cloud foundry summit and um yeah just listening. There are all these great talks there.

B

People from like various parts of the world and also various companies, we probably have people from vmware people from like ibm um people from um nines, etc. Like cloud native tech experts develop experts like from various parts of the world that we come together to talk about um cloud foundry and devops in general,.

A

Yeah, so the actually, let me share my screen. uh We shadrach and I actually chatted on my other place like I do stuff, which is jamestack radio, um so audio form, but we talked about cloud foundry and I feel, like I learned a lot in this this conversation, but now seeing it in action. uh I know so much more now and I know exactly what I'm going to be using it for in the future. So again, thanks for taking the time and.

B

Yeah, I'm just.

A

B

A

Yeah yeah, I would just shout out: uh everybody follow shedrack on twitter coderblack on twitter. There's the handle right in the lower lower right uh as well as follow this channel, follow the youtube uh we're making some changes in the next couple weeks too, as well, and how we sort of announce the um the the new stream. So following this channel will be the easiest way.

A

But if you follow the github community, twitter channel uh we're gonna start tweeting from there, as well as in the support community, so github.community as well uh and we'll have a place for you all to meet the maintainers and contributors of projects uh as well as, of course, start the projects. That would be a great opportunity for you to engage and show the appreciation as well so.