Developers don't need to be K8s experts! ! !

There was an article before "Nonsense DevOps, we developers don't want to do operation and maintenance at all!" It resonated with many developers. Every developer hopes to abandon the operation and maintenance work and focus more on the code they develop. into stunning apps. However, things are not as expected. In the era of cloud native, the operation and maintenance work of developers does not seem to be reduced, but has become application deployment and management on K8s.

For operation and maintenance personnel, they only need to maintain the underlying K8s to greatly improve flexibility and convenience. However, K8s is still too complicated for us developers, and we still need to learn how to package images and K8s related knowledge. A lot of time is wasted on application deployment, do we really need to be K8s experts? I just want to deploy an application so complicated? Have you ever wondered if there is a platform or method that allows us to deploy your application and manage it easily without being a K8s expert or even knowing K8s?

actual problems

For us developers, we will always encounter the following different scenarios, which may be company-level problems or business-level problems. Maybe it is very simple to use the traditional deployment method now, but as the business grows, we have to migrate . In the face of these problems, we must also make our voices heard.

In a small company, there is no dedicated operation and maintenance. Programmers are required to write Dockerfile + YAML + Kustomize and then deploy it to k8s. In addition to the workload, it also faces the complexity of K8s itself. For multiple sets of businesses, Dockerfie, Yaml, CI, and CD scripts account for most of the workload. Is it okay not to write these?
The microservices in the company are becoming more and more complex. On the basis of writing code, you have to consider the communication, dependency and deployment issues between each service. After all, apart from our developers, the operation and maintenance personnel will not be more familiar with microservices than you complex dependencies between. Maybe Helm has already been tried, but writing a complete chart package is still so complicated, and you may also face format problems, incomplete configuration decoupling, and problems that cannot be deployed in another environment. Time to write all Yaml. Is it okay to copy the application directly without writing additional Helm Chart?
Within large enterprises, they are at the crossroads of migrating traditional applications to cloud environments. Faced with the needs of various clusters, the smooth migration of existing applications, and even how to reuse some public modules will become problems that we need to solve. Do not redevelop every time, can you accumulate existing applications or modules?

In these scenarios, we spend a lot of time on writing additional Dockerfile, Yaml, and Helm Chart. K8s is very good, but it does not solve the problems of our developers. Instead, it becomes more complicated for our developers to use K8s. Not to mention these additional files or scripts that need to be written, just mastering the knowledge of K8s requires a lot of time and effort. Are these problems really unavoidable? I don't think so. Let's learn about Rainbond, a cloud-native application management platform that does not require knowledge of K8s. Who said that you can manage your application well only after you become a K8s expert?

Why Rainbond?

Rainbond is an application management platform that does not require knowledge of K8s. There is no need to perform cumbersome operations on the server, nor do you need to have in-depth knowledge of K8s. Rainbond follows an "app-centric" design philosophy. Only your business modules and applications are here. Every business module can be deployed and run directly from your code warehouse, and you can manage the full life cycle of the application even if you are not a K8s expert. At the same time, using Rainbond's modular assembly capabilities, your business can be flexibly precipitated into independent application modules. These modules can be combined at will and assembled infinitely, and finally build a variety of application systems.

1. I don't understand K8s, can I deploy K8s?

OK! For many beginners or developers, if the company has already built a usable K8s platform, then this step will not be a problem to worry about. But for some independent developers, it is difficult to have such an environment, and Rainbond provides such a solution. On a Linux server, you only need to run a Docker container first, access the Rainbond console, and then enter the server IP address, you can quickly deploy a complete K8s cluster.

add_cluster

If this is still too complicated, you can try to use Rainbond's quick installation. It only takes a container and 5 minutes to start a platform with a K8s cluster for you, and the services you deploy on the platform will also be deployed to this cluster. middle.

2. Can I deploy applications if I don’t want to or can’t write Dockerfile, Yaml and other files?

able! Rainbond supports automatic identification of various development languages, no matter which development language you use, such as Java, Python, Golang, NodeJS, Dockerfile, Php, . It can identify and automatically package them into container images, and quickly deploy your business to the K8s cluster for efficient management. You no longer need to write any code-independent files. Just provide your code warehouse address.

source_code_build

3. How to assemble various business systems?

In Rainbond, different business programs can be quickly programmed through simple connections. If you need the front-end project to depend on the back-end, just turn on the orchestration mode and connect them to quickly establish dependencies and realize modular assembly. This brings great flexibility to your application architecture, and you can quickly build complex application systems without complex configurations and operations.

At the same time, if you have implemented a complete business program, it may contain multiple microservice modules, and you can also publish it to the local component library to achieve modular accumulation. It can be clicked and used directly in the next deployment, and can be assembled with your other applications after deployment. The ability to realize unlimited assembly combinations.

component_assembly

4. If you don't know K8s, can you manage deployed applications?

no problem! Rainbond provides application-oriented full lifecycle management and maintenance. You don't need to learn Kubectl commands or know the complex concepts in K8s. You can manage the batch startup, shutdown, construction, and Update, rollback and other key operations, and also supports automatic recovery when the application fails, and automatic scaling of the application. It also supports the configuration of applying http and tcp policies, as well as corresponding certificate management.

app_manage

how to use?

Execute the following command on the Linux terminal, and after 5 minutes, open the browser and enter http://<your IP>:7070 to visit the Rainbond page.

curl -o install.sh https://get.rainbond.com && bash ./install.sh

Then follow the quickstart to quickly deploy your first application.