Skip to content

Conversation

@cappyzawa
Copy link
Member

@cappyzawa cappyzawa force-pushed the feat/bucket-controller-runtime-secrets-migration branch from 410ee9f to ebf1405 Compare July 22, 2025 16:56
@cappyzawa
Copy link
Member Author

This PR applies the same TLS configuration updates that were implemented in #1855 and #1856.

The Bucket controller now uses secrets.WithSystemCertPool() to maintain the existing "extend mode" behavior (system CAs + user CA) while following the updated API patterns established in the other controllers.

Replaces internal credential management with runtime/secrets package
to standardize authentication, proxy configuration, and TLS handling
across controllers. This migration eliminates code duplication by
leveraging shared utilities and improves maintainability through
consistent error handling patterns.

The refactoring splits the large reconcileSource method into focused
helper functions for better separation of concerns.

Signed-off-by: cappyzawa <[email protected]>
Include namespace in secret error message for better debugging context.
The secret name was already present in the error, but namespace information
was missing, making it harder to identify which secret in which namespace
was not found.

Signed-off-by: cappyzawa <[email protected]>
@cappyzawa cappyzawa force-pushed the feat/bucket-controller-runtime-secrets-migration branch from 51cb0e0 to 9463bcf Compare July 31, 2025 13:05
Copy link
Member

@matheuscscp matheuscscp left a comment

Choose a reason for hiding this comment

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

LGTM! 🚀

Copy link
Member

@stefanprodan stefanprodan left a comment

Choose a reason for hiding this comment

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

LGTM

Thanks @cappyzawa 🥇

@stefanprodan stefanprodan merged commit c2b572b into fluxcd:main Jul 31, 2025
8 checks passed
@cappyzawa cappyzawa deleted the feat/bucket-controller-runtime-secrets-migration branch July 31, 2025 16:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants