Based on the changing requirements, there may be scenarios where you will have to make changes to your current deployment, i.e., to make an application available in another partition, enable cloud bursting, etc. In such situations, you need to change the current deployment patterns, by updating the relative artifacts in runtime. Always follow the logical sequence when updating artifacts to avoid facing errors. The following sub-sections discuss the sequence in which you need to update the artifacts.
A Kubernetes cluster can be updated in run-time by adding hosts to the Kubernetes cluster. For more information on how new hosts can be added to an existing Kubernetes cluster via REST API or CLI, see Adding a Host to a Kubernetes-CoreOS Cluster.
You can carryout any of the following actions to update a network partition in run-time:
Follow the instructions below to add a new partition in an existing network partition in run-time:
Identify the network partition that corresponds to the deployed application, and define a new partition in the existing network partition definition JSON.
Update the identified network partition in Stratos.
Optionally, if you wish to use the new partition in the existing deployment policy, carryout the following steps:
Identify the deployment policy that corresponds to the deployed application, and add the newly defined partition to the existing deployment policy definition JSON.
Update the identified deployment policy in Stratos.
Follow the instructions below to update the values in an existing network partition in run-time:
Identify the network partition that corresponds to the deployed application, and update the values in the existing network partition definition JSON.
Update the identified network partition in Stratos.
Follow the instructions below to remove a partition from an existing network partition in run-time:
Identify the deployment policy that corresponds to the deployed application, and remove the partition from the deployment policy JSON definition.
Update the identified deployment policy in Stratos.
Identify the network partition that corresponds to the deployed application, and remove the partition from the network partition JSON definition.
Update the identified network partition in Stratos.
When a deployment policy is updated in run-time, Stratos applies these changes to all the applications that are using the deployment policy. You can carryout any of the following actions to update a deployment policy in run-time:
Follow the instructions below to add a new partition to an existing deployment policy in run-time:
Optionally, identify the network partition that corresponds to the deployed application, and define a new partition in the existing network partition definition JSON. If you wish to use an unused partition, which already exists in the network partition, skip step 1 and 2.
Update the identified network partition in Stratos.
Identify the deployment policy that corresponds to the deployed application, and add the new partition to the existing deployment policy definition JSON.
Update the identified deployment policy in Stratos.
Follow the instructions below to remove a partition from an existing deployment policy in run-time:
Identify the deployment policy that corresponds to the deployed application, and remove the partition from the deployment policy JSON definition.
Update the identified deployment policy in Stratos.
Identify the network partition that corresponds to the deployed application, and remove the partition from the network partition JSON definition.
Update the identified network partition in Stratos.
Follow the instructions below to update the values in an existing deployment policy in run-time:
Identify the deployment policy that corresponds to the deployed application, and update the values in the existing deployment policy definition JSON.
Update the identified deployment policy in Stratos.
When a auto-scaling policy is updated in run-time, Stratos applies these changes to all the applications that are using the auto-scaling policy. Only specific properties in an auto-scaling policy definition can be updated. For more information on what properties can be updated, see the Auto-scaling Policy Resource Definition, and see Updating an Auto-scaling Policy to learn how to update an auto-scaling policy via the REST API, CLI or the UI.
When a cartridge is updated in run-time, Stratos will not apply the changes to the currently deployed applications. However, Stratos will apply these changes to all the applications that are deployed after these changes. Only specific properties in a cartridge definition can be updated. For more information on what properties can be updated, see the Cartridge Resource Definition, and see Updating a Cartridge to learn how to update a cartridge via the REST API, CLI or the UI.
Stratos does not allow cartridge groups to be updated.
Only specific properties in an application definition can be updated as stated below. For more information on what properties can be updated, see the Application Resource Definition, and see Updating an Application to learn how to update an application via the REST API, CLI or the UI.