You need to ensure that the edge runtime is always updated to the latest version when it is available.
You decide to use rolling version tags in your deployment manifest.
Does it fit the requirements?
Click on the arrows to vote for the correct answer
A. B.Correct Answer: A.
Option A is CORRECT because using rolling tags (e.g.
1.0 - without specifying sub-versions)always updates to the latest version, i.e.
for the given scenario, this is the right solution.
There are two strategies for updating edge runtime modules (edgeAgent and edgeHub) using version tags: rolling tags and specific tags.
Option B is incorrect because using the other update strategy uses specific tags (like: 1.0.7) which will result in deploying the specific module version defined by the tag.
In this case, no automatic upgrade to the latest version takes place.
References:
The decision to use rolling version tags in the deployment manifest to update the edge runtime depends on various factors, such as the deployment model, the update process, and the desired outcome.
Rolling version tags refer to a versioning scheme that sequentially tags each new version of the edge runtime as it becomes available, with the latest version being tagged as "latest." When a deployment is initiated, the tag "latest" is used to pull the most recent version of the edge runtime. The rolling tag approach ensures that the edge runtime is always updated to the latest version when it is available.
However, there are some considerations to keep in mind when using rolling version tags:
Potential compatibility issues: While updating to the latest version of the edge runtime may be desirable, it's possible that the new version may not be compatible with the existing code or configuration. This could lead to runtime errors or failures.
Risk of breaking changes: New versions of the edge runtime may introduce breaking changes that could affect the behavior of the deployed modules. It's essential to test and validate the new version thoroughly before deploying it to production.
Uncontrolled updates: Rolling version tags may automatically update the edge runtime without proper validation or control, leading to potential issues or downtime.
Lack of rollback options: If the new version of the edge runtime causes issues or failures, rolling back to the previous version may be challenging or impossible.
Therefore, it's essential to evaluate the benefits and risks of using rolling version tags in the deployment manifest to ensure that it fits the requirements. If the benefits outweigh the risks, rolling version tags can be a useful approach to keep the edge runtime updated to the latest version automatically. However, if the risks are too high, an alternative approach should be considered.
In conclusion, the answer to the question depends on the specific requirements and circumstances. If the benefits of using rolling version tags outweigh the risks, then the answer is "Yes." If the risks are too high, then the answer is "No."