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

Pull-based "GitOps" deployments of Radius using ArgoCD #8078

Open
1 task
Tracked by #46
willtsai opened this issue Nov 22, 2024 · 3 comments
Open
1 task
Tracked by #46

Pull-based "GitOps" deployments of Radius using ArgoCD #8078

willtsai opened this issue Nov 22, 2024 · 3 comments
Labels
feature This issue describes a feature request in Radius triaged This issue has been reviewed and triaged

Comments

@willtsai
Copy link
Contributor

willtsai commented Nov 22, 2024

Overview of feature request

Scenario

I want to be able to treat my git repository as my "source of truth", where I check in my app templates, and then my cluster "picks up" the new app template to get it deployed via integration with ArgoCD

Note that there the deployment occurs when the cluster looks for the app definition and uses that, instead of a service reaching out to the cluster to deploy the app.

Acceptance criteria

Proposal

We should see if we can either leverage flux for Radius applications or see if not, create a feature in UCP/DE that allows for pull-based deployments

End result

I am an application developer using Radius. I push an update of my app's definition (in Bicep) to a git repository. After some amount of time my Radius environment picks up the new application definition and applies it.

Additional context

Feature spec here: https://github.com/willtsai/design-notes-radius/blob/main/tools/2024-06-gitops-feature-spec.md

Would you like to support us?

  • Yes, I would like to support you

AB#13743

@willtsai willtsai added triaged This issue has been reviewed and triaged feature This issue describes a feature request in Radius labels Nov 22, 2024
@radius-triage-bot
Copy link

👍 We've reviewed this issue and have agreed to add it to our backlog. Please subscribe to this issue for notifications, we'll provide updates when we pick it up.

We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.

For more information on our triage process please visit our triage overview

@radius-triage-bot
Copy link

👋 @willtsai Thanks for filing this feature request.

A project maintainer will review this feature request and get back to you soon.

We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.

For more information on our triage process please visit our triage overview

@ytimocin ytimocin added triaged This issue has been reviewed and triaged and removed triaged This issue has been reviewed and triaged labels Nov 25, 2024
@radius-triage-bot
Copy link

👍 We've reviewed this issue and have agreed to add it to our backlog. Please subscribe to this issue for notifications, we'll provide updates when we pick it up.

We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.

For more information on our triage process please visit our triage overview

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature This issue describes a feature request in Radius triaged This issue has been reviewed and triaged
Projects
None yet
Development

No branches or pull requests

2 participants