FAQ

• How do I get a Git personal access token?
• How do I initialize a public cloud service cluster?
• Cannot find the BWAF package
• Does each application in BizWorks require a separate database?
• What are the use cases for the business capability feature?
• Failed to connect to a cluster

How to get a Git personal access token

1. Log in to your GitLab repository.
2. In the top navigation bar, click your user avatar > Edit profile.
3. On the User Settings page, click Access Tokens.
4. On the Access Tokens page, perform the following steps:
   1. Enter a Token name.
   2. In the Select scopes section, select api and read_user.
   3. Click Create personal access token.

How to initialize a public cloud service cluster

Background information

BizWorks uses a semi-managed model, which means you provide the container cluster that runs your applications. When you onboard your cluster to BizWorks, you must initialize some components to ensure your applications run correctly. The components that require initialization include:

• KubeVela: This component is an implementation of the Open Application Model (OAM) and is used to deploy your applications. You must install this component if you use a K8s cluster. Do not install this component if you use an EDAS cluster.
• metricbeat: This component enables pod monitoring features, such as CPU and memory usage. If this component is not installed, you cannot view pod monitoring information.
• log-pilot: This component collects application runtime logs and sends them to Kafka for business capability trace analysis. If this component is not installed, the operations platform feature is unavailable because it receives no data.
• api gateway: This component routes calls to middle platform business capabilities. If this component is not installed, the endpoint returned after application deployment cannot be called.

Configuration details

This section describes each component and explains how its initialization affects the overall cluster initialization status.

• KubeVela: This component has no external dependencies and can be installed with the default parameters. If its initialization fails for any reason, the entire cluster initialization fails.
• metricbeat: This component depends on an Elasticsearch (ES) service that BizWorks provides directly.

  If the ES address is configured incorrectly, metricbeat fails to start, which causes the cluster initialization to fail.

• log-pilot: This component depends on Kafka and requires the Kafka instance provided by BizWorks. Accessing the public cloud Kafka instance across a VPC requires SSL configuration. This feature is not currently supported, but you can proceed with the default settings. Even if the Kafka address is incorrect, log-pilot can still start and does not affect the overall cluster initialization. However, logs will not be collected, and the operations features will be unavailable. If you need to use the operations features, contact the BizWorks operations team to manually configure log-pilot.

  If log-pilot initialization fails, it does not cause the entire cluster initialization to fail.

• api gateway: This component depends on Redis and the BizWorks console. You must purchase a Redis instance and add the cluster's IP address to the Redis whitelist. Configure the following parameters:
  • redis-host: The endpoint of the Redis instance you purchased.
  • redis-port: The port of the Redis instance you purchased.
  • redis-password: The password for your Redis instance.
  • pop-loadPrivate: false.
  • pop-endpoint: The address of the BizWorks console: bizworks.aliyun.com.
  • storageClass: The PersistentVolumeClaim (PVC) storage controller, such as alicloud-disk-ssd.

  If the api gateway fails to initialize, the entire cluster initialization fails.

Ensure the cluster has inbound and outbound public network access

Your cluster must have both inbound and outbound access to the public internet. Otherwise, the public cloud service cluster initialization fails. Outbound access is required to pull BizWorks images. Inbound access is required to allow BizWorks to manage and access the cluster.

• For information about how to configure public internet access for your cluster, see Use the SNAT feature of a public NAT gateway to access the internet.
• For information about how to allow public internet access to your cluster, see Associate an EIP with and manage a private CLB instance.

Cannot find the BWAF package

See Obtain the BWAF SDK.

Database requirements for applications

No. Each application is a microservice. As a best practice, each microservice should have its own database. For example, the trading service would have one database and the product service would have another. However, BizWorks does not enforce this, and you can configure multiple applications to share a single database.

Business capability use cases

A business capability is a structured way to capture and reuse established business scenarios.

Previously, when you implemented multiple microservices, you could only see a set of system interfaces. The business capability feature provides a business perspective, explaining what underlying microservices do and clarifying the role each interface plays in a business scenario. This approach visualizes your business capabilities.

By measuring business capabilities, you can understand their reuse rate and effectiveness. For example, you can identify which business scenarios are used frequently and deliver high value, and which requested features have low actual usage over time.

The core purpose of managing and operating business capabilities is to activate and leverage the capabilities already built into your microservices.

Failed to connect to a cluster

Symptom

Cause

The current resource account does not have the administrator or operator role for the cluster.

Solution

Configure RBAC permissions for the current account within the cluster. For detailed instructions, see Use RBAC to authorize operations on cluster resources.