Article reprinted from Docker
Program Overview
This technical solution is a continuous deployment (hereinafter referred to as CD) solution based on Kubernetes as the core, which can meet the development side of the program-level log viewing and analysis, the operation and maintenance side of the rapid scaling and day-to-day operation and maintenance analysis, and can ensure that the user's experience of the service. And the whole set can be placed on the resource utilization can be further improved, in the premise of not reducing the reliability of the service to reduce the cost of resource use.
Usage Scenario Analysis
This scenario applies to the continuous deployment process of the JavaWeb project with Tomcat as the container, and in the Kubernetes scenario, all the Node nodes are configured in a unified way, and the number of nodes is controlled according to the needs of the business environment.
Technical Architecture and Selection
Kubernetes cluster deployment mode: Stacked etcd topology
Kubernetes is installed as a highly available cluster using kubeadm, and Stacked etcd topology mode is selected.
For more information, see ).
Kibana
Kibana currently we are only using its discover node for log data querying, in terms of configuration.
Kibana configuration uses the "domain-*" method of configuration, every time you add a new domain name, you need to manually configure it here.
Kibana use discover to view, the default display of a domain under all the logs, you can filter through gy.wtype to choose to view the test environment or formal environment, or through gy.ltype which log type.
Container resource monitoring
Container resources are monitored using WeaveScope for resource consumption.
Benefits
Scan and add me on WeChat, note " Name + Company Position " to join Cloud Computing Learning Exchange Group , and like-minded friends **** the same punch card learning!
Recommended reading:
Click "good-looking" if you like it
.