-
Notifications
You must be signed in to change notification settings - Fork 8
chore: remove argo-events controller from gitops-runtime helm chart #1057
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
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Argo Events was deprecated in 0.26.0 with resources removed but controller retained for cleanup. This commit completes the removal by: - Removing argo-events dependency from Chart.yaml - Removing argo-events configuration from values.yaml - Removing argo-events from multi-runtime values files - Removing argo-events helper function and component-list entry from _helpers.tpl - Removing argo-events from test files - Updating README documentation to remove argo-events sections - Deleting argo-events CRDs from crds/ directory ## Breaking Changes ### 1. Argo Events Controller Removed **The Argo Events controller has been completely removed from this release.** In release 0.26.0, Argo Events was deprecated and all Argo Events resources (EventBus, EventSource, Sensor) were removed. The controller was kept temporarily to facilitate cleanup of existing resources. **CRITICAL UPGRADE REQUIREMENT:** - You **MUST** upgrade to version 0.26.x before upgrading to 0.27.0 or higher - This ensures that any existing Argo Events resources are properly cleaned up by the controller before it is removed - Upgrading directly from versions prior to 0.26.0 to 0.27.0+ may leave orphaned Argo Events resources in your cluster **If you skipped 0.26.x:** 1. Manually delete any remaining EventBus, EventSource, and Sensor resources 2. Manually delete the Argo Events CRDs if no longer needed 3. Then proceed with the upgrade to 0.27.0+ **Replacement:** Event reporting functionality has been replaced by: - `runtime-event-reporter` component - `cluster-event-reporter` component
19c39a4 to
09be906
Compare
Contributor
Author
|
/e2e |
mikhail-klimko
approved these changes
Jan 22, 2026
eti-codefresh
approved these changes
Jan 22, 2026
dmaizel
added a commit
that referenced
this pull request
Jan 22, 2026
…1057) Argo Events was deprecated in 0.26.0 with resources removed but controller retained for cleanup. This commit completes the removal by: - Removing argo-events dependency from Chart.yaml - Removing argo-events configuration from values.yaml - Removing argo-events from multi-runtime values files - Removing argo-events helper function and component-list entry from _helpers.tpl - Removing argo-events from test files - Updating README documentation to remove argo-events sections - Deleting argo-events CRDs from crds/ directory ## Breaking Changes ### 1. Argo Events Controller Removed **The Argo Events controller has been completely removed from this release.** In release 0.26.0, Argo Events was deprecated and all Argo Events resources (EventBus, EventSource, Sensor) were removed. The controller was kept temporarily to facilitate cleanup of existing resources. **CRITICAL UPGRADE REQUIREMENT:** - You **MUST** upgrade to version 0.26.x before upgrading to 0.27.0 or higher - This ensures that any existing Argo Events resources are properly cleaned up by the controller before it is removed - Upgrading directly from versions prior to 0.26.0 to 0.27.0+ may leave orphaned Argo Events resources in your cluster **If you skipped 0.26.x:** 1. Manually delete any remaining EventBus, EventSource, and Sensor resources 2. Manually delete the Argo Events CRDs if no longer needed 3. Then proceed with the upgrade to 0.27.0+ **Replacement:** Event reporting functionality has been replaced by: - `runtime-event-reporter` component - `cluster-event-reporter` component
This was referenced Jan 22, 2026
dmaizel
added a commit
that referenced
this pull request
Jan 22, 2026
* chore: remove argo-events controller from gitops-runtime helm chart (#1057) Argo Events was deprecated in 0.26.0 with resources removed but controller retained for cleanup. This commit completes the removal by: - Removing argo-events dependency from Chart.yaml - Removing argo-events configuration from values.yaml - Removing argo-events from multi-runtime values files - Removing argo-events helper function and component-list entry from _helpers.tpl - Removing argo-events from test files - Updating README documentation to remove argo-events sections - Deleting argo-events CRDs from crds/ directory ## Breaking Changes ### 1. Argo Events Controller Removed **The Argo Events controller has been completely removed from this release.** In release 0.26.0, Argo Events was deprecated and all Argo Events resources (EventBus, EventSource, Sensor) were removed. The controller was kept temporarily to facilitate cleanup of existing resources. **CRITICAL UPGRADE REQUIREMENT:** - You **MUST** upgrade to version 0.26.x before upgrading to 0.27.0 or higher - This ensures that any existing Argo Events resources are properly cleaned up by the controller before it is removed - Upgrading directly from versions prior to 0.26.0 to 0.27.0+ may leave orphaned Argo Events resources in your cluster **If you skipped 0.26.x:** 1. Manually delete any remaining EventBus, EventSource, and Sensor resources 2. Manually delete the Argo Events CRDs if no longer needed 3. Then proceed with the upgrade to 0.27.0+ **Replacement:** Event reporting functionality has been replaced by: - `runtime-event-reporter` component - `cluster-event-reporter` component * CI Automatic commit - align Chart version --------- Co-authored-by: cf-ci-bot-v2 <cf-ci-bot-v2@codefresh.io>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Breaking Change
CRITICAL UPGRADE REQUIREMENT:
Changes
Chart.yamlvalues.yamlvalues-multi-runtimes.yaml_helpers.tplcrds/directoryTest plan
helm lintpasseshelm unittest- all 168 tests passhelm templategenerates no argo-events resourceshelm dependency listshows argo-events removed