KubeAcademy by VMware
Top Takeaways
Next Lesson

Join 80,000+ fellow learners

Get hands-on practice with Kubernetes, track your progress, and more with a free KubeAcademy account.

Log In / Register

To wrap the course up, we’ll spend a few minutes reviewing the key takeaways from the course.

Boskey Savla

Senior Technical Marketing Architect at VMWare

Boskey Savla is Technical Marketing Manager @VMware focusing on Cloud Native Applications, she has 15 years of experience in systems and operations.

View Profile

Now, finally, welcome to the key takeaways lesson. So we have covered a lot of things. And what I want to really do is quickly summarize what we have learned so far in this entire chapter. To start off with, Kubernetes is... The reason why Kubernetes is so popular is because it understands how to talk to different infrastructures. And the way it does is it talks to different infrastructures via plugin models, and it has a plugin for each type, which is network, compute, and storage.

And depending upon the infrastructure that you're deploying on, you can select these individual components. It is ideal to have components that give you wide variety of functions. One key aspect to defining what plugins you use is networking. Networking is the basis of how microservices are built and consumed within Kubernetes or the resources. And so, you want to have a CNI that is capable of doing what you want it to do, all the way from layer two to layer seven, to creating network policies, a BGP routing, et cetera. So keep that in mind.

When it comes to storage, persistent volumes are a way for defining... A way of binding persistent volumes to your pods. By default, the nature of all pods is to create FML storage. So if you want data to persist, you will have to create persistent volumes for them to take advantage of that. There are different kinds of persistent volumes that you could create based on the backend storage that you have. And the way you define what storage policy you have is a storage class.

Again, when it comes to the Kubernetes API, it is pretty powerful. Security is a key concern, so make sure that when you're building the stack, you're thinking about security all the way from your infrastructure, who has access to the Kubernetes nodes, to the Kubernetes cluster itself, and the containers running within the cluster. And also, it is very important to secure that Kubernetes API. So make sure that you using [inaudible 00:02:14] plus identity to have users granted that particular API so they can only require the users have access to that.

Please take advantage of the role-based access control within Kubernetes so that you can define what users have, what level of access, and not everybody has [inaudible 00:02:34] route or system level accesses. So that's all in conclusion for this particular topic. I hope you enjoyed this lesson. Thank you so much.

Give Feedback

Help us improve by sharing your thoughts.

Share