# 5.0 Introduction to Multicloud Management capabilities In the past two years, with the maturity of public cloud services and the differentiation of cloud provider products, many enterprises have begun to adopt hybrid IT and multicloud solutions in order to improve efficiency and maintain competitive advantages in the digital transformation team, thus Accelerate the pace of your multicloud policy. Distributed applications and workloads that were previously centralized in on-premises data centers are redefining traditional data center boundaries and forcing application modernization and infrastructure expansion to accommodate increasingly distributed workloads. Relying on a combination of private clouds, multiple public clouds, and traditional infrastructure platforms, businesses are free to choose a cloud based on their specific strengths, benefiting from the specific strengths of each cloud provider. In this way, build the most suitable application architecture for the enterprise, so as to ensure high service availability, enhance application elasticity, and increase load capacity. Of course, enterprises can also reduce the risk of downtime of a single cloud provider by building redundant deployments to achieve rapid failover. ![Multicloud capabilities](https://docs.daocloud.io/daocloud-docs-images/docs/blogs/images/kairship04.png) In the face of complex multicloud environments, 5.0 Multicloud Management will bring us consistent cluster operation and maintenance, reduce management burden; cross-cluster application distribution capabilities, break data islands, and realize application cross-cluster level disaster recovery deployment. ## Features The main features of Multicloud Management are as follows: **Multicloud cluster instance management** - One-click deployment of multicloud cluster instances, quickly deploy enterprise-level Karmada clusters through the web interface, support the creation of multiple Karmada instances, and they work at the same time, and the instances are not aware of or affect each other. - One-click import of worker clusters, which supports one-click import of clusters from Kpanda's existing managed clusters to Karmada instances, and real-time synchronization of the latest information of Kpanda clusters. - An overview of the instance information, which supports viewing the CPU and memory usage of the connected worker clusters in the instance. - worker cluster management, which supports dynamic addition of new clusters to Karmada instances; support for dynamic removal of specific clusters from Karmada. - CloudShell, which supports obtaining KubeConfig link information, and users can manage Karmada instances on the local terminal. - Karmada native API support, supports all Karmada native APIs. **Multicloud workloads** - Supports interface-based creation of deployments, adding override configurations and distribution policies - Support viewing the deployment details of deployments, single Pod monitoring, and log information - Application failover, built-in application multicloud failover capability - Cross-cluster workload distribution, rich multicloud application distribution policy and coverage policy - Observability, rich auditing, Metrics exposure **Resource Management** - Support multicloud namespace management - Support multicloud storage statement management - Support multicloud configuration, key management - Support multicloud Service and Ingress resource management **Policy Center** Support propagation policy and override policy management, view the workload associated with the policy, and provide the feature of deleting idle propagation policies and override policies. ## Graphical user interaction The Multicloud Management module is an aggregation platform for multicluster management, which supports users to access clusters from different vendors and regions for unified management. Help enterprises quickly deploy workloads across clusters, and meet Cases such as cross-cluster management and disaster recovery deployment. In terms of hierarchical structure, a two-level architecture is adopted. The top layer extracts the list of multicloud clusters. Select to enter the multicloud cluster management center to view overview, worker cluster management, multicloud workload, resource management, and policy center. On the multicloud cluster instance list interface, users can clearly perceive real-time information such as the running status, resource usage, and number of clusters of each multicloud cluster instance. And can enter details based on multicloud cluster instance name. At the same time, if users want to use kubectl to manage the cluster, they can also use the CloudTTY desktop console tool on the interface. On the __Overview__ interface, users can view detailed cluster overview information, health status of cross-cluster workloads, and resource information. On the __worker cluster management__ interface, users can manage the access clusters of multicloud clusters, and can view information such as the status and release version of each cluster. On the __multicloud Workload__ interface, users can perceive information such as workload status and number of instances under the current multicloud cluster with permissions. And you can enter the workload details by name, and view logs, monitor. In the __Resource Management__ interface, users can manage services and routes, namespaces, storage declarations, configuration and key modules. These resources are created across clusters to satisfy the resources that the deployment of cross-cluster workloads depends on. In __Policy Center__ , users can view the propagation policies and override policies associated with workloads, but they are not allowed to delete the policies in use. In addition, users can also customize and create propagation policies and override policies to unlock advanced usage modes. ## What can Multicloud Management do You can manage Multicloud Management through the Web UI. You can use the Multicloud Management module to implement functional operations such as creating multicloud cluster instances, accessing clusters, and deploying applications across clusters. Among them, the capability of multicloud workloads is fully aligned with Kubernetes workloads. **Create a multicloud cluster** In the Multicloud Management module, users can create a multicloud cluster instance with one click, and then access and remove the worker cluster on the details page after the instance is successfully created. At the same time, the expulsion of workload can be achieved by marking the worker cluster with stains. **Access member cluster** The Multicloud Management will synchronize all the clusters that have been connected to the container management module. The user only needs to click the "Connect to Cluster" button at the worker cluster of the multicloud cluster instance, select the cluster to be connected, and click "OK" to complete access operation. **Deploy multicloud workloads** The Multicloud Management module supports Kubernetes-native workload type deployment and management capabilities, including: creation, configuration, expansion, deletion, and other full lifecycle management. In addition, it supports override configuration of clusters, allowing users to easily handle the configuration management of different clusters. - **Instance Scheduling Policy** Currently, Multicloud Management supports the deployment of instances to the cluster selected by the user in the form of replication, that is, the number of instances is configured as 2, and two worker clusters, Cluster A and Cluster B, are selected. A workload with 2 instances is deployed on B at the same time. More instance scheduling policies will be gradually supported in the future. - **Cluster affinity and anti-affinity** Users can select clusters by region and availability zone, or by configuring affinity and anti-affinity to achieve more refined cluster selection. - **Override configuration** Users can select clusters that require override configurations, and then see the general configurations that have been configured in the previous steps, and modify the configurations in the differential steps so that workloads on different clusters run with different configurations. - **Resource Management** When creating cross-cluster workloads, configuration differences between clusters are inevitable. Therefore, we can create configurations, keys, and storage statements in the resource management module, so that when creating workloads, we can quickly read and perform override configurations. The resource management module also manages namespaces, services and ingress, and these resources will be created across clusters. - **Policy Center** In the policy center, users can manage propagation policies and override policies created through workload association, and provide the feature of deleting idle policies. It also supports maintaining, creating and editing propagation policies and differentiation policies in YAML. ## Frequently Asked Questions - **Q: Which vendors' clusters are compatible with Multicloud Management?** A: The 5.0 Multicloud Management is compatible with the vendor clusters supported by the 5.0 container management, including AWS, Google Cloud, Xinchuang architecture, edge-cloud integration, and any standard Kubeneters ApiServer-based distribution container cluster. - **Q: How to realize the management of clusters of other manufacturers?** Answer: By obtaining the KubeConfig file of other vendors' clusters, performing the cluster access operation in the container management module, and filling in the KubeConfig file of the target cluster, the access management of a container cluster in Container Management is completed. Then, in the Multicloud Management module, you can access the cluster newly added to the container management module in the worker cluster list of the multicloud cluster instance. ![Manage KubeConfig](https://docs.daocloud.io/daocloud-docs-images/docs/blogs/images/kairship01.png) - **Q: How does the application implement cross-cluster communication?** A: Currently, the Multicloud Management module does not have a built-in implementation of cross-cluster communication between applications. We can integrate Submariner to flatten the network between connected clusters and achieve IP reachability of pods and services between clusters. Submariner also provides cross-cluster service discovery capabilities through Lighthouse. - **Q: How to obtain the real-time status of multicluster resources?** Answer: With the help of the self-developed open source component ClusterPedia, by installing the Agent component on the target cluster, combined with the Watch mechanism, the resource change information of the target cluster can be synchronized to the ETCD of the container management cluster in real time. Multicloud Management directly queries container-managed ETCD to obtain real-time status of multicluster resources. ![Get cluster resource status](https://docs.daocloud.io/daocloud-docs-images/docs/blogs/images/kairship02.png) - **Q: What is the positioning of 5.0 Multicloud Management in the fifth generation of products?** Answer: In the fifth-generation product, the Multicloud Management module is at the core of connecting the past and the future. Right: docking with the DCE 5.0 Workbench. For the upper-level scenario-based management module, the Multicloud Management module can expose any standard Kubernetes API, and easily realize cross-cluster application distribution and disaster recovery deployment. For the next: docking container management platform Kpanda, and Kpanda docking Any Kubernetes, such as edge K3S, Xinchuang environment, DCE, DKG, DKE, and external Openshift, Tanzu, abd CCE, Multicloud Management based on container management module, quick implementation Multicluster management. ![Positioning](https://docs.daocloud.io/daocloud-docs-images/docs/blogs/images/kairship03.png) - **Q: Who can create a multicloud cluster?** A: Users with Global Admin and Kairship Owner roles can create multicloud clusters. [Learn about Multicloud Management](../kairship/intro/index.md){ .md-button } [Download DCE 5.0](../download/index.md){ .md-button .md-button--primary } [Install DCE 5.0](../install/index.md){ .md-button .md-button--primary } [Free Trial](../dce/license0.md){ .md-button .md-button--primary }