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/deployments/gitops/applications-dashboard.md
+24-64Lines changed: 24 additions & 64 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,10 +21,9 @@ max-width="60%"
21
21
%}
22
22
23
23
24
-
Monitor the current[health and syncstatus of applications](#identify-applications-with-warningserrors), and then select an application to drill down into its resources, deployments, and services:
25
-
*Use application header for
24
+
Identify applications with[health and syncerrors](#identify-applications-with-warningserrors), and then select an application to drill down into its resources, deployments, and services:
25
+
*[Get status from application header](#get-status-from-application-header)
26
26
*[View deployment and configuration info for selected application](#view-deployment-and-configuration-info-for-selected-application)
27
-
*[Monitor health and sync statuses for selected application](#monitor-health-and-sync-statuses-for-selected-application)
28
27
*[Monitor resources for selected application](#monitor-resources-for-selected-application)
29
28
*[Monitor deployments for selected application](#monitor-deployments-for-selected-application)
30
29
*[Monitor services for selected application](#monitor-services-for-selected-application)
@@ -120,10 +119,10 @@ Applications with `rollout` resources need Argo Rollouts on the target cluster,
120
119
* To stop the sync operation, click**Terminate**.
121
120
* Drill down into the application to investigate the issue and make changes.
122
121
123
-
##Use application header for latest status info
124
-
When you select an application from the GitOps Apps dashboard, the application header is displayed at the top of the page.
125
-
The app header gathers and displays critical information aboutthe application, regardless of the tabselected.
126
-
For example, it displays the health, current and previous sync operation results, and indicates if auto-sync is enabled or disabled for the application.The**More** linksopen panels with detailed information.
122
+
##Get status from application header
123
+
When you select an application from the GitOps Apps dashboard, the application header is displayed at the top of the page with important information on the application.
124
+
Once you select an application, the quickest option to monitor statuses is throughthe application header which is always displayed, no matter what tabyou navigate to.
125
+
For example, it displays the health, current and previous sync operation results, and indicates if auto-sync is enabled or disabled for the application.Sync statuses also have**More** linksthat display details such as the date, tags, and message.
alt="Accessing Quick View from the Current State tab"
178
180
caption="Accessing Quick View from the Current State tab"
179
-
max-width="50%"
181
+
max-width="60%"
180
182
%}
181
183
182
184
The Quick View includes the following tabs:
@@ -189,34 +191,7 @@ The Quick View includes the following tabs:
189
191
* Events: Displays status and sync events for the application.
190
192
191
193
192
-
##Monitor health and sync statuses for selected application
193
-
Monitor the health status of the selected application, the current sync status, and the result of the previous sync operation.
194
-
Once you select an application, the quickest option to monitor statuses is through the application header which is always displayed, no matter what tab you navigate to.
alt="Monitor application resources in Current State tab"
234
209
caption="Monitor application resources in Current State tab"
235
-
max-width="50%"
210
+
max-width="60%"
236
211
%}
237
212
238
213
The icon for a resource node identifies the type of Kubernetes resource it represents. For general information on K8s resources, see[Working with Kubernetes objects](https://kubernetes.io/docs/concepts/overview/working-with-objects/){:target="\_blank"}.
@@ -282,7 +257,7 @@ max-width="50%"
282
257
283
258
####Working with resources in Tree view
284
259
The Tree view is designed to impart key information at a glance. Review the sections that follow for pointers to quickly get to what you need in the Tree view.
285
-
260
+
<!---
286
261
**Context menu**
287
262
Every resource has a context menu that opens on clicking the three dots on the right of the node. The options available differ according to the type of resource.
alt="Current State Tree view: Resource context menu"
295
270
caption="Current State Tree view: Resource context menu"
296
271
max-width="50%"
297
-
%}
272
+
%}-->
298
273
299
274
**Resource info**
300
275
Mouse over a node to see a tooltip for that resource. For detailed information, select the resource.
@@ -325,37 +300,22 @@ max-width="50%"
325
300
326
301
327
302
**Resource inventory**
328
-
The Resource inventory in the Tree view (bottom-left), summarizes the aggregated count for each resource type in the application.
329
-
For visibility and quick access,`Syncing` and`Out-of-Sync` resources are bucketed separately.
330
-
331
-
{::nomarkdown}
332
-
<br>
333
-
{:/}
303
+
The Resource inventory in the Tree view (bottom-left), summarizes the aggregated count for each resource type in the application. The number of`out-of-sync` items for that resource type if any are numbered in red.
334
304
335
305
Click-filters:
336
306
337
-
In the resource inventory, selecting a`Syncing` or`Out-of-Sync` resource type, filters the Current State by that resource type and sync status.
338
-
These filters are automatically appliedto the default filter list for both Tree and List views.
307
+
Selecting any resource type, filters the Current State by that resource type and sync status.
308
+
These filters are automatically applied to the default filter list for both Tree and List views.
339
309
Here's an example of an application with out-of-sync resources, and the result on selecting an out-of-sync resource type.
alt="Current State Tree view: Resource inventory filtered byout-of-sync service"
358
-
caption="Current State Tree view: Resource inventory filtered byout-of-sync service"
317
+
alt="Current State Tree view: Resource inventory filtered byRollouts"
318
+
caption="Current State Tree view: Resource inventory filtered byRollouts"
359
319
max-width="50%"
360
320
%}
361
321
@@ -406,7 +366,7 @@ Identify the health of an application resource through the color-coded border an
406
366
|**Healthy**| Resource is functioning as required.| {::nomarkdown}<img src="../../../../images/icons/current-state-healthy.png" display=inline-block">{:/}|
407
367
|**Progressing**| Resource is not healthy but can become healthy before the timeout occurs.| {::nomarkdown}<img src="../../../../images/icons/current-state-progressing.png" display=inline-block">{:/}|
408
368
|**Suspended**| Resource is not functioning, and is either suspended or paused. For example, Cron job or a canary rollout.| {::nomarkdown}<img src="../../../../images/icons/current-state-suspended.png" display=inline-block">{:/}|
409
-
|**Missing**| Resource is not present on the cluster.|{::nomarkdown}<img src="../../../images/icons/current-state-missing.png" display=inline-block">{:/}|
369
+
|**Missing**| Resource is not present on the cluster.|{::nomarkdown}<img src="../../../../images/icons/current-state-missing.png" display=inline-block">{:/}|
410
370
|**Degraded**| Resource is not healthy, or a timeout occurred before it could reach a healthy status.| {::nomarkdown}<imgsrc="../../../../images/icons/current-state-degraded.png"display=inline-block/>{:/}|
411
371
|**Unknown**| Resource does not have a health status, or the health status is not tracked in Argo CD. For example,`ConfigMaps` resource types.| {::nomarkdown}<img src="../../../../images/icons/current-state-unknown.png" display=inline-block">{:/}|
412
372
@@ -657,11 +617,11 @@ max-width="50%"
657
617
658
618
The table lists the controls in the Rollout Player to manage an ongoing rollout.
659
619
660
-
{}: .table .table-bordered .table-hover}
620
+
{: .table .table-bordered .table-hover}
661
621
| Rollback player option| Description|
662
622
| --------------| ------------|
663
623
|**Rollback**| Not available currently.|
664
-
|**Resume** {::nomarkdown}<img src=".../../../../images/icons/rollout-resume.png" display=inline-block"> {:/}| Resume a step that has been paused indefinitely.|
624
+
|**Resume** {::nomarkdown}<img src="../../../../images/icons/rollout-resume.png" display=inline-block"> {:/}| Resume a step that has been paused indefinitely.|
665
625
|**Skip step** {::nomarkdown}<img src="../../../../images/icons/rollout-skip-step.png" display=inline-block"> {:/}| Skip execution of current step. Such steps are marked as Skipped in the rollout visualization.|
666
626
|**Promote full rollout** {::nomarkdown}<img src="../../../../images/icons/rollout-promote-full.png" display=inline-block"> {:/}| Skip remaining pause, traffic routing, and analysis steps, and deploy the current release.|