{:/}.
-
->If you star applications as favorites, you can filter by the same applications in the [DORA metrics dashboard]({{site.baseurl}}/docs/reporting/dora-metrics/#metrics-for-favorite-applications).
-
-
-
-#### Deployment type
-Applications are displayed according to their deployment type which can be one of the following:
-* Applications
+file="/images/applications/app-dashboard-main-view.png"
+url="/images/applications/app-dashboard-main-view.png"
+alt="Applications Dashboard: List view"
+caption="Applications Dashboard: List view"
+max-width="60%"
+%}
- Standalone applications. For detailed information, see the official documentation on [Applications](https://argo-cd.readthedocs.io/en/stable/operator-manual/declarative-setup/#applications){:target="\_blank"}.
+#### Applications Card view
+Here is an example of the Applications dashboard in Card view mode. The Card view provides a scannable view of application data and the actions to manage applications.
{% include
image.html
lightbox="true"
-file="/images/applications/apps-standalone.png"
-url="/images/applications/apps-standalone.png"
-alt="Standalone applications in Applications Dashboard"
-caption="Standalone applications in Applications Dashboard"
-max-width="30%"
+file="/images/applications/app-dashboard-card-view.png"
+url="/images/applications/app-dashboard-card-view.png"
+alt="Applications Dashboard: Card view"
+caption="Applications Dashboard: Card view"
+max-width="60%"
%}
-* Application set
- Based on the Argo CD's ApplicationSet CRD, where several applications are always deployed as a set. For detailed information, see the official documentation on [Generating Applications with ApplicationSet](https://argo-cd.readthedocs.io/en/stable/user-guide/application-set/){:target="\_blank"}.
+### Applications dashboard information
+Here's a description of the information and actions in the Applications dashboard.
- {% include
-image.html
-lightbox="true"
-file="/images/applications/app-appset-model.png"
-url="/images/applications/app-appset-model.png"
-alt="Application Set in Applications Dashboard"
-caption="Application Set in Applications Dashboard"
-max-width="30%"
-%}
-
-* App-of-apps
- In this deployment model, the parent application deploys a set of child applications. For detailed information, see the official documentation on [App of Apps](https://argo-cd.readthedocs.io/en/stable/operator-manual/declarative-setup/#app-of-apps){:target="\_blank"}.
+{: .table .table-bordered .table-hover}
+| Item | Description |
+| -------------- | -------------- |
+|Application filters | Filter by a range of attributes to customize the information in the dashboard to bring you what you need. {::nomarkdown} A comprehensive read-only view of the deployment and definition information for the application.
Manually synchronize the application.
Modify application definitions.
- Refresh: Retrieve desired (Git) state, compare with the live (cluster) state, and refresh the application to sync with the desired state.
- Hard Refresh: Refresh the application to sync with the Git state, while removing the cache.
{:/} |
-| **Degraded** | {::nomarkdown}
{:/} |
-| **Suspended** | {::nomarkdown}
{:/} |
-| **Missing** | {::nomarkdown}
{:/} |
-| **Progressing** | {::nomarkdown}
{:/} |
-| **Unknown** | {::nomarkdown}
{:/} |
+> To quickly see which resources have been added, modified, or removed for the current or for a specific deployment, switch to the Timeline tab and expand the deployment record to show Updated Resources. See [Monitor resource updates for deployments](#monitor-resource-updates-for-deployments).
+#### View modes for application resources
-##### Sync state
-The sync state is identified by the icon to the left of the resource name and the color of the resource name. For information on sync options you can configure for applications, see [Sync settings]({{site.baseurl}}docs/deployment/create-application/#sync-settings).
-
-{: .table .table-bordered .table-hover}
-| Sync state | Display in Tree view |
-| -------------- | ---------- |
-| **Synced** | {::nomarkdown}
{:/} |
-| **Syncing** | {::nomarkdown}
{:/} |
-| **Out-of-Sync** | {::nomarkdown}
{:/} |
-| **Unknown** | {::nomarkdown}
{:/} |
-
+The Current State tab supports Tree and List view formats.
+* Tree view (default): A hierarchical, interactive visualization of the application and its resources. Useful for complex deployments with multiple clusters and large numbers of resources. See also [Working with resources in Tree view](#working-with-resources-in-tree-view).
+Here is an example of the Current State in Tree view.
-##### Resource inventory
-At the bottom left is the Resource inventory, summarizing the aggregated count for each resource type in the application. Syncing and Out-of-Sync resources are bucketed separately for visibility and quick access.
-{::nomarkdown}
--{:/} - -**Click-filters** -In the resource inventory, selecting a Syncing or Out-of-Sync resource type, filters the Current State by that resource type and sync state. -These filters are automatically reflected in the default filter list for both Tree and List views. -Here's an example of an application with out-of-sync resources, and the result on selecting an out-of-sync resource type. +{% include +image.html +lightbox="true" +file="/images/applications/current-state-tree-app-in-progress.png" +url="/images/applications/current-state-tree-app-in-progress.png" +alt="Tree view of application resources in Current State" +caption="Tree view of application resources in Current State" +max-width="50%" +%} +* List View: A list-based representation of application's resources, sorted by the Last Update. + Here is an example of the Current State in List view. {% include image.html lightbox="true" -file="/images/applications/current-state-tree-resource-list.png" -url="/images/applications/current-state-tree-resource-list.png" -alt="Current State Tree view: Resource inventory" -caption="Current State Tree view: Resource inventory" +file="/images/applications/apps-current-state.png" +url="/images/applications/apps-current-state.png" +alt="List view of application resources in Current State" +caption="List view of application resources in Current State" max-width="50%" %} +> Filters are common to both Tree and List views, and when applied are retained when switching between views. + +##### Working with resources in Tree view +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. + +**Context menu** +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. + {% include image.html lightbox="true" -file="/images/applications/current-state-tree-resource-filtered.png" -url="/images/applications/current-state-tree-resource-filtered.png" -alt="Current State Tree view: Resource inventory filtered by out-of-sync service" -caption="Current State Tree view: Resource inventory filtered by out-of-sync service" +file="/images/applications/current-state-resource-context-menu.png" +url="/images/applications/current-state-resource-context-menu.png" +alt="Current State Tree view: Resource context menu" +caption="Current State Tree view: Resource context menu" max-width="50%" %} -##### Resource info -Mouse over a node to see a tooltip for that resource. For detailed information, select the resource; see [Detailed resource information](#detailed-resource-information) in this article. +**Resource info** +Mouse over a node to see a tooltip for that resource. For detailed information, select the resource. {% include image.html @@ -378,8 +330,8 @@ caption="Current State Tree view: Resource tooltip" max-width="50%" %} -##### Search resources -Quickly find a resource by typing the resource name in the search field. Search results have a different border for identification. Press Enter to navigate to the next result. +**Search resources** +Quickly find a resource by typing the resource name in the search field. You can identify search results through the border which is different from the borders depicting health status. Press Enter to navigate to the next result. {% include image.html @@ -392,29 +344,85 @@ max-width="50%" %} -#### Current State List view -Here is an example of the Current State in List view. + +**Resource inventory** +The Resource inventory in the Tree view (bottom-left), summarizes the aggregated count for each resource type in the application. +For visibility and quick access, `Syncing` and `Out-of-Sync` resources are bucketed separately. + +{::nomarkdown} +
+{:/} + +Click-filters: + +In the resource inventory, selecting a `Syncing` or `Out-of-Sync` resource type, filters the Current State by that resource type and sync status. +These filters are automatically applied to the default filter list for both Tree and List views. +Here's an example of an application with out-of-sync resources, and the result on selecting an out-of-sync resource type. + {% include image.html lightbox="true" -file="/images/applications/apps-current-state.png" -url="/images/applications/apps-current-state.png" -alt="Applications Dashboard: List view of Current State" -caption="Applications Dashboard: List view of Current State" +file="/images/applications/current-state-tree-resource-list.png" +url="/images/applications/current-state-tree-resource-list.png" +alt="Current State Tree view: Resource inventory" +caption="Current State Tree view: Resource inventory" max-width="50%" %} -#### Detailed resource information -Selecting a resource, in either Tree or List view, shows resource manifests, logs, and events if any, based on the resource type you selected. Endpoints for example show only manifests, while pods show manifests, logs, and events. +{% include +image.html +lightbox="true" +file="/images/applications/current-state-tree-resource-filtered.png" +url="/images/applications/current-state-tree-resource-filtered.png" +alt="Current State Tree view: Resource inventory filtered by out-of-sync service" +caption="Current State Tree view: Resource inventory filtered by out-of-sync service" +max-width="50%" +%} -> Selecting the application resource in Tree View, displays the [Quick View](#application-quick-view) for the application. -{::nomarkdown} -
-{:/} +#### Health status for application resources +View and monitor health status of the selected application's resources in the Current State tab, in Tree or List views. +Identify the health of an application resource through the color-coded border and the resource-type icon (Tree view), or the textual labels at the right of the resource (List view). + + +{: .table .table-bordered .table-hover} +| Health status | Description | Display in Tree view | +| -------------- | ------------| ------------------| +| **Healthy** | Resource is functioning as required. | {::nomarkdown}
{:/} |
+| **Progressing** | Resource is not healthy but can become healthy before the timeout occurs.| {::nomarkdown}{:/} |
+| **Suspended** | Resource is not functioning, and is either suspended or paused. For example, Cron job or a canary rollout.| {::nomarkdown}{:/} |
+| **Missing** | Resource is not present on the cluster. |{::nomarkdown}{:/} |
+| **Degraded** | Resource is not healthy, or a timeout occurred before it could reach a healthy status.| {::nomarkdown}{:/} |
+| **Unknown** | Resource does not have a health status, or the health status is not tracked in Argo CD. For example,`ConfigMaps` resource types. | {::nomarkdown}{:/} |
+
+See also [Argo CD's set of health checks](https://argo-cd.readthedocs.io/en/stable/operator-manual/health/).
+
+
+
+#### Sync status for application resources
+
+Similar to the health status, the Current State also tracks the sync status of all application resources. The sync status identifies if the live state of the application resource on the cluster is synced with its desired state in Git.
+Identify the sync status through the icon on the left of the resource name and the color of the resource name (Tree view), or the textual labels at the right of the resource (List view).
+
+The table describes the possible sync statuses for an application resource, and its representation in the Tree view.
+
+{: .table .table-bordered .table-hover}
+| Sync state | Description |Display in Tree view |
+| -------------- | ---------- | ---------- |
+| **Synced** | The live state of the resource on the cluster is identical to the desired state in Git.| {::nomarkdown}{:/} |
+| **Syncing** | The live state of the resource was not identical to the desired state, and is currently being synced.| {::nomarkdown}{:/} |
+| **Out-of-Sync** | {::nomarkdown}The live state is not identical to the desired state.To sync a resource, select the Sync option from the resource's context menu in Tree view. {:/}| {::nomarkdown}
{:/} |
+| **Unknown** | The sync status could not be determined. | {::nomarkdown}{:/} |
+
+
+#### Manifests for application resources
+
+In either Tree or List views, double-click an application resource to see its manifests. The manifests are displayed in the Summary tab.
+> Based on the selected resource type, you can also view logs, and events. Endpoints for example show only manifests, while pods show manifests, logs, and events.
+
+> To view information for the application resource, select the application node in Tree View. See [Application information](#application-quick-view).
-**Summary**
{% include
image.html
@@ -426,18 +434,22 @@ caption="Current State Tree view: Resource tooltip"
max-width="50%"
%}
-* Desired and Live states:
- * Managed resources stored in Git repositories and using Git as the single source of truth, show both the Desired state and the Live state.
+Here's what you can see and do in the Summary tab:
+> Press Ctrl/Command F to search for strings in the manifest.
+
+* Desired and Live states of the resource manifest:
+ * Managed resources, stored in Git repositories and using Git as the single source of truth, show both the Desired (Git) and the Live (cluster) states.
If there are discrepancies between them, the Diff view is displayed, highlighting the differences in both versions for comparison.
* Resources that are not stored in Git but live in the cluster, show only the Live state.
-* Share resource details: Copy the URL and send to others in your organization to share the resource details for collaborative review and analysis. Pasting the URL in a browser opens to the same resource view.
-* Hide Managed Fields: When selected, hides managed-field information from the manifest. Managed-fields show information on which field manager manages the field, after Kubernetes introduced `Server Side Apply`. For more information, see [Field Management](https://kubernetes.io/docs/reference/using-api/server-side-apply/#field-management){:target="\_blank"}.
+* Share resource details: Copy the URL and send to others in your organization to share the resource details for collaborative review and analysis. Pasting the URL in a browser opens to the same view of the resource.
+* Hide Managed Fields: In the Live state version of the manifest, you can hide managed-field information from the manifest. Managed-fields show information on which field manager manages the field, after Kubernetes introduced `Server Side Apply`. For more information, see [Field Management](https://kubernetes.io/docs/reference/using-api/server-side-apply/#field-management){:target="\_blank"}.
{::nomarkdown}
{:/} -**Logs** +#### Logs for application resources +In either Tree or List views, double-click an application resource to see its logs. Logs are available only for resource types such as pods. {% include image.html @@ -449,6 +461,7 @@ caption="Current State: Logs for resource" max-width="50%" %} + * Search: Free-text search for any string in the log, using the next and previous buttons to navigate between the results, or Enter for sequential navigation. * Wrap: Enable/disable line wrapping * Download: Download the complete log into a text file for offline viewing and analysis. @@ -457,7 +470,12 @@ max-width="50%"
{:/} -**Events** +#### Events for application resources +In either Tree or List views, double-click an application resource to see events in the Events tab. +> If your runtime is lower than the version required to view events, you are notified to upgrade to the required version. + +The Events tab displays both successful and failed events from Argo CD, starting with the most recent event. +Argo CD displays events as they occur for an application resource, and retains event information for a duration of 30 minutes. Historical events older than this duration are removed, and the Events tab can be empty if there are no ongoing events. {% include image.html @@ -469,16 +487,16 @@ caption="Current State: Events for resource" max-width="50%" %} -View events for application resources in the Events tab. -> If your rutime is lower than the version required to view events, you are notified to upgrade your runtime. -The Events tab displays both successful and failed events from Argo CD, starting with the most recent event. -Argo CD displays events as they occur for an application resource, and retains event information for a duration of 30 minutes. Historical events older than this duration are removed, and the Events tab can be empty if there are no ongoing events. -### Application timeline -The Timeline tab displays the history of deployments for the selected application, sorted by the most recent update (default), and enriched with image, Pull Request (PR), Jira issues, and commit information for each deployment. Ongoing deployments display rollout progress and rollout analysis as the deployment unfolds. - -Each application displays up to ten of the most recent deployments. + + + +### Monitor deployments for selected application +Monitor an ongoing deployment for the selected application, and review its historical deployments. +The Timeline tab displays the history of deployments for the selected application, sorted by the most recent deployment (default), labeled **Current Version** at the top. + +The deployment chart displays the day-to-day deployments for the selected time period. Mouse over the dot on the deployment chart for information on historical deployments. {% include image.html @@ -490,16 +508,16 @@ caption="Applications Dashboard: Timeline tab" max-width="30%" %} -#### Filters +You can: +* [Monitor CI details by deployments](#monitor-ci-details-by-deployment) +* [Monitor updated resources by deployment](#monitor-updated-resources-by-deployment) +* [Monitor rollouts by deployment](#monitor-rollouts-by-deployment) -View the subset of deployments of interest to you. Filter by Date range, PRs, issues, committers, and more. -#### Deployment chart - -The deployment chart conveniently located below the filters displays the day-to-day deployments for the selected time period. Get information on historical deployments, as the deployment entries are shown for up to ten of the most recent deployments. - -* To jump to a specific deployment, click the dot on the chart that represents the deployment. -* To see GitOps details, mouse over the dot that represents the deployment. +**How to monitor deployments** +1. If required, set filters to narrow the number of deployments for the selected application. +1. To view GitOps details for a deployment, in the deployment chart mouse over the dot that represents the deployment. +1. To view additional details, expand the record for that deployment. {% include image.html @@ -511,95 +529,157 @@ caption="Applications Dashboard: Deployment chart" max-width="30%" %} -#### Deployment details +#### Monitor CI details by deployment -**Deployment entries** +Each deployment record displays the complete CI history for that deployment. -Each deployment entry displays the complete history of that deployment, by Git hash, Kubernetes services, and Argo applications: + +* The **CI Builds** shows the image(s) created or updated during deployment. Click to see the **Images** view in a new browser window. +* The **Pull Request (PRs)** used for the commit. +* The Jira **Issues** the PR aims to resolve or has resolved, with the current status. +* The **Committer** who made the changes. +#### Monitor updated resources by deployment +Each deployment record also identifies the resources that were changed (created, updated, or removed) as part of that deployment in **Updated Resources**. You can trace the history of a resource, from the original to their final versions. For each version, you can see the actual change or changes through the Diff view. The Full View shows the complete resource manifest, with the diff view of the changes, while the Compact View shows only those lines with the changes. + +> For detailed information on the current state of a resource, switch to the Current State tab and click the resource node. See [Monitoring application resources](#monitoring-application-resources). + +1. Select a deployment record, and expand **Updated Resources**. + {% include image.html lightbox="true" -file="/images/applications/app-dashboard-time-expanded-card.png" -url="/images/applications/app-dashboard-time-expanded-card.png" -alt="Applications Dashboard: Deployment entry in Timeline tab" -caption="Applications Dashboard: Deployment entry in Timeline tab" +file="/images/applications/timeline-resources-updated.png" +url="/images/applications/timeline-resources-updated.png" +alt="Timeline tab: Updated Resources for deployment" +caption="Timeline tab: Updated Resources for deployment" max-width="70%" %} -* The **CI Builds** shows the image(s) created or updated during deployment. Click to see the **Images** view in a new browser window. -* The **Pull Request (PRs)** used for the commit. -* The Jira **Issues** the PR aims to resolve or has resolved, with the current status. -* The **Committer** who made the changes. -* The Kubernetes **Services** updated during the deployment, according to the Argo rollout strategy, and the current rollout status. - The example above shows the rollouts according to the canary rollout strategy. The blue line shows the progress of rollout with the current step versus the total number of steps. - Expanding the live version deployment shows the number of replicas currently deployed, as green circles. -* The Argo **Applications** updated during this deployment. +{:start="2"} +1. To see the changes for a resource, click the resource name. + The Full View of the resource manifest is displayed with the diff view of the changes. -#### Rollout progress visualization -A live deployment, meaning an Argo CD sync due to a change in the desired state, is visualized through the progress bar, as the rollout. -> Rollout progress is displayed only if you have an Argo `rollout` resource defined for your application. +{% include +image.html +lightbox="true" +file="/images/applications/timeline-resources-full-view.png" +url="/images/applications/timeline-resources-full-view.png" +alt="Full View of changes for updated resource" +caption="Full View of changes for updated resource" +max-width="70%" +%} -For detailed information, see [Argo Rollouts documentation](https://argoproj.github.io/argo-rollouts/){:target="\_blank"}. +{:start="3"} +1. To view only the changes, click **Compact View**. -Here is an example of the rollout progress bar for an ongoing canary deployment. The rollout comprising four steps has not started, and traffic has not been routed as yet to the new version of the application. +{% include +image.html +lightbox="true" +file="/images/applications/timeline-resources-compact-view.png" +url="/images/applications/timeline-resources-compact-view.png" +alt="Full View of changes for updated resource" +caption="Full View of changes for updated resource" +max-width="70%" +%} + + + +#### Monitor rollouts by deployment +A rollout is initiated when there is an Argo CD sync due to a change in the desired state. +Visualize ongoing and completed rollouts by deployments in **Services**. + +> To view and manage a rollout, you must have an Argo `rollout` resource defined for your application, and [install Argo Rollouts in the cluster]({site.baseurl}}/docs/_docs/deployment/install-argo-rollouts). + +For detailed information on Argo Rollouts, see [Argo Rollouts documentation](https://argoproj.github.io/argo-rollouts/){:target="\_blank"}. + +##### Rollout progress +For an ongoing rollout, the rollout bar displays the progress of the rollout. You can also visualize the steps in the rollout, and control the rollout using the options in the Rollout Player. + +Here is an example of an ongoing rollout for a canary deployment in Updated Services. The rollout comprising four steps has not started, and no traffic has not been routed as yet to the new version of the application. {% include image.html lightbox="true" file="/images/applications/apps-dashboard-rollout-in-progress.png" url="/images/applications/apps-dashboard-rollout-in-progress.png" -alt="Application deployment in progress" -caption="Application deployment in progress" +alt="Rollout in progress for deployment" +caption="Rollout in progress for deployment" max-width="50%" %} -Here is an example of the rollout progress bar for the same deployment on completion. All traffic has been routed to the new version. +Based on the current state of the rollout, you can pause and resume an ongoing rollout. +Here is an example of the rollout for the same deployment on completion. All traffic has been routed to the new version. {% include image.html lightbox="true" file="/images/applications/apps-dashboard-rollout-complete.png" url="/images/applications/apps-dashboard-rollout-complete.png" -alt="Application deployment completed" -caption="Application deployment completed" +alt="Rollout completed for deployment" +caption="Rollout completed for deployment" +max-width="50%" +%} + +##### Manage ongoing rollout +Click the rollout name to visualize its steps. Manually manage the rollout through the controls in the Rollout Player. +Here you can see that two out of four steps have been completed, 25% of the traffic has been routed, and the rollout has been paused for the defined length of time. + +{% include +image.html +lightbox="true" +file="/images/applications/rollout-player.png" +url="/images/applications/rollout-player.png" +alt="Rollout step visualization and Rollout Player" +caption="Rollout steps and Rollout Player" max-width="50%" %} -#### Rollout steps visualization -Clicking the rollout name displays the visualization of the steps in the rollout. + +The table lists the controls in the Rollout Player to manage an ongoing rollout. -Argo defines an analysis run as an instantiation of an AnalysisTemplate. The result of an analysis run determines if the rollout is completed, paused, or aborted. For detailed information, see the [Analysis section in Argo Rollouts](https://argoproj.github.io/argo-rollouts/features/analysis/){:target="\_blank"}. +: .table .table-bordered .table-hover} +| Rollback player option | Description | +| -------------- | ------------| +| **Rollback** | Not available currently. | +| **Resume** {::nomarkdown}
{:/}| Resume a step that has been paused indefinitely. |
+| **Skip step** {::nomarkdown}
{:/} | Skip execution of current step. Such steps are marked as Skipped in the rollout visualization. |
+| **Promote full rollout** {::nomarkdown}
{:/} | Skip remaining pause, traffic routing, and analysis steps, and deploy the current release. |
-Here you can see that two out of four steps have been completed, 25% of the traffic has been routed, and the rollout has been paused for the defined length of time.
+
+
+##### View analysis run
+If you have defined an analysis template for the rollout, you can check the run results and the manifest.
+ The result of an analysis run determines if the rollout is completed, paused, or aborted. For detailed information, see the [Analysis section in Argo Rollouts](https://argoproj.github.io/argo-rollouts/features/analysis/){:target="\_blank"}.
+
+If you are running Background Analysis for example, the first step shows the list of analysis metrics.
{% include
image.html
lightbox="true"
-file="/images/applications/apps-dashboard-rollout-analysis.png"
-url="/images/applications/apps-dashboard-rollout-analysis.png"
-alt="Application rollout: Analysis run"
-caption="Applications rollout: Analysis run"
-max-width="30%"
+file="/images/applications/app-rollout-analysis-template-step.png"
+url="/images/applications/app-rollout-analysis-template-step.png"
+alt="Rollout: Analysis Metrics in Background Analysis"
+caption="Analysis Template: Analysis Metrics in Background Analysis"
+max-width="50%"
%}
-To view run results, expand **Analysis metrics** in Background Analysis.
-The Manifest tab displays the analysis template manifest.
+Click the metric link in the step.
{% include
image.html
lightbox="true"
-file="/images/applications/apps-dashboard-run-results.png"
-url="/images/applications/apps-dashboard-run-results.png"
-alt="Application rollout: Analysis run results"
-caption="Applications rollout: Analysis run results"
-max-width="30%"
+file="/images/applications/app-rollout-run-results-manifest.png"
+url="/images/applications/app-rollout-run-results-manifest.png"
+alt="Analysis Template: Run Results and Manifest for Analysis Metric"
+caption="Analysis Template: Run Results and Manifest for Analysis Metric"
+max-width="50%"
%}
-### Application services
-The Services tab for an application shows the K8s services for each deployment of the application.
+### Monitor services for selected application
+The Services tab shows the K8s services for each deployment of the application.
Each service shows the number of replicas, the endpoint IP, the labels that reference the application, and the health status.
For more information, see the official documentation on [Services](https://kubernetes.io/docs/concepts/services-networking/service/){:target="\_blank"}.
diff --git a/_docs/deployment/create-application.md b/_docs/deployment/create-application.md
index 8f15651d..47aea2d7 100644
--- a/_docs/deployment/create-application.md
+++ b/_docs/deployment/create-application.md
@@ -1,5 +1,5 @@
---
-title: "Applications"
+title: "Creating applications"
description: ""
group: deployment
toc: true
@@ -14,12 +14,12 @@ Codefresh provides all the options and functionality to create and manage Argo C
* General configuration settings
* Advanced configuration settings
- The Create application wizard guides you through the process of creating an application. For how-to information, see [Create an Argo CD application](#how-to-create-an-argo-cd-application).
+ The Create application wizard guides you through the process of creating an application. For how-to information, see [Create an application](#create-an-application).
For example Argo CD applications, see this [repo](https://github.com/oleksandr-codefresh/argocd-example-apps){:target="_blank"}.
* Edit and delete applications
Once the application is created and synced to the cluster, it is displayed in the Applications dashboard. Here, you can select an application to update the application's configuration settings, or delete it.
- To monitor the health and sync status, deployments, and resources for the application, see [Applications dashboard]({{site.baseurl}}/docs/deployment/applications-dashboard/).
+ To monitor the health and sync status, deployments, and resources for the application, see [Monitoring applications]({{site.baseurl}}/docs/deployment/applications-dashboard/).
### Application: Definitions
Application definitions include the name, runtime, and the name of the YAML manifest. By default, the YAML manifest has the same name as that of the application.
@@ -74,10 +74,10 @@ The cluster and namespace to which to deploy the application.
{:/}
##### Sync Options
-{::nomarkdown}Common to both manual and automatic sync policies.- Skip schema validation: When selected, bypasses validating the YAML schema.
- Auto-create namespace: When selected, automatically create the namespace if the specified namespace does not exist in the cluster.
- Prune last: When selected, removes those resources that do not exist in the currently deployed version during the final wave of the sync operation. See Prune last.
- Apply out of sync only: When selected, syncs only those resources in the application that have been changed and are OutOfSync, instead of syncing every resource regardless of their state. This option is useful to reduce load and save time when you have thousands of resources in an application. See Selective Sync.
- Skip schema validation: When selected, bypasses validating the YAML schema.
- Auto-create namespace: When selected, automatically create the namespace if the specified namespace does not exist in the cluster.
- Prune last: When selected, removes those resources that do not exist in the currently deployed version during the final wave of the sync operation. See Prune last.
- Apply out of sync only: When selected, syncs only those resources in the application that have been changed and are OutOfSync, instead of syncing every resource regardless of their state. This option is useful to reduce load and save time when you have thousands of resources in an application. See Selective Sync.
+
{:/} ##### Prune propagation policy @@ -150,7 +150,7 @@ Review: **How to** -1. In the Codefresh UI, go to [Applications](https://g.codefresh.io/2.0/applications-dashboard?sort=desc-lastUpdated){:target="\_blank"}. +1. In the Codefresh UI, go to [Applications dashboard](https://g.codefresh.io/2.0/applications-dashboard/list){:target="\_blank"}. 1. On the top-right, select **Add Application**. 1. In the Add Application panel, add definitions for the application: * Application name: Must be unique within the cluster. @@ -217,111 +217,15 @@ Review: Your application is first committed to Git, and then synced to the cluster which may take a few moments. -Track the application in the [Applications dashboard](https://g.codefresh.io/2.0/applications-dashboard){:target="_blank"}. +Track the application in the [Applications dashboard](https://g.codefresh.io/2.0/applications-dashboard/list){:target="_blank"}. {::nomarkdown}
{:/} -### Update application configuration -Update General or Advanced configuration settings for a deployed application. Once the application is deployed to the cluster, the Configuration tab is available on selecting the application in the Applications dashboard. - -> You cannot change application definitions (the application name and the selected runtime), and the Git Source selected for the application. - -**How to** - -1. In the Codefresh UI, go to the [Applications dashboard](https://g.codefresh.io/2.0/applications-dashboard){:target="\_blank"}. -1. Select the application to update, and then select the **Configuration** tab. - -{% include - image.html - lightbox="true" - file="/images/applications/edit-app-configuration-tab.png" - url="/images/applications/edit-app-configuration-tab.png" - alt="Configuration tab with application settings" - caption="Configuration tab with application settings" - max-width="70%" - %} - -{:start="3"} -1. Update the **General** or **Advanced** configuration settings as needed: - [General configuration](#general-configuration-settings) - [Advanced configuration](#advanced-configuration-settings) - When you change a setting, the Commit and Discard Changes buttons are displayed. - - {% include - image.html - lightbox="true" - file="/images/applications/edit-app-change-setting.png" - url="/images/applications/edit-app-change-setting.png" - alt="Edit application settings" - caption="Edit application settings" - max-width="70%" - %} - -{:start="4"} -1. Do one of the following: - * To _commit all changes_, click **Commit**. This final commit screen is displayed with a diff view of the changes. - * To _undo all changes_ and return to the previous settings, click **Discard Changes**. This action removes all the changes you have made so far and returns you to the Applications dashboard. - - >If you change settings and then restore existing values for the same, Codefresh automatically removes the Commit and Discard Changes buttons as there are no new changes to commit or discard. - - {% include - image.html - lightbox="true" - file="/images/applications/edit-app-diff-view.png" - url="/images/applications/edit-app-diff-view.png" - alt="Commit changes with diff view" - caption="Commit changes with diff view" - max-width="70%" - %} - -{:start="5"} -1. To confirm all changes, at the bottom-left, click **Commit**. - The changes are committed to Git, and in a few moments also synced to the cluster. - -{::nomarkdown} -
-{:/} - -### Delete an application -Delete an application from Codefresh. Deleting an application deletes the manifest from the Git repository, and then from the cluster where it is deployed. When deleted from the cluster, the application is removed from the Applications dashboard in Codefresh. - ->The Prune resources setting determines the scope of the delete action. When selected, both the application and its resources are deleted. When not selected, only the application is deleted. For more information, review [Sync settings](#sync-settings) in this article. -Codefresh warns you of the implication of deleting the selected application in the Delete form. - -1. In the Codefresh UI, go to the [Applications dashboard](https://g.codefresh.io/2.0/applications-dashboard){:target="\_blank"}. -1. Select the application to delete. -1. Click the three dots for additional actions, and select **Delete**. - - {% include - image.html - lightbox="true" - file="/images/applications/app-delete-option.png" - url="/images/applications/app-delete-option.png" - alt="Delete application" - caption="Delete application" - max-width="80%" - %} - - Pay attention to the impact of the delete action for the selected application that Codefresh displays. - - {% include - image.html - lightbox="true" - file="/images/applications/delete-app-prune-affects.png" - url="/images/applications/delete-app-prune-affects.png" - alt="Prune setting impact on deleting application" - caption="Prune setting impact on deleting application" - max-width="70%" - %} - -{:start="4"} -1. To confirm, click **Commit & Delete**. - -{::nomarkdown} -
-{:/} -### What to read next +### Related articles +[Monitoring applications]({{site.baseurl}})/docs/deployment/applications-dashboard) +[Managing applications]({{site.baseurl}})/docs/deployment/manage-applications) +[Home dashboard]({{site.baseurl}})docs/reporting/home-dashboard) [DORA metrics]({{site.baseurl}}/docs/reporting/dora-metrics/) \ No newline at end of file diff --git a/_docs/deployment/manage-application.md b/_docs/deployment/manage-application.md new file mode 100644 index 00000000..2ccd3e16 --- /dev/null +++ b/_docs/deployment/manage-application.md @@ -0,0 +1,360 @@ +--- +title: "Managing applications" +description: "" +group: deployment +toc: true +--- + +Application creation and deployment is one part of the continuous deployment/delivery process. An equally important part is optimizing deployed applications when needed. + +* [Edit applications](#edit-application-definitions) + Optimize deployed applications by changing application definitions when needed. + +* [Synchronize applications](#manually-synchronize-an-application) + Sync applications on-demand by manually applying sync options or selecting the resources to sync. + + + + +* [Manage rollouts for deployments](#manage-rollouts-for-deployments) + Control ongoing rollouts by resuming indefinitely paused steps, promoting rollouts, aborting, restarting and retrying rollouts. + + + + + +### Edit application definitions +Update General or Advanced configuration settings for a deployed application through the Configuration tab. Once the application is deployed to the cluster, the Configuration tab is available on selecting the application in the Applications dashboard. + +> You cannot change application definitions (the application name and the selected runtime), and the Git Source selected for the application. + +**How to** + +1. In the Codefresh UI, go to the [Applications dashboard](https://g.codefresh.io/2.0/applications-dashboard/list){:target="\_blank"}. +1. Do one of the following: + * Select the application to update, and then from the context menu on the right, select **Edit**. + + * Click the application and then select the **Configuration** tab. + +{% include + image.html + lightbox="true" + file="/images/applications/edit-app-configuration-tab.png" + url="/images/applications/edit-app-configuration-tab.png" + alt="Configuration tab with application settings" + caption="Configuration tab with application settings" + max-width="70%" + %} + +{:start="3"} +1. Update the **General** or **Advanced** configuration settings as needed: + [General configuration]({{site.baseurl}}/docs/deployment/create-application/#application-general-configuration-settings) + [Advanced configuration]({{site.baseurl}}/docs/deployment/create-application/#application-advanced-configuration-settings) + When you change a setting, the Commit and Discard Changes buttons are displayed. + + {% include + image.html + lightbox="true" + file="/images/applications/edit-app-change-setting.png" + url="/images/applications/edit-app-change-setting.png" + alt="Edit application settings" + caption="Edit application settings" + max-width="70%" + %} + +{:start="4"} +1. Do one of the following: + * To _commit all changes_, click **Commit**. This final commit screen is displayed with a diff view of the changes. + * To _undo all changes_ and return to the previous settings, click **Discard Changes**. This action removes all the changes you have made so far and returns you to the Applications dashboard. + + >If you change settings and then restore existing values for the same, Codefresh automatically removes the Commit and Discard Changes buttons as there are no new changes to commit or discard. + + {% include + image.html + lightbox="true" + file="/images/applications/edit-app-diff-view.png" + url="/images/applications/edit-app-diff-view.png" + alt="Commit changes with diff view" + caption="Commit changes with diff view" + max-width="70%" + %} + +{:start="5"} +1. To confirm all changes, at the bottom-left, click **Commit**. + The changes are committed to Git, and in a few moments also synced to the cluster. + +{::nomarkdown} +
+{:/} + +### Manually synchronize an application +Manually synchronize an application to expedite Git-to-cluster sync. The sync options selected for manual sync override the sync options defined for the application. +The sync options, grouped into Revision and Additional Settings, are identical to the Sync options in the General settings when you created the application. + +>You can also synchronize application resources with sync statuses, such as `Service`, `AnalysisTemplate`, and `Rollouts` resources for example, in the Current State tab. The context menu of the resource shows the Sync option. + +**Before you begin** +* Review: + [Revision settings for application sync](#revision-settings-for-application-sync) + [Additional Options for application sync](#additional-options-for-application-sync) + [Synchronize resources](#synchronize-resources) + +**How to** +1. In the Codefresh UI, go to the [Applications dashboard](https://g.codefresh.io/2.0/applications-dashboard/list){:target="\_blank"}. +1. Sync an application: + * Select the application to sync, and do one of the following: + * From the context menu on the right, select **Synchronize**. + * On the top-right, click **Synchronize**. + + Sync a resource: + * Click the application with the resource to sync. + * In the **Current State** tab, open the context menu of the resource, and then select **Sync**. + +1. Select the **Revision** and **Additional Options** for the manual sync. + Review +1. Click **Next**. +1. In the Synchronize Resources form, select the scope of the manual sync: + * To sync only specific resources, search for the resources by any part of their names, or define a Regex to filter by the required resources. + * **All**: Sync all resources regardless of their sync state. + * **Out of sync**: Sync _only_ resources that are `Out of sync`. + +{::nomarkdown} +
+{:/} + +#### Revision settings for application sync +Revision settings determine the behavior for the branch you select. + +**Revision** +The branch in Git to synchronize with the cluster. + +**Prune** +When selected, removes legacy resources from the cluster that do not exist currently in the Git branch. + +**Apply only** +When selected, syncs only those resources in the application that have been changed and are `OutOfSync`, instead of syncing every resource regardless of their state. This option is useful to reduce load and save time when you have thousands of resources in an application. See [Selective Sync](https://argo-cd.readthedocs.io/en/stable/user-guide/sync-options/#selective-sync){:target="\_blank"}. + +**Dry run** +When selected, allows you to preview the application before changes are made to the cluster. + +**Force** +When selected, orphans the dependents of a deleted resource during the sync operation. This option is useful to prevent + +{::nomarkdown} +
+{:/} + +#### Additional Options for application sync + +##### Sync Options + +* **Skip schema validation** + When selected, bypasses validating the YAML schema. +* **Auto-create namespace** + When selected, automatically creates the namespace if the specified namespace does not exist in the cluster. If the namespace already exists, this setting is ignored. +* **Prune last** + When selected, removes those resources that do not exist in the currently deployed version during the final wave of the sync operation. See [Prune last](https://argo-cd.readthedocs.io/en/stable/user-guide/sync-options/#prune-last){:target="\_blank"}. +* **Apply out of sync only** + When selected, syncs only those resources in the application that have been changed and are `OutOfSync`, instead of syncing every resource regardless of their state. This option is useful to reduce load and save time when you have thousands of resources in an application. See [Selective Sync](https://argo-cd.readthedocs.io/en/stable/user-guide/sync-options/#selective-sync){:target="\_blank"}. +* **Respect ignore differences** + When selected, Argo CD omits resources defined for the `spec.ignoreDifferences` attribute from the sync. Otherwise, Argo CD implements the desired state ad-hoc during the sync operation. See [Respect ignore difference configs](https://argo-cd.readthedocs.io/en/stable/user-guide/sync-options/#respect-ignore-difference-configs){:target="\_blank"}. + +##### Prune propagation policy +{::nomarkdown}Defines how resources are pruned, applying Kubernetes cascading deletion prune policies. +Read more at Kubernetes - Cascading deletion.
- Foreground: The default prune propagation policy used by Argo CD. With this policy, Kubernetes changes the state of the owner resource to `deletion in progress`, until the controller deletes the dependent resources and finally the owner resource itself.
- Background: When selected, Kubernetes deletes the owner resource immediately, and then deletes the dependent resources in the background.
- Orphan: When selected, Kubernetes deletes the dependent resources that remain orphaned after the owner resource is deleted.
+{:/} + +#### Synchronize resources +Synchronize Resource options allow you to selectively sync application resources. You can bypass sync settings at the application level, and directly select the resources you want to sync, by state or otherwise. +* All resources regardless of their sync states +* Only out-of-sync resources +* Only selected resources + +By default, Synchronize Resources displays and selects all resources in the application. + + {% include + image.html + lightbox="true" + file="/images/applications/sync-manual-resources-form.png" + url="/images/applications/sync-manual-resources-form.png" + alt="Default settings for Synchronize Resources" + caption="Default settings for Synchronize Resources" + max-width="50%" + %} + +You can search/filter resources using part of the resource names or regex strings, and then select the resources you want to sync. +For example, if you made changes to `api` resources or `audit` resources, type `api` or `audit` to locate the resources and then selectively sync those resources. + + {% include + image.html + lightbox="true" + file="/images/applications/sync-manual-resource-search.png" + url="/images/applications/sync-manual-resource-search.png" + alt="Selective sync in Synchronize Resources" + caption="Selective sync in Synchronize Resources" + max-width="50%" + %} + + +{::nomarkdown} +
+{:/} + + + +### Manage rollouts for deployments +Control ongoing rollouts by resuming indefinitely paused steps, promoting rollouts, aborting, restarting and retrying rollouts. + +{::nomarkdown} +
+{:/} + +#### Pause/resume ongoing rollouts +Pause and resume ongoing rollouts directly from the Timeline tab in the Applications dashboard. +If the rollout is already automatically paused as result of a step definition, this action pauses the rollout even after the pause duration. + + +1. In the Codefresh UI, go to the [Applications dashboard](https://g.codefresh.io/2.0/applications-dashboard/list){:target="\_blank"}. +1. Select the application and go to the Timelines tab. +1. In the deployment record for the ongoing rollout, expand **Updated Services**. +1. Based on the current state of the rollout, click **Pause** or **Resume**, as relevant. + +{% include + image.html + lightbox="true" + file="/images/applications/rollout-resume-indefinite-pause.png" + url="/images/applications/rollout-resume-indefinite-pause.png" + alt="Resume paused rollout" + caption="Resume paused rollout" + max-width="70%" + %} + +{::nomarkdown} +
+{:/} + +#### Manage an ongoing rollout with the Rollout Player +Manage an ongoing rollout using the controls in the Rollout Player to skip steps, and promote rollouts. + +1. In the Codefresh UI, go to the [Applications dashboard](https://g.codefresh.io/2.0/applications-dashboard/list){:target="\_blank"}. +1. Select the application and go to the Timelines tab. +1. In the deployment record for the ongoing rollout, click the name of the rollout. +1. Select the required option in the Rollout Player. + + +{% include +image.html +lightbox="true" +file="/images/applications/rollout-player.png" +url="/images/applications/rollout-player.png" +alt="Rollout Player controls for an ongoing rollout" +caption="Rollout Player controls for an ongoing rollout" +max-width="50%" +%} + + +The table describes the controls in the Rollout Player. + +{: .table .table-bordered .table-hover} +| Rollback player option | Description | +| -------------- | ------------| +| **Rollback** | Not available currently. | +| **Pause** | Pause the rollout. If the rollout is already automatically paused as the result of a step definition, clicking Pause pauses the rollout also after the pause duration. | +| **Resume** | Resume a rollout that was paused either manually by clicking Pause, or automatically through the step's definition. | +| **Skip step** | Skip execution of current step. Such steps are marked as Skipped in the rollout visualization. | +| **Promote full** | Skip all remaining steps, and deploy the current image. | + +{::nomarkdown} +
+{:/} + +#### Manage the `rollout` resource + +Control the rollout through the options available for the Rollout resource. + +1. In the Codefresh UI, go to the [Applications dashboard](https://g.codefresh.io/2.0/applications-dashboard/list){:target="\_blank"}. +1. Select the application and go to the Current State tab. +1. Open the context menu of the `Rollout` resource, and select the relevant option. + +{% include +image.html +lightbox="true" +file="/images/applications/rollout-resource-context-menu.png" +url="/images/applications/rollout-resource-context-menu.png" +alt="Options for `rollout` resource in the Current State tab" +caption="Options for `rollout` resource in the Current State tab" +max-width="50%" +%} + +The table describes the options for the `Rollout` resource. + +{: .table .table-bordered .table-hover} +| Option | Description | +| -------------- | -------------- | +|**Abort** | Terminate the current rollout. | +|**Pause** | Pause the current rollout. | +|**Promote-full** | Promote the current rollout by skipping all remaining stages in the rollout, and deploy the current image. | +|**Restart** | Manually restart the pods of the rollout.| +|**Resume** | Resume a rollout that has been paused. | +|**Retry** | Retry a rollout that has been aborted. Available only when a rollout has been aborted. | +|**Skip-current-step** | Skip executing the current step, and continue with the next step. | + + + + +### Related articles +[Creating applications]({{site.baseurl}}/docs/deployment/create-application) +[Home dashboard]({{site.baseurl}}/docs/reporting/home-dashboard) +[DORA metrics]({{site.baseurl}}/docs/reporting/dora-metrics) + + + + diff --git a/_docs/deployment/sync-application.md b/_docs/deployment/sync-application.md deleted file mode 100644 index 4c70a1d2..00000000 --- a/_docs/deployment/sync-application.md +++ /dev/null @@ -1,68 +0,0 @@ ---- -title: "Manually sync applications" -description: "" -group: deployment -toc: true ---- - -Sync applications directly from the Codefresh UI - -The Synchonuze option si - - -The set of options for application synchronization identical to that of Argo CD. In Codefresh, they are grouped into sets: Revision and Additional Options. - - -### Synchronize application - - -Codefresh groups Synchronization options By - -### Revision settings for application sync -revision - The branch to be checked out when a deployment happens - -Prune: When selected, removes legacy resources that do not exist currently in Git. If pruning is not enforced and Argo CD identifies resources that require pruning, it displays them in the -Read more in [No Prune Resources](https://argo-cd.readthedocs.io/en/stable/user-guide/sync-options/#no-prune-resources){:target="\_blank"}. - -Apply only: When selected, applies Kubernetes sever-side apply with field-management controls for patches and updates. Modifications to fields foChanges to a field of which you are not the manager results by If a new field is created, the new ownCompared to the last-applied annotation managed by kubectl, Server Side Apply uses a more declarative approach, which tracks a user's field management, rather than a user's last applied state. This means that as a side effect of using Server Side Apply, information about which field manager manages each field in an object also becomes available. - -For a user to manage a field, in the Server Side Apply sense, means that the user relies on and expects the value of the field not to change. The user who last made an assertion about the value of a field will be recorded as the current field manager. This can be done either by changing the value with POST, PUT, or non-apply PATCH, or by including the field in a config sent to the Server Side Apply endpoint. When using Server-Side Apply, trying to change a field which is managed by someone else will result in a rejected request (if not forced, see Conflicts). -Read more in instead of the client-side apply. when syncinng the application. We have a use case I don't see discussed much. We leverage mutating webhooks to provide lots of valuable default configuration for our Kubernetes users. An issue with this is that when running kubectl apply, the mutation will not take place if there is no difference between the desired and live states (I believe kubectl doesn't try to apply the patch in this case). However, when running kubectl apply --server-side, the mutations are always applied. - -SSA controls modification right by clarifying field ownership, which can effectively prevent wrong modification. Understanding SSA merge policy and under what circumstances users can modify fields is necessary. - -Whether it is an update or a patch, there will be three circumstances. - -The current manager is the manager of all fields. Then the operation can proceed normally. -The current manager is not the manager of some fields. The current operation can continue if those fields are not modified, and the current manager will be added to the fieldManager of the field as co-manager(sharedmanager). -Modify non-manager fields, and conflicts occur. You can override value by becoming a shared manager or force the modification using--force-conflict. - -Our users primarily interact with Kubernetes through ArgoCD. Without Argo CD supporting server-side apply, there is no way apply these mutations unless the resource actually has some new desired state. - -Dry run: When selected, skips dry run for resources that are not known to the cluster. This option is useful when CRDs for custom resources are not created as part of the sync mechanism, but creatd by other mechanisms. In such cases, Argo CD's default behavior is to automatically fail the sync with the server could not find requested resource error. -Read more in [Skip Dry Run for new custom resource types](https://argo-cd.readthedocs.io/en/stable/user-guide/sync-options/#skip-dry-run-for-new-custom-resources-types){:target="\_blank"}. - -Force -When selected, orphans (deletes??) the dependents of a deleted resource during the sync operation. This option is useful to prevent - -### Additional Options for application sync - -Sync options are described in ???? -Respect ignore differences -When selected, ignore differences between all resources in the applicaion that could not be synced or resolved. -Read more in [Argo CD Diffing Customization](https://argo-cd.readthedocs.io/en/stable/user-guide/diffing/){:target="\_blank"}. - -#### Prune propagation policy -{::nomarkdown}Defines how resources are pruned, applying Kubernetes cascading deletion prune policies. -Read more at Kubernetes - Cascading deletion.
- Foreground: The default prune propagation policy used by Argo CD. With this policy, Kubernetes changes the state of the owner resource to `deletion in progress`, until the controller deletes the dependent resources and finally the owner resource itself.
- Background: When selected, Kubernetes deletes the owner resource immediately, and then deletes the dependent resources in the background.
- Orphan: When selected, Kubernetes deletes the dependent resources that remain orphaned after the owner resource is deleted.
diff --git a/_docs/incubation/intro-hosted-runtime.md b/_docs/incubation/intro-hosted-runtime.md index ed1e2dfb..c2a66b69 100644 --- a/_docs/incubation/intro-hosted-runtime.md +++ b/_docs/incubation/intro-hosted-runtime.md @@ -51,7 +51,7 @@ Get insights into important KPIs and deployments, across runtimes and clusters, The Applications dashboard displays applications across runtimes and clusters, from which you can select and analyze individual applications. Individual application information is grouped by current and historical deployments, enriched with Argo, Jira, and Git details, including rollout visualizations for ongoing deployments (Timeline tab), and an interactive tree view of application resources (Current State tab). -See [Applications dashboard]({{site.baseurl}}/docs/deployment/applications-dashboard/). +See [Monitoring applications]({{site.baseurl}}/docs/deployment/applications-dashboard/). {% include image.html diff --git a/_docs/integrations/container-registries.md b/_docs/integrations/container-registries.md index 5702f861..2aef4ac1 100644 --- a/_docs/integrations/container-registries.md +++ b/_docs/integrations/container-registries.md @@ -87,5 +87,5 @@ use it. [Issue-tracking integrations]({{site.baseurl}}/docs/integrations/issue-tracking/) [Shared configuration repo]({{site.baseurl}}/docs/reference/shared-configuration/) [Images]({{site.baseurl}}/docs/deployment/images/) -[Applications dashboard]({{site.baseurl}}/docs/deployment/applications-dashboard/) +[Monitoring applications]({{site.baseurl}}/docs/deployment/applications-dashboard/) [Add Git sources to runtimes]({{site.baseurl}}/docs/runtime/git-sources/) diff --git a/_docs/reporting/dora-metrics.md b/_docs/reporting/dora-metrics.md index f6bbcbca..f0d848aa 100644 --- a/_docs/reporting/dora-metrics.md +++ b/_docs/reporting/dora-metrics.md @@ -46,7 +46,7 @@ More than one option within the same filter type has an OR relationship. More th > When no filters are defined, all metrics are shown for the last 90 days. ### Metrics for favorite applications -If you have [starred applications as favorites]({{site.baseurl}}/docs/deployment/applications-dashboard/#filters-and-favorites) in the Applications dashboard, clicking {::nomarkdown}
{:/} in DORA metrics, displays metrics only for those applications.
+If you have [starred applications as favorites]({{site.baseurl}}/docs/deployment/applications-dashboard/#applications-dashboard-information) in the Applications dashboard, clicking {::nomarkdown}{:/} in DORA metrics, displays metrics only for those applications.
### Metric totals
@@ -82,5 +82,5 @@ In addition, you can select the granularity for each graph:
## What to read next
[Codefresh architecture]({{site.baseurl}}/docs/getting-started/architecture/)
-[Applications dashboard]({{site.baseurl}}/docs/deployment/applications-dashboard/)
+[Monitoring applications]({{site.baseurl}}/docs/deployment/applications-dashboard/)
diff --git a/_docs/reporting/home-dashboard.md b/_docs/reporting/home-dashboard.md
index 2307a992..c3a402c0 100644
--- a/_docs/reporting/home-dashboard.md
+++ b/_docs/reporting/home-dashboard.md
@@ -136,7 +136,7 @@ Analytics are derived by comparing the selected date range to the corresponding
### Related articles
[DORA metrics]({{site.baseurl}}/docs/reporting/dora-metrics/)
-[Applications dashboard]({{site.baseurl}}/docs/deployment/applications-dashboard/)
+[Monitoring applications]({{site.baseurl}}/docs/deployment/applications-dashboard/)
[Images in Codefresh]({{site.baseurl}}/docs/deployment/images/)
diff --git a/_docs/whats-new/whats-new.md b/_docs/whats-new/whats-new.md
index 54596238..a2430915 100644
--- a/_docs/whats-new/whats-new.md
+++ b/_docs/whats-new/whats-new.md
@@ -336,7 +336,7 @@ Logs are displayed if the resource has logs:
* For online viewing, you have free-text search and line-wrap functionalities.
* For offline viewing and analysis, you can download the complete log into a text file.
-For details, see [Current State Tree view]({{site.baseurl}}/docs/deployment/applications-dashboard/#current-state-tree-view).
+For details, see [Current State Tree view]({{site.baseurl}}/docs/deployment/applications-dashboard/view-modes-for-application-resources/#working-with-resources-in-tree-view).
#### Application rollout visualization
In addition to installing Argo Rollouts in your cluster, visualize Argo Rollout history and progress directly in the Applications (deployment) dashboard. Visualize rollouts from multiple clusters and runtimes in a single centralized location through the Deployment tab.
@@ -375,7 +375,7 @@ As the rollout occurs, visualize step-by-step progress. Expanding Background Ana
max-width="30%"
%}
-For details, see [Rollout progress and step visualization]({{site.baseurl}}/docs/deployment/applications-dashboard/#rollout-progress-visualization).
+For details, see [Rollout progress and step visualization]({{site.baseurl}}/docs/deployment/applications-dashboard/#monitor-rollouts-by-deployment).
#### Nested workflows
Add nested workflow functionality to Codefresh pipelines. A nested workflow is a step within the parent workflow that either submits a new workflow, or creates a PR (Pull Request) that runs a different workflow based on the PR result.
diff --git a/images/applications/app-dashboard-card-view.png b/images/applications/app-dashboard-card-view.png
new file mode 100644
index 00000000..bbc57d3c
Binary files /dev/null and b/images/applications/app-dashboard-card-view.png differ
diff --git a/images/applications/app-dashboard-errors.png b/images/applications/app-dashboard-errors.png
index 728a7092..e32b74b3 100644
Binary files a/images/applications/app-dashboard-errors.png and b/images/applications/app-dashboard-errors.png differ
diff --git a/images/applications/app-dashboard-favorite.png b/images/applications/app-dashboard-favorite.png
new file mode 100644
index 00000000..91e7f173
Binary files /dev/null and b/images/applications/app-dashboard-favorite.png differ
diff --git a/images/applications/app-header-health-sync-status.png b/images/applications/app-header-health-sync-status.png
new file mode 100644
index 00000000..abdad3c0
Binary files /dev/null and b/images/applications/app-header-health-sync-status.png differ
diff --git a/images/applications/app-header-sync-details.png b/images/applications/app-header-sync-details.png
new file mode 100644
index 00000000..fc085780
Binary files /dev/null and b/images/applications/app-header-sync-details.png differ
diff --git a/images/applications/app-header-view-details.png b/images/applications/app-header-view-details.png
new file mode 100644
index 00000000..5d250a16
Binary files /dev/null and b/images/applications/app-header-view-details.png differ
diff --git a/images/applications/app-resources-monitor-screen.png b/images/applications/app-resources-monitor-screen.png
new file mode 100644
index 00000000..02f394ce
Binary files /dev/null and b/images/applications/app-resources-monitor-screen.png differ
diff --git a/images/applications/app-rollout-analysis-template-step.png b/images/applications/app-rollout-analysis-template-step.png
new file mode 100644
index 00000000..e77307d8
Binary files /dev/null and b/images/applications/app-rollout-analysis-template-step.png differ
diff --git a/images/applications/app-rollout-run-results-manifest.png b/images/applications/app-rollout-run-results-manifest.png
new file mode 100644
index 00000000..a293d65b
Binary files /dev/null and b/images/applications/app-rollout-run-results-manifest.png differ
diff --git a/images/applications/apps-git-source-app.png b/images/applications/apps-git-source-app.png
new file mode 100644
index 00000000..ad51689d
Binary files /dev/null and b/images/applications/apps-git-source-app.png differ
diff --git a/images/applications/current-state-resource-context-menu.png b/images/applications/current-state-resource-context-menu.png
new file mode 100644
index 00000000..0291029a
Binary files /dev/null and b/images/applications/current-state-resource-context-menu.png differ
diff --git a/images/applications/dashboard-views.png b/images/applications/dashboard-views.png
new file mode 100644
index 00000000..0464007a
Binary files /dev/null and b/images/applications/dashboard-views.png differ
diff --git a/images/applications/rollout-player.png b/images/applications/rollout-player.png
new file mode 100644
index 00000000..1e01193c
Binary files /dev/null and b/images/applications/rollout-player.png differ
diff --git a/images/applications/rollout-resource-context-menu.png b/images/applications/rollout-resource-context-menu.png
new file mode 100644
index 00000000..c05a3de7
Binary files /dev/null and b/images/applications/rollout-resource-context-menu.png differ
diff --git a/images/applications/rollout-resume-indefinite-pause.png b/images/applications/rollout-resume-indefinite-pause.png
new file mode 100644
index 00000000..f645d334
Binary files /dev/null and b/images/applications/rollout-resume-indefinite-pause.png differ
diff --git a/images/applications/sync-manual-resource-search.png b/images/applications/sync-manual-resource-search.png
new file mode 100644
index 00000000..83f89566
Binary files /dev/null and b/images/applications/sync-manual-resource-search.png differ
diff --git a/images/applications/sync-manual-resources-form.png b/images/applications/sync-manual-resources-form.png
new file mode 100644
index 00000000..5a8c2edf
Binary files /dev/null and b/images/applications/sync-manual-resources-form.png differ
diff --git a/images/applications/timeline-resources-compact-view.png b/images/applications/timeline-resources-compact-view.png
new file mode 100644
index 00000000..a48b261b
Binary files /dev/null and b/images/applications/timeline-resources-compact-view.png differ
diff --git a/images/applications/timeline-resources-full-view.png b/images/applications/timeline-resources-full-view.png
new file mode 100644
index 00000000..a890c673
Binary files /dev/null and b/images/applications/timeline-resources-full-view.png differ
diff --git a/images/applications/timeline-resources-updated.png b/images/applications/timeline-resources-updated.png
new file mode 100644
index 00000000..bcadf2e6
Binary files /dev/null and b/images/applications/timeline-resources-updated.png differ
diff --git a/images/icons/rollout-promote-full.png b/images/icons/rollout-promote-full.png
new file mode 100644
index 00000000..8c147d1d
Binary files /dev/null and b/images/icons/rollout-promote-full.png differ
diff --git a/images/icons/rollout-resume-indefinite-pause.png b/images/icons/rollout-resume-indefinite-pause.png
new file mode 100644
index 00000000..a9de8168
Binary files /dev/null and b/images/icons/rollout-resume-indefinite-pause.png differ
diff --git a/images/icons/rollout-resume.png b/images/icons/rollout-resume.png
new file mode 100644
index 00000000..ea75d24a
Binary files /dev/null and b/images/icons/rollout-resume.png differ
diff --git a/images/icons/rollout-skip-step.png b/images/icons/rollout-skip-step.png
new file mode 100644
index 00000000..23323228
Binary files /dev/null and b/images/icons/rollout-skip-step.png differ