Skip to content

Multicloud Ingress

Multicloud Ingress is a unified abstraction of the standard Kubernetes Ingress multicloud. By creating an Ingress and associating it with several multicloud services, it can be distributed to multiple clusters at the same time.

Currently, two creation methods are provided: form creation and YAML creation. This article takes form creation as an example. You can follow the steps below.

  1. After entering a multicloud instance, in the left navigation bar, click Resource Management -> Multicloud Ingress , and click the Create Multicloud Ingress button in the upper right corner.

    Ingress List

  2. On the Create Ingress page, after configuring the deployment location, setting ingress rules, Ingress Class, and whether to enable session affinity, etc., click OK . For details, please refer to Create Ingress.

    Create Ingress

  3. It supports one-click conversion of sub-cluster services to multicloud ingress. Click Convert Now on the list page, select the ingress under the specified worker cluster and namespace, and click OK to convert successfully.

    Convert Now

  4. Click ┇ on the right side of the list to update and delete the ingress.

    Update/Delete

    Note

    If an ingress is deleted, the service-related information will also disappear, so please proceed with caution.

YAML example

Here is an example YAML for multicloud ingress that you can use with a little modification.

kind: Ingress
apiVersion: networking.k8s.io/v1
metadata:
  name: ingress-test
  namespace: default
  uid: 49a45f23-2e5a-4a23-9f21-77418c1b9bbb
  resourceVersion: '1979660'
  generation: 1
  creationTimestamp: '2023-04-27T00:07:43Z'
  labels:
    propagationpolicy.karmada.io/name: ingress-ingress-test-ygddx
    propagationpolicy.karmada.io/namespace: default
  annotations:
    shadow.clusterpedia.io/cluster-name: k-kairship-jxy
spec:
  rules:
    - host: testing.daocloud.io
      http:
        paths:
          - path: /
            pathType: Prefix
            backend:
              service:
                name: test-service
                port:
                  number: 123
status:
  loadBalancer: {}

Comments