Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: authorise kargo to argocd-update #2962

Merged
merged 4 commits into from
Nov 21, 2024

Conversation

fykaa
Copy link
Contributor

@fykaa fykaa commented Nov 19, 2024

Signed-off-by: Faeka Ansari <faeka6@gmail.com>
@fykaa fykaa self-assigned this Nov 19, 2024
@fykaa fykaa requested review from a team as code owners November 19, 2024 05:46
Copy link

netlify bot commented Nov 19, 2024

Deploy Preview for docs-kargo-io ready!

Name Link
🔨 Latest commit c462695
🔍 Latest deploy log https://app.netlify.com/sites/docs-kargo-io/deploys/673e6cce7b00630008557e35
😎 Deploy Preview https://deploy-preview-2962.docs.kargo.io
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link

codecov bot commented Nov 19, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 50.90%. Comparing base (34c6128) to head (c462695).
Report is 9 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2962      +/-   ##
==========================================
- Coverage   50.92%   50.90%   -0.02%     
==========================================
  Files         279      279              
  Lines       25180    25178       -2     
==========================================
- Hits        12823    12818       -5     
- Misses      11666    11669       +3     
  Partials      691      691              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.


🚨 Try these New Features:

@@ -1156,3 +1156,34 @@ Although the `argocd-update` step is the only promotion step to currently
utilize this health check framework, we anticipate that future built-in and
third-party promotion steps will take advantage of it as well.
:::

### Authorizing Kargo to Update Argo CD Applications
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Given the importance of this information, I think this should be up higher and I wouldn't give it its own section either. If we put it in a note box at the end of the section that first introduces this step (i.e. line 988), it will be much harder to miss this.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Understood!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

addressed in c715095

Signed-off-by: Faeka Ansari <faeka6@gmail.com>
Comment on lines 989 to 1014
:::note
For Kargo `Stage`s to modify and manage Argo CD `Application` resources,
explicit authorization must be granted in the `Application` manifests.
This is achieved by including the `kargo.akuity.io/authorized-stage` annotation.

The annotation must be formatted as follows:

```yaml
kargo.akuity.io/authorized-stage: "<project-name>:<stage-name>"
```

The following example shows how to configure an Argo CD `Application`
manifest to authorize the `test` `Stage` of the `kargo-demo` `Project`:

```yaml
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: kargo-demo-test
namespace: argocd
annotations:
kargo.akuity.io/authorized-stage: kargo-demo:test
spec:
# Application specifications go here
```
:::
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Formatting looks off on this entire block.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I should remove the indentations

Signed-off-by: Faeka Ansari <faeka6@gmail.com>
@krancour krancour added this to the Live Docs milestone Nov 20, 2024
Signed-off-by: Faeka Ansari <faeka6@gmail.com>
@fykaa fykaa force-pushed the docs/update-authorized-stage-annotation branch from 93feffe to c462695 Compare November 20, 2024 23:12
@krancour krancour added this pull request to the merge queue Nov 21, 2024
Merged via the queue into akuity:main with commit 7f92d75 Nov 21, 2024
24 of 25 checks passed
github-actions bot pushed a commit that referenced this pull request Nov 21, 2024
Signed-off-by: Faeka Ansari <faeka6@gmail.com>
(cherry picked from commit 7f92d75)
@akuitybot
Copy link

Successfully created backport PR for release-1.0:

fykaa added a commit to fykaa/kargo that referenced this pull request Dec 20, 2024
Signed-off-by: Faeka Ansari <faeka6@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

docs: need to document the kargo.akuity.io/authorized-stage annotation
3 participants