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-cd): Upgrade Argo CD to 2.6.0 #1758

Merged
merged 1 commit into from
Feb 7, 2023

Conversation

pdrastil
Copy link
Member

@pdrastil pdrastil commented Jan 11, 2023

Upgrade to 2.6.0 stable version

Upgrade notes: https://argo-cd.readthedocs.io/en/latest/operator-manual/upgrading/2.5-2.6/


Note on DCO:

If the DCO action in the integration test fails, one or more of your commits are not signed off. Please click on the Details link next to the DCO action for instructions on how to resolve this.

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).

Changes are automatically published when merged to main. They are not published on branches.

@pdrastil pdrastil added awaiting-upstream Is waiting for a change upstream to be completed before it can be merged. and removed size/XXL labels Jan 11, 2023
@pdrastil pdrastil force-pushed the feature/upgrade branch 2 times, most recently from 3fc61e7 to fa2f120 Compare January 18, 2023 13:05
@pdrastil pdrastil force-pushed the feature/upgrade branch 9 times, most recently from 909d7bf to 1b55fac Compare January 27, 2023 23:37
@pdrastil pdrastil force-pushed the feature/upgrade branch 6 times, most recently from b6326d1 to bf46e1e Compare February 2, 2023 12:31
@pdrastil pdrastil force-pushed the feature/upgrade branch 3 times, most recently from 32c5afd to cc41f6a Compare February 7, 2023 09:09
@pdrastil pdrastil marked this pull request as ready for review February 7, 2023 09:11
Copy link
Member

@jmeridth jmeridth left a comment

Choose a reason for hiding this comment

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

LGTM 👍

@mbastawisy-careem
Copy link

Hey everyone, any updates on when this will be released?

@pdrastil pdrastil removed the awaiting-upstream Is waiting for a change upstream to be completed before it can be merged. label Feb 7, 2023
@jmeridth
Copy link
Member

jmeridth commented Feb 7, 2023

@mbastawisy-careem once we get another approval. Thank you for your patience.

Copy link
Collaborator

@yu-croco yu-croco left a comment

Choose a reason for hiding this comment

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

LGTM! 🚀

@pdrastil pdrastil merged commit 0d3150c into argoproj:main Feb 7, 2023
@pdrastil pdrastil deleted the feature/upgrade branch February 7, 2023 15:02
type: object
required:
- metadata
- spec
type: object
required:
- pathParamPrefix
Copy link

Choose a reason for hiding this comment

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

Is it intentional that this is required now? I'm getting the following error when upgrading:

failed to apply ApplicationSet.argoproj.io, argocd/skip-apps: ApplicationSet.argoproj.io "skip-apps" is invalid: spec.generators[0].git.         pathParamPrefix: Required value

The documentation seems to infer that it should be optional:
https://argo-cd.readthedocs.io/en/release-2.6/operator-manual/applicationset/Generators-Git/#git-generator-directories

Copy link
Member Author

Choose a reason for hiding this comment

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

Good catch @esphen - missed that one with diff. PR contains the fix #1829

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.

6 participants