Over the past year or so, we've taken a deep dive into container orchestration tools and guided teams to build and publish cloud native GitLab helm charts that can be deployed on kubernetes. For friends who are considering getting started with Kubernetes, we have the following 6 suggestions:
View documents, online courses and presentations online
Don't do it behind closed doors, go to the online documentation and video demos, which are all good channels for us to quickly get familiar with and understand Kubernetes. In fact, we do not need to attend a whole set of courses in order to use K8s, but for some technical details, professional explanations and experience sharing are undoubtedly very helpful.
Of course, the best way to apply what you have learned is the actual test drill. There are many PaaS platforms or Kubernetes tools that have free resources or free trial periods. We can build and deploy a small cluster on it, try, configure, change... ...just play!
Find out why Kubernetes
One of the biggest challenges with using Kubernetes is figuring out what we're going to do - as a test round, a staging environment, or for production?
It is not complicated to use it only in the development environment, just need to understand some basic concepts, such as namespace, and understand what is secret, what is configuration, what is deployment, etc. These concepts will be used throughout our use process.
Going a step further on Kubernetes, we need to understand something that didn't exist before, like role-based access control, RBAC, and more. These capabilities weren't available a year ago, but are becoming more important now, and are great for different roles throughout the process, making sure that what's being done doesn't affect other things that shouldn't be touched.
For example, we can now have fine-grained control through RBAC, setting up multiple namespaces, and each namespace controls access or creation of secrets and configuration. In this way, we have a production-grade multi-tenant cluster, and we don't have to worry about tenants interacting and interfering with each other before.
The Kubenretes versions of service providers are not necessarily the same
Many people will choose to use Kubernetes services provided by service providers. It should be noted here that the versions of Kubenrets provided by service providers are often inconsistent. In general, they will be close, but some functions are implemented slightly differently. Perhaps the basic versions are similar, and the difference will exist in the advanced support provided by the service provider when integrating with its own product.
In addition, it should be noted that some service providers do not support us to "do it yourself", and we cannot use our own plug-ins and components with the products and services provided by the service providers.
Do not blindly use new features
In the year since we first learned about Kubernetes, its capabilities have expanded a lot. For new changes, if you rashly use them without a full understanding, it may be counterproductive. We spend some time reading and thinking about whether it is really useful or how to use it. After all, seeing others do it does not mean that it is the best in the industry. best practice.
Update the version frequently
Kubernetes is a production-ready system, but it's not a software that releases a new version every six months, with new features and functionality being added every day. So if we install Kubernetes, don't update it for a year, and then consider finding an LTS, it's actually too late. Our advice is to check Kubernetes for new features and features once a month to make sure we're not "out of date".
One last bit of advice (advertising)
A series of conceptual abstractions proposed by Kubernetes are very consistent with an ideal distributed scheduling system. However, a large number of difficult technical concepts have also formed a steep learning curve, which directly raises the threshold for the use of Kubernetes.
Rainbond, an open source PaaS of Nimbus Cloud, packages these technical concepts into "Production-Ready" applications, which can be used as a Kubernetes panel that developers can use without special learning.
In addition, Kubernetes itself is a container orchestration tool and does not provide management processes, while Rainbond provides ready-made management processes, including DevOps, automated operation and maintenance, microservice architecture and application market, etc., which can be used out of the box.
Learn more: https://www.goodrain.com/scene/k8s-docker
Original: https://about.gitlab.com/2018/04/16/five-things-i-wish-i-knew-about-kubernetes/