Create Ingresses
This section describes how to create an Ingress.
Prerequisites
Application Management for Cluster Federation should have been installed and enabled.
You should join a multi-cluster project and have the Federated Project Management permission within the project.
To create an ingress that supports the HTTPS protocol, you need to create a secret of type TLS Information, which must contain the Base64-encoded certificate and private key. For more information, see Create a Secret.
There must be at least one service in the project to which the ingress belongs. For more information, see Create a Stateful or Stateless Service.
Steps
Log in to the KubeSphere web console with a user who has the Federated Project Management permission, and access your multi-cluster project.
Click Application Workloads > Ingresses in the left navigation pane.
Click Create on the page.
On the Basic Information tab, set the basic information for the Ingress, then click Next.
Parameter Description Name
The name of the Ingress. The name can only contain lowercase letters, numbers, and hyphens (-), must start and end with a lowercase letter or number, and can be up to 253 characters long.
Alias
The alias of the Ingress. Different Ingresses can have the same alias. The alias can only contain Chinese characters, letters, numbers, and hyphens (-), cannot start or end with a hyphen (-), and can be up to 63 characters long.
Description
The description of the Ingress. The description can contain any characters and can be up to 256 characters long.
On the Routing Rules tab, click Add Routing Rule, set the routing rule parameters, then click Next.
Click Add Routing Rule to set routing rules. You can set multiple routing rules, each corresponding to a domain name.
Hover the cursor over a created routing rule, then click on the right side to edit the routing rule settings.
Hover the cursor over a created routing rule, then click on the right side to delete the routing rule.
Parameter Description Domain
The user-defined domain name.
Protocol
The protocol supported by the Ingress. The value can be HTTP or HTTPS.
Secret
The Secret used to provide the certificate and key when the Ingress protocol is HTTPS. This Secret must contain the tls.cert and tls.key fields, which store the Base64-encoded certificate and private key, respectively.
Path
The domain path and its mapping relationship with the service port.
Click Add to set multiple paths.
Click on the right side of a created path to delete the path.
On the Advanced Settings tab, set labels and annotations for the Ingress, then click Create.
Click Add to set multiple labels or annotations.
Click on the right side of a created label or annotation to delete it.
Note The cluster gateway and project gateway in KubeSphere are implemented based on Nginx Ingress Controller. You can set annotations on the Ingress to control the behavior of the gateway. For more information, see Nginx Ingress Controller Documentation.
After the Ingress is created, it will be displayed in the Ingress list.
Feedback
Was this page Helpful?
Receive the latest news, articles and updates from KubeSphere
Thanks for the feedback. If you have a specific question about how to use KubeSphere, ask it on Slack. Open an issue in the GitHub repo if you want to report a problem or suggest an improvement.