Upgrade Flux to 2.4.x - #386

Files that changed from the base of the PR and between 929ab5c and f2f7288.

• packages/system/fluxcd/values.yaml (1 hunks)

packages/system/fluxcd/values.yaml (5)

7-7: Flux version updated to 2.4.x

This change aligns with the PR objective to upgrade Flux to version 2.4.0. Using 2.4.x instead of 2.4.0 allows for minor version updates within the 2.4 series, which is a good practice for maintaining up-to-date dependencies.

Please ensure that all components and configurations are compatible with Flux 2.4.x. You can verify this by checking the Flux documentation for any breaking changes or new features that might affect your setup.

---

Line range hint 1-47: Overall assessment of Flux upgrade and configuration changes

This PR successfully upgrades Flux to version 2.4.x and introduces several important configuration changes:

1. Increased concurrency and shorter requeue intervals for faster reconciliations.
2. Adjusted resource limits to accommodate the new settings.
3. Improved integration between controllers and the notification system for better observability.

These changes align well with the PR objective and should enhance the performance and functionality of your Flux setup. However, given the scope of the changes, I recommend the following steps:

1. Thoroughly test these changes in a staging environment that closely mirrors your production setup.
2. Monitor system performance, resource usage, and stability closely after deployment.
3. Be prepared to fine-tune the configuration (especially concurrency and resource limits) based on observed behavior in your specific environment.
4. Ensure your team is familiar with the new Flux version and any new features or breaking changes it might introduce.
5. Update any related documentation or runbooks to reflect these changes.

Great work on this upgrade! These improvements should provide a more robust and observable Flux system for your Cozystack users.

---

Line range hint 18-33: Performance tuning and resource allocation changes

The changes to kustomize-controller, helm-controller, and source-controller include:

1. Increased concurrency (--concurrent=20)
2. Shorter requeue interval for dependencies (--requeue-dependency=5s)
3. Significantly increased resource limits (CPU: 2000m, Memory: 2048Mi)

These changes aim to improve performance but may have implications:

• Higher concurrency could lead to faster reconciliations but increased resource usage.
• Shorter requeue interval might result in quicker updates but increased system load.
• The substantial increase in resource limits might be necessary for the new settings but could put pressure on cluster resources.

Please ensure you:

1. Test these changes thoroughly in a staging environment.
2. Monitor the performance and resource usage closely after deployment.
3. Be prepared to adjust these values if you observe any negative impacts on system stability or other workloads.

Run the following command to check the current resource usage of these controllers:

kubectl top pods -n cozy-fluxcd | grep -E '(kustomize-controller|helm-controller|source-controller)'

Compare the output with the new limits to ensure they are appropriate.

---

Line range hint 34-41: Enhanced configuration for source-controller

The addition of --storage-adv-addr and --events-addr arguments to the source-controller improves its integration with other Flux components:

1. --storage-adv-addr=source-controller.cozy-fluxcd.svc: This sets the advertised storage address, crucial for proper service discovery.
2. --events-addr=http://notification-controller.cozy-fluxcd.svc/: This configures the controller to send events to the notification-controller, enhancing observability.

Please ensure that:

1. The service names (source-controller, notification-controller) are correct.
2. The namespace (cozy-fluxcd) is correct for your setup.

You can verify the existence of these services with:

kubectl get services -n cozy-fluxcd | grep -E '(source-controller|notification-controller)'

Also, check that the notification-controller is properly configured to receive events.

---

Line range hint 42-47: Consistent event configuration across controllers

The addition of --events-addr=http://notification-controller.cozy-fluxcd.svc/ to kustomize-controller, helm-controller, image-reflector-controller, and image-automation-controller is a positive change:

• It ensures all controllers send events to the notification-controller, enhancing system-wide observability.
• The consistent configuration across controllers is a good practice for maintainability.

To ensure this configuration works as intended:

1. Verify that the notification-controller is properly set up and running.
2. Check that it's configured to handle incoming events from multiple sources.

Run the following command to check the status of the notification-controller:

Also, review the notification-controller logs after applying these changes to ensure it's receiving events from all controllers:

Look for log entries indicating received events from various controllers.