You need to enable JavaScript to run this app.
Volcano Engine Function as a Service

Volcano Engine Function as a Service

Copy page
Download PDF
Version management
Releasing functions
Copy page
Download PDF
Releasing functions
After you create a function, you need to release it before it can start running the function-related workloads. This topic describes how to release a function.​
Background information​
veFaaS supports both full release and canary release.​
Full release​
  • The new revision receives 100% of the traffic.​
  • You can initiate the next release after a successful full release.​
Canary release​
  • The new revision receives 10% to 100% of the traffic. After the specified percentage is reached, you need to confirm the next operation, such as adjusting the percentage, proceeding to a full release, or rolling back.​
  • In a canary release, if the traffic percentage of the new revision is less than 100%, the function is in the Releasing state, and the next release is not allowed.​
tip​
  • The first release is a full release by default.​
  • Starting from the second release, you can select the desired release method.​
Prerequisites​
A function has been created. For specific operations, see Creating functions.​
Procedure​
  1. Log in to the veFaaS console.​
  1. In the top navigation bar, select the target region.​
  1. In the function list, find the function for which you want to create a trigger and click its name.​
  1. In the upper-right corner of the function details page, click Release, and specify parameters related to the release.​
  • ​
    Parameter​
    Description​
    Function revision​
    Select the function revision to be released.​
    • Latest: The system automatically creates a revision and releases it based on the latest edited function code and configuration.​
    • Specific revision number: Release the selected revision. Online traffic will be routed back to the selected revision, and a new release ticket will be created.​
    Revision description​
    Enter the description of the function revision to be released. The description can be up to 200 characters in length and can be left empty.​
    Minimum instances​
    You need to specify this parameter when you release the function revision for the first time.​
    The minimum number of instances is the number of reserved instances. The system will maintain at least this number of continuously running instances until you set it to 0. Reserved instances are billed continuously while they are running. For billing details, see Product billing.​
    tip​
    • For microservice applications, the minimum number of instances must be greater than or equal to 1.​
    • If you need to adjust the minimum number of instances, go to Resource management > Maximum resource > Instance count range.​
    Maximum instances​
    You need to specify this parameter when you release the function revision for the first time.​
    Set the maximum number of instances required for the function to handle workloads. After the function is released, the configured function resources will take effect.​
    tip​
    If you need to adjust the maximum number of instances, go to Resource management > Maximum resource > Instance count range.​
    Release method​
    When you release a function revision for the second time, select an appropriate release method as needed.​
    • Full release: The new revision receives 100% of the traffic.​
    • Canary release: You can specify the traffic percentage between the online revision and the canary revision to be released. To observe the behavior of the new and old function revisions, select Canary release.​
    tip​
    When a canary revision exists, requests are randomly routed to the new and old function revisions based on the traffic percentage.​
    Deployment details​
    Display the configuration changes and code changes of the function revision to be released compared to the online revision.​
    ​
  1. Click Confirm to go to the Release management > Release details page for the current function. Then, the function release starts.​
What to do next​
  • During the function release process, you can observe the release progress in real time. For detailed information, see Observing the release process.​
  • For event functions, web applications, and tasks, you can create triggers, define the function trigger logic, and start the function-related workloads after a successful full release. For detailed operations, see Creating triggers.​
Last updated: 2026.08.19 14:06:06