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

feat(argo-workflows): Support workflowEvent configuration to Argo Workflow Controller #3115

Merged
merged 2 commits into from
Jan 10, 2025

Conversation

crileroro
Copy link
Contributor

@crileroro crileroro commented Jan 9, 2025

Checklist:

  • I have bumped the chart version according to versioning
  • I have updated the documentation according to documentation
  • I have updated the chart changelog with all the changes that come with this pull request according to changelog.
  • Any new values are backwards compatible and/or have sensible default.
  • I have signed off all my commits as required by DCO.
  • My build is green (troubleshooting builds).

@crileroro crileroro changed the title Support workflowEvent configuration to Argo Workflow Controller chore(argo-workflows): Support workflowEvent configuration to Argo Workflow Controller Jan 9, 2025
@crileroro crileroro changed the title chore(argo-workflows): Support workflowEvent configuration to Argo Workflow Controller feat(argo-workflows): Support workflowEvent configuration to Argo Workflow Controller Jan 9, 2025
Signed-off-by: Cristhian Roa <cristhian.roa@constellr.com>
@crileroro crileroro force-pushed the feat/add-workflow-event-options branch from 67c415d to 52ccb43 Compare January 9, 2025 17:08
@github-actions github-actions bot added the size/S label Jan 9, 2025
# -- Enable to emit events on workflow status changes.
## This can take up a lot of space in k8s (typically etcd), resulting in errors when trying to create new events:
## "Unable to create audit event: etcdserver: mvcc: database space exceeded"
enabled: true
Copy link
Collaborator

Choose a reason for hiding this comment

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

I think it's reasonable to set as false for existing users to reduce unexpected effects. 🤔

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Isn't it already enable for existing users? Looking at previous Argo Workflows versions (e.g., v.3.5.*,v.3.4.*, v.3.3*) , workflow events have been enabled by default like in version v.3.5.13.
PR argoproj/argo-workflows#13746 adds support to toggle workflowEvents. I set the default to true to not affect previous versions

Copy link
Collaborator

Choose a reason for hiding this comment

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

Thank you for the info, I didn't know that the default is true . then LGTM.

@yu-croco yu-croco enabled auto-merge (squash) January 10, 2025 10:18
@yu-croco yu-croco merged commit 23b484d into argoproj:main Jan 10, 2025
6 checks passed
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.

3 participants