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

Argo Workflow to know when a new chart has been deployed by Argo CD #1802

Open
1 of 2 tasks
fharper opened this issue Sep 6, 2023 · 1 comment
Open
1 of 2 tasks
Labels
feature Something new

Comments

@fharper
Copy link
Contributor

fharper commented Sep 6, 2023

What is your feature idea?

I would like to have an Argo Workflow that one can use to know if a new application version has been synced by Argo CD, and the most important, published, and running.

Why is it needed?

It will be helpful to automate execution of actions that need to happen once a new application version has been deployed, and running. My personal use case is to be able to run the TypeSense scraper once a new documentation version is up, and running in production, but I would see multiple usage for something like this by our users.

Is this missing feature preventing you from using kubefirst?

  • Yes

Code of Conduct

  • I agree to follow this project's Code of Conduct
@fharper fharper added the feature Something new label Sep 6, 2023
@alechp
Copy link

alechp commented Sep 12, 2023

Loosely related Argo/Chart issue:

#1801 (comment)
#1801 (comment)

TLDR:

  • Need to update github action workflows so that Chart URI includes generated --cluster-name as opposed to environment (ie. development, staging, production)
  • After updating these manually, creates derivative issue where Chart museum fails on release because it says chart already exists (if you try updating the workflow)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Something new
Projects
None yet
Development

No branches or pull requests

2 participants