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/create-application.md
+9-1Lines changed: 9 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,7 @@ Application definitions include the name, runtime, and the name of the YAML mani
38
38
39
39
## Application: General configuration settings
40
40
41
-
General configuration settings define the source, destination, and sync policies for the application.
41
+
General configuration settings define the group to which the application belongs, source, destination, and sync policies for the application.
42
42
43
43
{% include
44
44
image.html
@@ -50,6 +50,14 @@ General configuration settings define the source, destination, and sync policies
50
50
max-width="70%"
51
51
%}
52
52
53
+
<!--- ### Groups
54
+
Optional. The group or groups to which to add the application.
55
+
You can group applications based on criteria meaningful to your organization, such as environment, region, or any other relevant attribute. You can then view deployments for these applications in the same location in the Groups tab of the GitOps Apps dashboard. A new view for GitOps Application, App Groups allow you to collate multiple applications view their timelines.
56
+
57
+
Select an existing group, or create a new application group by typing a name and pressing Enter.
58
+
59
+
-->
60
+
53
61
### Source
54
62
The Git repository to be tracked for changes to the application's source code.
55
63
{::nomarkdown}<ul> <li><b>Repository URL</b>: The Git repo or the Helm package repo with the application source code, to be tracked for changes. <br>If SSH is configured for the runtime, you can connect to the repo with either HTTPS or SSH. On selecting the repository, Codefresh automatically updates the URL format. See <a href="https://codefresh.io/docs/docs/installation/gitops/monitor-manage-runtimes/#configure-ssh-for-gitops-runtimes">Configure SSH for runtimes</a>.<br>If the Argo CD project is not the <span style="font-family: var(--font-family-monospace); font-size: 87.5%; color: #ad6800; background-color: #fffbe6">default</span> project, make sure that the repo has the correct access roles for your application.<ul><li><b>Revision and Path</b>: Applies to Git repositories. </li><li><b>Chart</b>: Applies to Helm repositories. The name of the Helm package with all the resource definitions for the application, and the version. </li></ul>For more information, see <a href="https://argo-cd.readthedocs.io/en/stable/user-guide/tracking_strategies/" target="\_blank">Tracking and Deployment Strategies</a>.</li></ul> {:/}
Delete unused or legacy applications to avoid clutter and remove unnecessary resources.
26
31
32
+
To delete specific resources within an application, see [Delete application resources]({{site.baseurl}}/docs/deployments/gitops/applications-dashboard/#delete-application-resources).
33
+
27
34
28
35
29
36
@@ -95,11 +102,13 @@ Update General or Advanced configuration settings for a deployed application thr
95
102
96
103
97
104
105
+
98
106
## Manually synchronize an application
99
107
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.
100
108
The sync options, grouped into Revision and Additional Settings, are identical to the Sync options in the General settings when you created the application.
101
109
102
-
>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.
110
+
>**TIP**:
111
+
You can also synchronize _application resources_ with sync statuses such as `Service`, `AnalysisTemplate`, and `Rollouts` resources for example, in the Current State tab. Select the Sync option from resource's context menu.
103
112
104
113
**Before you begin**
105
114
* Review:
@@ -222,6 +231,45 @@ For example, if you made changes to `api` resources or `audit` resources, type `
222
231
<br><br>
223
232
{:/}
224
233
234
+
235
+
## Terminate on-going sync for GitOps applications
236
+
Manually terminate an on-going synchronization process for the application. You may need to terminate an on-going sync that remains indefinitely as Syncing, or because you have detected problems in the current deployment
237
+
Terminating a sync operation reverts the deployment to the previously deployed version or image.
238
+
239
+
1. In the Codefresh UI, from Ops in the sidebar, select [GitOps Apps](https://g.codefresh.io/2.0/applications-dashboard/list){:target="\_blank"}.
240
+
1. If needed, filter by **Status****Syncing** to view applications with active sync operations.
241
+
1. Select the application and then from the application header, click **Terminate Sync**.
As an alternative to manually syncing an application, either refresh or hard refresh the application. Both options are always available in the application toolbar.
257
+
258
+
1. In the Codefresh UI, from Ops in the sidebar, select [GitOps Apps](https://g.codefresh.io/2.0/applications-dashboard/list){:target="\_blank"}.
259
+
1. Select the application, and then from the top-right, select the required action:
260
+
***Refresh**: Retrieve desired (Git) state, compare with the live (cluster) state, and refresh the application to sync with the desired state.
261
+
***Hard Refresh**: Refresh the application to sync with the Git state, while removing the cache.
Rollback to a previously deployed version of active GitOps applications. You may want to rollback a newly deployed version due to errors in your code or misconfigurations, etc.
227
275
@@ -316,7 +364,7 @@ caption="Rollback completed for application"
316
364
max-width="70%"
317
365
%}
318
366
319
-
## Manage rollouts for deployments
367
+
## Manage rollouts for GitOps application deployments
320
368
Control ongoing rollouts by resuming indefinitely paused steps, promoting rollouts, aborting, restarting and retrying rollouts.
321
369
322
370
{::nomarkdown}
@@ -426,7 +474,7 @@ The table describes the options for the `Rollout` resource.
426
474
|**Retry**| Retry a rollout that has been aborted. Available only when a rollout has been aborted. |
427
475
|**Skip-current-step**| Skip executing the current step, and continue with the next step. |
428
476
429
-
## Delete an application
477
+
## Delete GitOps applications
430
478
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 GitOps Apps dashboard in Codefresh.
431
479
432
480
>**Prune resources** in the application's General settings determines the scope of the delete action.
0 commit comments