You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/user-guide/application-groups.md
+51-16Lines changed: 51 additions & 16 deletions
Original file line number
Diff line number
Diff line change
@@ -137,6 +137,11 @@ Users need to have [Build and deploy permission](../user-guide/global-configurat
137
137
138
138
### Hibernating and Unhibernating Apps
139
139
140
+
{% hint style="warning" %}
141
+
### Who Can Perform This Action?
142
+
Users need to have [Build & deploy permission](../global-configurations/authorization/user-access.md#role-based-access-levels) or above (along with access to the environment and application) to hibernate or unhibernate applications.
143
+
{% endhint %}
144
+
140
145
Since every application comes with an option to hibernate, the same is true for application groups. Using application group, you can hibernate one or more applications belonging to the same environment if you do not want them to consume resources (replica count will be set to 0).
141
146
142
147
In other words, you can hibernate running applications or unhibernate hibernated applications as per your requirement.
@@ -145,11 +150,11 @@ In other words, you can hibernate running applications or unhibernate hibernated
145
150
146
151
1. In the `Overview` page of your application group, use the checkboxes to choose the applications you wish to hibernate, and click the **Hibernate** button.
147
152
148
-
153
+
3. Hibernation will initiate as shown below. You may close the window.
155
160
@@ -161,45 +166,74 @@ Your applications pods would be scaled down and would stop incurring costs.
161
166
162
167
1. In the same `Overview` page, you can use the checkboxes to choose the hibernated applications you wish to unhibernate, and click the **Unhibernate** button.
163
168
164
-
169
+
3. Unhibernation will initiate as shown below. You may close the window.
171
176
172
177
173
178
174
179
Your applications would be up and running in some time.
175
180
181
+
### Restart Workloads
182
+
183
+
{% hint style="warning" %}
184
+
### Who Can Perform This Action?
185
+
Users need to have [Build & deploy permission](../global-configurations/authorization/user-access.md#role-based-access-levels) or above (along with access to the environment and application) to restart workloads in bulk.
186
+
{% endhint %}
187
+
188
+
Restarting workloads might be necessary if you want your new code or configuration to come into effect, or you are experiencing issues like crashing of pods.
189
+
190
+
Using application group, you can select the workloads (i.e., Pod, Deployment, ReplicaSet, etc.) of specific applications and restart them.
191
+
192
+
1. Use the checkboxes to choose the applications whose workloads you wish to restart, and click the **Restart Workload** button.
193
+
194
+
195
+
196
+
2. Next to the application, click the workload dropdown to view all the individual workloads of an application. Choose only the ones you wish to restart.
Restarting workloads might take time depending on the number of applications.
209
+
176
210
### Filtering Applications
177
211
178
212
Assume you have multiple applications (maybe 10, 50, 100, or more) showing up in an application group. If you want to limit your operations (build/deploy/other) to a specific set of applications, the filter feature will help you narrow down the list. Thus, you will see only those applications you select from the filter (be it on the `Overview` page, `Build & Deploy` page, and so on.)
179
213
180
214
1. Click the filter next to the application group as shown below.
@@ -234,16 +268,17 @@ Users can delete a saved filter if they have Admin/Manager access on all applica
234
268
235
269
### Changing Branch
236
270
271
+
{% hint style="warning" %}
272
+
### Who Can Perform This Action?
273
+
Users need to have [Admin role](../user-guide/global-configurations/authorization/user-access.md#role-based-access-levels) or above (along with access to the environment and applications) to update their branch.
274
+
{% endhint %}
275
+
237
276
Assume you have a few applications whose [build pipelines](../reference/glossary.md#build-pipeline) fetch from the `main` branch of your code repository. However, you decided to maintain a `master` branch, and you want all the upcoming CI builds to consider the `master` branch as the source. Devtron provides you the option to change the branch at both levels—individual application as well as application group.
238
277
239
278
1. In the **Build & Deploy** tab of your application group, select the intended applications and click the **Change Branch** button present at the bottom.
2. Enter the new branch name. If your build pipeline has `Branch Regex` as the Source Type, you must ensure your new branch name matches the regex (regular expression) provided in that build pipeline. Once done, click **Update Branch**.
Users need to have [Admin role](../user-guide/global-configurations/authorization/user-access.md#role-based-access-levels) or above (along with access to the environment and applications) to update their branch
0 commit comments