The examples in WordPress with Single Pod show how to quickly create WordPress services. The WordPress services created in this way have the following features:
- The data is written to the mySQL database running on the same container.
- Services can be quickly launched.
- Databases and storage-type files will be lost if the container is stopped for certain reason.
Using MySQL databases can ensure the permanent storage of data. The databases will continue to run when the pod/container restarts. This document explains how to configure MySQL database using TencentDB and how to create a WordPress service that using TencentDB.
Creating WordPress Service
- Log in to the TencentDB MySQL console, and click Create in the database instance list. See the figure below:
- Select the configuration to purchase. For details, see TencentDB MySQL.
The region of the database must be the same as that of the cluster, otherwise you will not be able to connect to the database.
- After successfully creating the database, you can view it in MySQL instance list.
- Initialize the database. For details, see [Initializing MySQL database].
Creating a WordPress Service that Using Tencent DB
- Log in to the TKE console.
- In the left sidebar, click Clusters to go to the Deployment page and select Create. See the figure below:
- Set up the workload basic information on the Create Workload page according to the following instructions. See the figure below:
- Workload Name: The name of the workload to be created. Here,
wordpress is used as an example.
- Description: Fill in the related workload information.
- Tag: Key = value. This is a key value pair, and the tag in this example is set by default as k8s-app = wordpress.
- Namespace: To be selected based on your requirements.
- Type: To be selected based on your requirements.
- Volume: Set up the workload volumes mounted based on your requirements. For more details, see Volume Management.
- Set up Containers in Pod according to the following instructions. See the figure below:
- Name: Enter the custom container name. Here,
test is used as an example.
- Image: Enter
- Image Tag: Enter
- Environment variable: Enter the following configuration information in sequence.
WORDPRESS_DB_HOST = Private IP for cloud database MySQL
WORDPRESS_DB_PASSWORD = Password entered during initialization
Keep default settings for other options.
- Set up the service’s pod number according to the following instructions. See the figure below:
- Manual adjustment: Set the number of pods. The number of pods in this example is set as 1. You can click + or - to change the number of pods.
- Auto adjustment: Automatically adjust the number of pods if any of the setting conditions are met. For more details, see Auto Scaling.
- Configure the workload Access settings (service) according to the following instructions. See the figure below:
- Service: Check Enable.
- Service Access: Select Via Internet.
- Load balancer: Select according to your requirements.
- Port mapping: Select TCP protocol, and set both the container port and service port to 80.
The security group of the service’s cluster must open the node network and container network to the Internet. It is also required to open ports 30000 to 32768 to the Internet. Otherwise TKE service may be unavailable. For more details, see TKE Security Group Settings.
- Click Create workload to complete the creation of the
Accessing WordPress Service
WordPress service can be accessed using the following two methods.
Accessing WordPress Service Through Cloud Load Balancer IP
- In the left sidebar, click Clusters to go to the Cluster Management page.
- Click on the WordPress service’s cluster ID and select Service > Service.
- Enter the service management page and copy the WordPress service’s cloud load balancer IP. See the figure below:
- Enter the cloud load balancer IP in the browser’s address bar and press Enter to be able to access the service.
Accessing Service Using Service Name
Other services or containers in the cluster can be accessed directly by the service name.
Verifying WordPress Service
When the service is successfully created, you can directly enter the WordPress server configuration page when accessing the service. See the figure below:
More WordPress Settings
If creation of the container failed, you can read the Event FAQs.