-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Deploy OpenShift route for external communications using the Helm Chart #3777
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.
Hello there rmarting! 👋
Thank you and congrats 🎉 for opening your first PR on this project! ✨ 💖
We will try to review it soon!
@Narekmat @provectus/kafka-devops PTAL :) |
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.
@rmarting thank you for your changes.
Please increment version in Chart.yaml file to 0.6.4
@Narekmat Done!!! Ready for your review! Thanks However, it seems that there is a conflict with the latest version in the |
Are you aware that you can use ingress annotations to achieve the same effect? :) In my experience it is rare to include openshift specific features such as routes in generic helm charts. |
@cadnce you are right, however OpenShift routes is another way to expose externally services outside from the platform. I found many users using OpenShift routes to expose their services instead of the ingress objects, as from a platform point of view, it is very easy and you don't need to deal with the host entries. This PR is just to improve the helm chart to use this kind of object (optionally) for this kind of platform. I found other Helm Charts in the community including too. |
Any comment? Thanks! |
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.
Please replace appVersion: to v0.7.0 and version 0.7.2
@Narekmat Done! |
This PR has been automatically marked as stale because no requested changes have been applied. It will be closed if no further activity occurs. Thank you for your contributions. |
@Narekmat This PR is ready for your review. Thanks! |
We'll take a look why helm linter is failing. |
@rmarting it seems that this logic is indeed very dependent on openshift, as our linter cannot validate the changes. |
This PR has been automatically marked as stale because no requested changes have been applied. It will be closed if no further activity occurs. Thank you for your contributions. |
@Haarolean please, dont close for now this PR. I have an idea about how to validate the route object, but I need some time to implement it. How long can be opened the PR before an automatic close? Thanks |
@rmarting we'd need to reopen it in the charts repo anyway :) |
Ok! @Haarolean I will try to resolve it there with a new PR. Thanks for the heads up! |
What changes did you make? (Give an overview)
This PR is created to support the enhacement identified in the provectus/kafka-ui-charts#4. It is an initial approach to cover that feature for OpenShift environments.
Is there anything you'd like reviewers to focus on?
Code format for the new Route template (I compared with the Ingress one, but just to double check that is aligned with the code formats)
How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)
It was tested locally using a local OpenShift cluster (using OpenShift Local), and another remote cluster.
The
value.yaml
file used for my local tests was similar to:This is the command used to execute the Helm Chart:
Checklist (put an "x" (case-sensitive!) next to all the items, otherwise the build will fail)
Check out Contributing and Code of Conduct
A picture of a cute animal (not mandatory but encouraged)