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

Revert "Update Flux dependencies" #3818

Merged
merged 6 commits into from
Jul 6, 2023
Merged

Revert "Update Flux dependencies" #3818

merged 6 commits into from
Jul 6, 2023

Conversation

foot
Copy link
Contributor

@foot foot commented Jul 6, 2023

Reverts #3811

This PR requires any dependencies upgrade to controller-runtime 0.15.0 which has many breaking changes:

Maybe we squeeze in one more release before doing that bump?

foot added 6 commits July 6, 2023 09:43
…his commit ignores the linter warnings but needless to say this needs to be resolved properly, in a follow-up PR."

This reverts commit 9f4bb9e.
…/fluxcd/kustomize-controller/api v0.34.0 => v1.0.0-rc.4 - github.com/fluxcd/source-controller/api v1.0.0-rc.1 => v1.0.0-rc.5 - github.com/fluxcd/notification-controller/api v0.32.1 => v1.0.0-rc.4 - github.com/fluxcd/pkg/runtime v0.29.0 => v0.39.0"

This reverts commit c6f25af.
@foot foot marked this pull request as ready for review July 6, 2023 09:31
@foot foot requested a review from yiannistri July 6, 2023 09:31
@foot foot merged commit 5780243 into main Jul 6, 2023
@foot foot deleted the revert-3811-3810-flux-v2 branch July 6, 2023 09:40
sourcev1beta2.AddToScheme,
kustomizev1beta2.AddToScheme,
sourcev1.AddToScheme,
kustomizev2.AddToScheme,
Copy link
Contributor

Choose a reason for hiding this comment

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

for gitrepository v1 and kustomization v1

Copy link
Contributor

Choose a reason for hiding this comment

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

  1. assume only v1 -> we could support flux v2 but we break < 0.4x
    release this
    do we have customers asking for backward compatibility ?
    in case yes, we could open a ticket to think on supporting backward compatibility as follow up

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