Next Steps

After Core and the required Aligned Extensions pass validation, complete the following post-install tasks according to your scenario.

PriorityTaskWhen to useContinue with
Recommended immediatelyPublish the Operators of ACP Common Aligned Extensions and the packages of ACP Common Agnostic Extensions.Publish them so that these Operators and cluster plugins can be installed when you need them.Publish the Common Extensions
Recommended immediatelyInstall the Product Docs plugin.Install this plugin so in-console help links can open product documentation.Install Product Docs Plugin
ConditionalCreate workload clusters or connect existing clusters.Use this path when your architecture requires workload clusters separate from the global cluster. To create workload clusters on Alauda OS, first upload and install the infrastructure provider for the target IaaS platform and the Cluster Bootstrap Provider on the global cluster, regardless of which IaaS platform the global cluster runs on.Clusters
ConditionalUpload and install other Extensions Packages.Use this path when you need platform capabilities that the Common Extensions do not provide.Extend
Recommended before broad user onboardingConfigure identity providers, users, roles, projects, and project membership.Use this path before onboarding administrators, project users, or application teams.Users and Roles and Projects
Recommended before application workloadsPrepare storage, networking, registry access, and workload prerequisites.Use this path before application teams deploy workloads.Storage, Networking, Registry, and Workload Clusters
Recommended before production operationReview backup, upgrade, monitoring, and operational documentation.Use this path before operating the platform for production workloads.Backup, Upgrade, and Observability

These tasks do not all apply to every installation. Follow the paths that match your deployment architecture and operational requirements.

Publish the Common Extensions

The installation pushes the images of all packages in plugins/ and publishes the cluster plugins of ACP Common Aligned Extensions, but it does not publish their Operators. Until you publish them, these Operators cannot be installed from the Web Console or with YAML. The packages of ACP Common Agnostic Extensions are not uploaded during the installation.

You can publish both sets at any time; publishing them right after the installation is recommended. Run the commands with Violet v4.2.13 or later on a machine that can reach ACP and its image registry and has the plugins/ directory of the extracted Core Package. For the addresses and credentials, see Addresses and Credentials.

Publish the Operators of ACP Common Aligned Extensions

The images are already in the registry. With --skip-push, Violet only creates the resources that publish the packages and pushes no images, so --dest-repo is not needed. Set <plugins-dir> to the plugins/ directory of the extracted Core Package.

read -rsp "Platform token: " PLATFORM_TOKEN; printf '\n'
violet push <plugins-dir> --platform-address "https://<platform-address>" --platform-token "${PLATFORM_TOKEN}" --skip-push

Publish ACP Common Agnostic Extensions

Place the downloaded packages of ACP Common Agnostic Extensions in one directory and push the directory. Set <registry-address> to the address of the external registry that you prepared for the installation, and use a registry account that can push. If the registry needs no credentials, use --no-auth instead of the registry credentials.

REGISTRY_ADDRESS="<registry-address>"
REGISTRY_USERNAME="<registry-username>"
read -rsp "Registry password: " REGISTRY_PASSWORD; printf '\n'
violet push <agnostic-packages-dir> --platform-address "https://<platform-address>" --platform-token "${PLATFORM_TOKEN}" \
  --dest-repo "${REGISTRY_ADDRESS}" --username "${REGISTRY_USERNAME}" --password "${REGISTRY_PASSWORD}"
unset PLATFORM_TOKEN REGISTRY_PASSWORD

Publish to the Standby global Cluster

Only in a Global Cluster Disaster Recovery environment. Repeat the two steps against the standby global cluster: set --platform-address to its VIP, use an API token created in its Web Console, and set --dest-repo to its registry. Otherwise, the packages go to the primary global cluster. For how to set these values on Alauda OS, see Install etcd-sync.

read -rsp "Standby platform token: " STANDBY_TOKEN; printf '\n'
read -rsp "Standby registry password: " STANDBY_REGISTRY_PASSWORD; printf '\n'
violet push <plugins-dir> --platform-address "https://<standby-vip>" --platform-token "${STANDBY_TOKEN}" --skip-push
violet push <agnostic-packages-dir> --platform-address "https://<standby-vip>" --platform-token "${STANDBY_TOKEN}" \
  --dest-repo "<registry-address>" --username "<registry-username>" --password "${STANDBY_REGISTRY_PASSWORD}"
unset STANDBY_TOKEN STANDBY_REGISTRY_PASSWORD

Verify the Result

In Administrator, open Marketplace > OperatorHub and select the global cluster. The Operators of both Common Extensions are listed and can be installed. In a DR environment, check the standby global cluster in its own Web Console as well.

If violet push fails, see Troubleshooting.

Install Product Docs Plugin

The Product Docs plugin provides access to product documentation within the platform. All help links throughout the platform direct users to this documentation. If this plugin is not installed, clicking help links in the platform results in 404 access errors.

Open Cluster Plugins

Navigate to Administrator. In the left sidebar, click Marketplace > Cluster Plugins and select the global cluster.

Install the Plugin

Locate the Product Docs plugin and click Install.