-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
fix(argo-cd): Correct ApplicationSet controller port #1200
fix(argo-cd): Correct ApplicationSet controller port #1200
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @visheyra, thanks for your contribution.
These tasks still are open:
- Adapt Chart.yaml: bump version, and write a changelog line
- Sign-off your commit (git commit -s --amend)
For the change itself, i'd suggest to omit the containerPort from values and "hardcode" it as introduced here: e7a2746
It seems that @mikeeq missed that while he implemented the 2.3 changes
4f9ff2f
to
85fbdb8
Compare
@mkilchhofer Okay, I think indeed hardcoding it is better ^^. I pushed/force I think this cover all your points now ? |
3eacfbc
to
6a641ec
Compare
Signed-off-by: amaury ravanel <amaury.ravanel@gmail.com>
6a641ec
to
98f2075
Compare
Signed-off-by: Marco Kilchhofer <mkilchhofer@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm now 👍
* Add default value for the applicationSet controller container port Signed-off-by: amaury ravanel <amaury.ravanel@gmail.com> * Apply suggestions from code review Signed-off-by: Marco Kilchhofer <mkilchhofer@users.noreply.github.com> Co-authored-by: Marco Kilchhofer <mkilchhofer@users.noreply.github.com>
This PR propose a fix for the #1199.
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:
Changes are automatically published when merged to
master
. They are not published on branches.