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(argocd-image-updater): Add support for additional initContainers and additional volume/volumeMounts for argocd-image-updater #1542

Merged
merged 1 commit into from
Oct 11, 2022

Conversation

bakito
Copy link
Contributor

@bakito bakito commented Oct 11, 2022

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.

@bakito bakito requested a review from oliverbaehler as a code owner October 11, 2022 14:28
@bakito bakito changed the title Add support for additional initContainers and additional volume/volumeMounts for argocd-image-updater feat: Add support for additional initContainers and additional volume/volumeMounts for argocd-image-updater Oct 11, 2022
@bakito bakito changed the title feat: Add support for additional initContainers and additional volume/volumeMounts for argocd-image-updater feat(argocd-image-updater): Add support for additional initContainers and additional volume/volumeMounts for argocd-image-updater Oct 11, 2022
…eMounts

fix github action to handle crd installation correctly

Signed-off-by: bakito <github@bakito.ch>
Copy link
Contributor

@oliverbaehler oliverbaehler left a comment

Choose a reason for hiding this comment

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

Thanks for your contribution :)

@oliverbaehler oliverbaehler merged commit 32d8666 into argoproj:main Oct 11, 2022
kubectl apply -f charts/argo-cd/templates/crds
helm repo add dandydeveloper https://dandydeveloper.github.io/charts/
helm dependency build charts/argo-cd/
helm template charts/argo-cd/ -s templates/crds/* | kubectl apply -f -
Copy link
Member

Choose a reason for hiding this comment

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

@bakito why so complicated now? ;-)

Copy link
Member

Choose a reason for hiding this comment

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

AH lol, answering myself: Because Argo CD have now templated CRDs

Copy link
Contributor Author

@bakito bakito Oct 12, 2022

Choose a reason for hiding this comment

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

@mkilchhofer
Because the crd need to be rendered since they are in templates.
Crds were moved into templates and extenedt with template logic which prevents them to be applied as is.

See https://github.com/argoproj/argo-helm/blob/main/charts/argo-cd/templates/crds/crd-project.yaml#L6

To get my pr green I had to fix this logic in the action, as it was forgotten to be tested in the original PR.
#1342

I did not find an easier solution, if you have one, feel free to change it.

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.

3 participants