everything you need to pass the 2022 updated CKA (certified kubernetes administrator)

hey everyone and welcome back to gen is code today we're going to be talking about the certified kubernetes administrator exam what you need to study what updates did they make to it and lastly tips and tricks to make you faster and pass your exam with ease so as usual we can jump into today's readme as always these are located at github.com jedi as code this specific one is slash wiki used to be called resources but i change it because i like the name wiki better just to give a little bit of background i took the the june 2022 updated version of the cka they change it to be completely in a remote desktop previously wasn't this way but hopefully some of the tips that i'll share about the exam environment will help you when you take yours it took about one month of general study time three days of exam prep the total exam is 120 minutes but they actually give you 122 minutes when you get to the exam but don't count it prepare for 120 minutes and then i feel like i moved pretty quickly after my first pass-through through all the questions i think i skipped one i had about 50 minutes left and i skipped it because i knew it would take a long time not because i didn't know it but i passed out the score of 91 you only need 66 percent to pass so i can definitely help you get there so in today's guide we're going to be talking about how to study what materials you should go over depending on where your level is at with kubernetes next we're going to be talking about the testing environment again it is now on a remote desktop so i'll give some details about that and lastly a finesse guide this is probably going to be my favorite part i'm just going to be sharing a bunch of tips tricks aliases functions uh stuff like that to make you really fast on the exam because again it's a timed exam open note so you can have all the docs but it's really up to you to really know where to look and what commands you need to kind of have down to a t so you can pass with enough time all right first things first you got to get your material down to a t you got to know kubernetes not like the back of your hand but pretty well so there are a couple ways of doing this i prefer to just take one of those guided courses provided on the internet i took the uh the a cloud gurus cka course right here before i made this guide i did a little bit of research and it seems like everyone on the internet really recommends code cloud ck certification course again links to everything here on the uh the readme but if you don't have a cloud guru for free like i do i recommend that you take the uh the code cloud of course instead if you already know kubernetes like the back of your hand again you don't need to take one of these courses but the next couple steps i do recommend regardless of your skill level the first thing that will help you a lot on the exam is the killer.sh exam simulator now regardless of your kubernetes skill level i highly recommend that you go through the killer.sh exam simulator it aims to be very similar to the cka exam itself it's pretty similar but with the new virtual environment it's a little bit different but they give you more questions they give you harder questions all within the same time limit as the actual cka so if you can do this guy and pass with a really good score you'll have no problem on the cka one thing i will say though is um they give you two free runs with the purchase of your cka exam so not that free but you should definitely run through this exam simulator at least once and then review after you're done with your run they give you an explanation that goes question by question on how to solve each one of the practice questions on the killer.sh simulator i recommend that you read every single explanation regardless of how comfortable you are on the question because you'll pick up new ways of doing things of understanding things or it might just be a good review after you've done your killer.sh run the people that make killer.sh also makes killer coda and killacoda has a lot of example cka scenarios currently there are 12 of them just do all of them at least once this will really just fill out any gaps that the exam simulator or your studies might have missed so complete these questions as well next up i'm going to be talking a little bit about the testing environment again this was updated in june 2022 to be in a completely remote desktop environment there is a mock-up on the screen right now not a screenshot actually taken from the exam but i got it from this blog post you can check out that link down there they have some advice on the exam as well so at a high level the design is pretty straightforward on the top you have the psi browser things that you know are related to the proctoring of your environment left side you have the questions and on the right side you have your remote desktop so now i'll just go into some tips so check-in process this is a psi exam check-in process can be kind of a pain make sure you have your id and you can do a camera scan of your entire room make sure it's clean they get really picky about just having random things on your desk so be prepared for that previously you could have two monitors plugged in but right now they only allow you to have one so prepare accordingly so the check-in process can be a little stressful it's a little annoying when they reject your check-ins because you did one small thing wrong or you left like a water bottle on your desk but don't stress out too much just stay focused and keep your focus on the cka so specifics related to the new remote desktop environment it is an xfce desktop with firefox as the default browser and again with any remote desktop you can expect a little bit of lag but after the first couple minutes i found my lag to be bearable because the entire test environment is in a remote desktop you can have multiple terminals multiple browsers so as many tabs as you'd like as many browsers as you'd like this kind of eliminates the need for things like tmux if you don't already know it so in my case i had one terminal open to do my work i had one terminal to just take notes and vim and then on my browser i once have open with the kubernetes base docs and then i had one tab open with the complete one pager api reference which i'll talk about later last little note here if you use a different keyboard layout like i use dvorak over qwerty uh don't worry all that stuff gets transferred over just fine now you might think it's a little silly to talk about copy paste but if you've ever worked in a remote desktop environment you know that copy pasting can be a little bit wonky at times so here are a couple tips you can copy and paste with the right click menu so right click copy right click paste works fine you can also use ctrl shift c and v within the remote desktop to copy and paste and then the instructions let me scroll up on the left side there's a copy button on the uh the coup config switching and also copy buttons on any important piece of text so use those one-click copy buttons it'll save you from typos and keep you in the right context so you're interacting with the correct clusters small note here if you copy from firefox and paste into vim it'll trigger a warning saying this is an unsafe paste you can just click ok one weird thing i noticed was when i copy pasted from firefox into vim it would skip the first character for example with the yamo manifest typically the first line is api version it would just skip the a and i would have pi version and i have to fix that typo so keep an eye out for that not sure if it'll happen to you but if it does it's good to know in the xfce terminal some things are already set up for you which are kind of nice coupe cuddles are preconfigured with auto completion and alias decay so you don't need to worry about that some guides including the killer.sh tell you to memorize a couple of vim options such as shift with 2 expand tab true and tab stop 2. you don't need to these are preset in the terminal if for some reason you don't like vim vs code and webstorm are available i didn't use them but you can click the link to find out more and i kind of mentioned this before tmx is available but you don't need it if you don't know it because you can just open multiple terminals in the desktop anyways finally some miscellaneous recommendations just use the biggest possible screen you can it'll make everything more comfortable and you know having more comfort on the exam will probably probably have you do better on the exam itself um one thing is the psi browser has this big top bar and there's a double arrow pointing upwards on the right side on my screen it was red click that it'll like collapse the top bar a bit giving you a little bit more real estate to work with the questions and the remote environment and that is it for the testing environment so this is the last section of the guide the finesse part where i just teach you some functions some aliases ways of really speeding up your game because according to this mindset bullet point time is your most valuable resource and speed is your best friend so the faster you work the more time you'll have at the end to review questions or just go over things that were difficult and one of the key things to understand to move fast on the exam is to be imperative first and declare the second i know with kubernetes we tend to prefer crafting meticulous yaml manifest by hand and applying them but on the exam you want to prefer creating things with coop cuddle create or run over the typical coop cuddle apply there are some times where you'll still have to use apply but you want to start with kube cuddle create or run to generate those templates if you can so now that i told you how important coop cut will create and cube color run are let me just go into those commands a little bit more copying from yaml is a last resort if there is a resource that you can create using coupe code or create or coupe code or run you want to prefer that first if you need to expand and do something further from create or run you can use the dash dash dry run equals client output yaml and then pipe the output to a file to have the template to work from i've gone ahead and hopped on over to the terminal to show you what i mean so take for example the cka says to create a pod with two containers one busy box and one engine x we know to create a pod we gotta do cucuta run and we'll call it double for two pods and we have to start with an image i'll go ahead and start with busy box but in order to add the second container with the engine x image i'm gonna have to use this as a template so in order to do that we do dry run on the client side and then output yaml to get a template and then from there we can use that template as a base to add whatever we need so in our case we want to add another container one for uh nginx do the same thing here [Applause] and then once your template and then once you've made edits to your templates just like that you can do a cube cutter apply from a file and just like that you got your pod so now that i've shown you how easy it is to generate yaml templates from the kubecurl run command you can also do the same thing with create it's important to know exactly what you can create imperatively with the commands you might be tempted to memorize it i didn't a really good way of checking what exactly you can or can't do is using the dash h option so if i wanted to know what i could create with coupon upgrade i'm going to make this smaller because kukula outputs are gigantic it'll tell you exactly what available commands there are to create resources so everything here can be created using coop cuddle create so you want to prioritize using this over yaml template from the docs now it might be hard to memorize exactly what options need to be passed to every single resource type so again the h option comes in handy as it gets more and more detailed with your command for example if i wanted to create a deployment i could do create deploy but i forget exactly what needs to go into a deployment i can use the h option it gives you a couple examples as well as all the options available in the command so become best friends with cool clutter run and coop cuddle create because it'll help you so much on the exam you also want to make sure you have an absolutely solid understanding of the kubernetes documentation and structure and make sure to kind of mentally bookmark places you think you might need to come back to later for example i know that coupe cuddle create does not allow me to create something like a network policy so if i just search it i happen to know that there's a really good template near the top right here in addition to that i have a small trick to help you find example manifest for things you need so if you're looking for a persistent volume yemo manifest you can do ctrl f and then type in specifically k i n d colon space and the type of resource you want and that'll pretty much jump you straight to an example that you need so if i did kind persistent volume persistent volume claim also happens to match but it'll help define resources pretty quickly cool i kind of hinted at this part before but kubernetes api has a one-pager reference so if there's any option or key that you need more details on this is a great place to look instead of just scouring the documentation hoping you find the right key so take for example you need to find out what exactly goes into a pod spec you can click on pod v1 core pod spec and then every single key with description of its behavior is right here so again if you need something specific in the api the one pager api reference is really good you can find the one pager api reference by clicking this top level reference button and then this link to the one page api reference will give you exactly what you're looking for and in the spirit of saving time you want to make sure that you use short names and type less for example cm is the same thing as config map sts is stateful set deploy deployment pvc persistent volume claim you should try to remember the more common ones but if you ever forget them you can use the k api resources command to view them all apologies if this is a little small but the resources that have short names will have those short names listed in the second column of k api resources now last thing on this guide i'm going to be going over some aliases functions variables things that will help you just be faster on the exam so remember that dry run client output yaml thing that we're probably going to be typing a lot we can put that in a variable d o stands for dry output so if you set the do variable the do variable to the dry run client output yaml string instead of typing it out every single time you can do something like kubeco run nginx image nginx insert the dry output variable and just like that you have your yaml template next we got a function called mkcd which makes a directory and then cds into it this is useful for organizing your yaml manifests by question it's pretty easy to memorize mkcd is a function that makes a directory and then cds into that directory so if you happen to know that question 16 requires you to write a couple manifests mkcd question 16 and then you can create your manifest from there [Applause] yeah and because there are just so many questions and so many different clusters it really helps to stay organized by questions so mkcd will save you a little bit of time if you choose to remember it of course you can always just make the directory and then cd into it manually i just prefer to do it faster with makecd so that's it for the must-haves that i would recommend everyone to remember next i have a couple nice tabs at the bottom okay apply f is something that i typed a lot of so i aliased that to k a f caf and then coulda here is very similar just the destroy operation of the file so a really efficient way of working in my opinion is to start with your template from cuddle run or create using the dry output variable to create your template then from there make your edits then use kaf to apply your yaml manifest to the cluster now if you're familiar with kubernetes tools you might know that there's a tool called coop ctx and kubernetes you don't have these tools on the exam nor is are probably worth the time to set it up so a kind of quick and dirty way of doing it was i would export a variable nk um which just targets the coupe system namespace coupe system namespace so if i want to do k get pause but i didn't want to type in namespace cube tab system tab like this i could do a k get pod and then mk just like that same result similarly i just use the n variable to target whatever important namespace was in the question so i could type less as well again completely optional and up to you now the last thing that i'll share is how to delete pods quickly you can use grace period 0 with force to terminate pause immediately if you don't want to sit around waiting for pause to delete before you can create new things you really wouldn't want to do this anywhere else but the exam but because you want to move fast this might be helpful for you alright that is it for today's video hopefully you found this guide helpful if you have any more questions about the exam just drop in the comments i'll reply but if you do every single thing in this guide i have no doubt that you can pass the cka now before i go i do have one small request i haven't been uploading as much as i would have liked to which happens but if there's anything that you would like to see anything that interests you please drop it in the comments i would love to build the direction of this channel together with that said good luck have fun and let us know how you did

Channel: .ascode()

Views: 41,380

Keywords:

Id: 8VK9NJ3pObU

Length: 14min 34sec (874 seconds)

Published: Sun Jul 17 2022