< img height="1" width="1" style="display:none;" alt="" src="https://px.ads.linkedin.com/collect/?pid=3131724&fmt=gif" />
🚀 KubeSphere v4.1.2 with Enhancements and Bug Fixes is available now. Read the release notes for v4.1.2 → close
  • English
    • English
    • 简体中文
    1. 1.Create a KubeSphere Cloud account and log in to the platform.
    2. 2.In the upper-right corner, click Console, and then click Lite Cluster on the left.
    3. 3.Create a K8s cluster with KubeSphere installed.
    4. 4.Access KubeSphere with the default account and password (admin/P@88w0rd).
  •  Star
  1. Docs / 
  2. Documentation / 
  3. Extension User Guide / 
  4. Application Management for Cluster Federation / 
  5. Application Workloads / 
  6. Ingresses / 
  7. Edit Routing Rules

Documentation

Last updated:
    Edit

    Edit Routing Rules

    This section describes how to edit routing rules.

    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.

    Steps

    1. Log in to the KubeSphere web console with a user who has the Federated Project Management permission, and access your multi-cluster project.

    2. Click Application Workloads > Ingresses in the left navigation pane.

    3. Click more on the right side of the ingress you want to edit, then select Edit Routing Rules from the dropdown list.

    4. In the Edit Routing Rules dialog, set the routing rules, then click OK.

      • 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 pen on the right side to edit the routing rule settings.

      • Hover the cursor over a created routing rule, then click trash-light 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 trash-light on the right side of a created path to delete the path.

    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.

    Previous : Edit Ingress Information
    What’s on this Page