FAQ
This topic answers frequently asked questions about AppStack.
Kubernetes clusters
Does a resource pool have to be a Kubernetes cluster?
AppStack currently supports only cloud-native scenarios. This includes Alibaba Cloud Container Service for Kubernetes (ACK) clusters, Kubernetes clusters from other cloud providers, and self-managed Kubernetes clusters.
Why does an image pull fail during deployment?
Check if the required imagePullSecret for the image repository is configured on the Kubernetes cluster.
For ACK clusters, see: https://www.alibabacloud.com/help/en/container-service-for-kubernetes/latest/use-an-imagepullsecret-to-pull-images-from-a-private-image-repository
For self-managed clusters, see: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/
AppStack vs. Apsara DevOps Flow
AppStack and Apsara DevOps Flow are both products in the Apsara DevOps suite. Apsara DevOps Flow focuses only on deployment and lacks concepts such as applications, environments, and resource pools. AppStack complements and extends the continuous deployment (CD) capabilities of Apsara DevOps Flow. While Apsara DevOps Flow only defines task workflows, which makes it difficult to standardize them. In contrast, AppStack uses the 'application' concept to group pipelines, environments, and resources, which standardizes the R&D management process.
Using AppStack with external Kubernetes clusters
Yes. As long as the API server of your Kubernetes cluster is accessible from the public internet, you can add the cluster to AppStack with its kubeconfig credential.
AppStack and KubeVela
AppStack uses KubeVela to provide enhanced deployment capabilities based on the Open Application Model (OAM) and contributes to the KubeVela project.