Application Deployment and Management
Overview
Applications deployed in AppEngine(K8s), in addition to Docker image-related information, also include the following configuration information:
- Resource limit (memory)
- Number of instances
- Environment variables
- External domain names and certificates
How to access
After an application is deployed, an internal domain name is automatically assigned in the form of<app-name>.<namespace>.svc.cluster.local. Other applications deployed to AppEngine V2 can access this application through this domain name and support TCP and UDP protocols. If you are deploying a stateful application, each instance will have its own internal domain name in addition to the unified internal access domain name, in the form of...
If you need to access from the outside, HTTP/HTTPS or TCP/UDP form can be chosen. HTTP/HTTPS must specify the domain name for the application. If you use https, you must also configure the secret certificate. The TCP/UDP form needs to select the ports to be exposed; each company has a certain port range, and one port can only be used by one application. For TCP/UDP server IP, please contact Eco Cloud team to obtain it.
Create an application
- Application type: stateless and stateful. Each instance of stateful applications has its own network identification and can communicate with each other. A single instance of stateless applications does not have its own network identification and cannot communicate with each other.
- Application name: only lowercase letters and numbers are allowed, and the connector (-) can only begin with a lowercase letter and is not longer than 253
- Docker image: the docker image address of the application, which can be any address that can be accessed by the AppEngine. Considering the download speed, it is recommended to use the mirror repository provided by Eco Cloud to store images. Contact the Eco Cloud Administrator to open it.
- Docker repository Secrets: if the mirror repository needs logging in, specify the credential information here (created in Secrets management)
- Start command: specifies the start command as a JSON array if needed. It is recommended to specify directly in the Dockerfile
ENTRYPOINTOrCMD - Start command parameters: specifies the parameters of the start command as a JSON array if needed
- Number of instances: specifies the number of instances to start (integer greater than or equal to 1)
- Memory limit: the range is [64,4096] in Mb
- Internal access to domain names: automatically generated based on application name and Namespace
- Service: the protocol of the service provided by the application (TCP or UDP), the service port and the container port. The service port can be arbitrarily specified (80 is recommended for HTTP service). The container port is the port exposed by the Docker image
- External service type: if you provide an external HTTP service, you need to link the URL. If you provide external TCP/UDP service, you need to select the port
- Whether to allow only HTTPS: if yes, HTTP requests will be automatically redirected to HTTPS
- URLs: URLs (domain names and paths) that provide external access; multiple URLs can be linked. If you only allow HTTPS, you must specify the TLS certificate (created in Secrets Management)
- Environment variable: the environment variable used by the application runtime can be directly assigned a value, or can be referred to in the ConfigMap item created in "Configuration Management"
About disk quota
At present, AppEngine(K8s) does not limit the disk size, but do not store persistent files locally. You need to use back-end storage services such as FDS; the logs must be written to standard output or standard error output (stdout/stderr).
We monitor the usage of the disk, and for applications that take up too much (>5G) disk space, a reboot will be forced after one notification.
Application details
Start or stop application
In the upper right corner of the "Application details" page, there is a start/stop button to start or stop the application. It should be noted that after the application is stopped and started again, the number of instances will become 1
Manual expansion
After manually modifying the number of instances, it takes a certain time to start or terminate the instance. Therefore, the instance information on the "Instance list" takes some time before it is synchronized to the set number of instances
List of events
Lists at the bottom of "Application Details" the 100 most recent events in reverse order of occurrence
Update application
Updates the application to modify information other than the application name, Namespace, and instance number.
Grayscale upgrade
Grayscale upgrade is a way to smoothly upgrade external service application. The general process is as follows:
Apply online, link the official domain name, and provide external services
Deploy new applications, link test domain names for testing
After passing the test, the official domain name is removed from the legacy application and linked to the new application
Stop or delete old applications