-
Notifications
You must be signed in to change notification settings - Fork 21
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
I have detected several issues on the Helm Chart #13
Comments
Yes this project is open to contributions. Please let me know which issues
you found.
…On Fri, Mar 4, 2022, 3:05 PM Alby Hernández ***@***.***> wrote:
Hello there,
Me and my team were at the point to develop the same operator until I
discovered this one. This is useful but I am deploying it on EKS/GKE using
the Helm chart. I inspected all the manifests and made it work using
Kustomization + Helm approach because I had to patch several things. I have
it working now and like it a lot after several hours solving some typical
issues.
Is this project open to collaborations? I mean, I would like to open
several PRs to parametrize and fix several things that make it run in
Kubernetes and not only in OpenShift
Thanks in advance for your answer
—
Reply to this email directly, view it on GitHub
<#13>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABPERXEXVRLPYK3DQPDY4TTU6JUIFANCNFSM5P6OLFVA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Due to there are several failures on the Helm Chart that make hard to use it, I will open several PRs these days to treat each of them individually and make it easier not to break anything. What do you thing? |
That is fine. Please make sure you understand how the helm char is
generated.
On Fri, Mar 4, 2022, 4:16 PM Alby Hernández ***@***.***>
wrote:
… Yes this project is open to contributions. Please let me know which issues
you found.
… <#m_-2811387597373662410_>
On Fri, Mar 4, 2022, 3:05 PM Alby Hernández *@*.*> wrote: Hello there, Me
and my team were at the point to develop the same operator until I
discovered this one. This is useful but I am deploying it on EKS/GKE using
the Helm chart. I inspected all the manifests and made it work using
Kustomization + Helm approach because I had to patch several things. I have
it working now and like it a lot after several hours solving some typical
issues. Is this project open to collaborations? I mean, I would like to
open several PRs to parametrize and fix several things that make it run in
Kubernetes and not only in OpenShift Thanks in advance for your answer —
Reply to this email directly, view it on GitHub <#13
<#13>>, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABPERXEXVRLPYK3DQPDY4TTU6JUIFANCNFSM5P6OLFVA
<https://github.com/notifications/unsubscribe-auth/ABPERXEXVRLPYK3DQPDY4TTU6JUIFANCNFSM5P6OLFVA>
. Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you are subscribed to this thread.Message
ID: @.*>
Due to there are several failures on the Helm Chart that make hard to use
it, I will open several PRs these days to treat each of them individually
and make it easier not to break anything.
What do you thing?
—
Reply to this email directly, view it on GitHub
<#13 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABPERXEA5P4QHVBO6VGPGU3U6J4SXANCNFSM5P6OLFVA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you commented.Message ID:
***@***.***>
|
I'm using Helm as well, and created some explicit issues for certain problems that I discovered: |
Hello there,
Me and my team were at the point to develop the same operator until I discovered this one. This is useful but I am deploying it on EKS/GKE using the Helm chart. I inspected all the manifests and made it work using Kustomization + Helm approach because I had to patch several things. I have it working now and like it a lot after several hours solving some typical issues.
Is this project open to collaborations? I mean, I would like to open several PRs to parametrize and fix several things that make it run in Kubernetes and not only in OpenShift
Thanks in advance for your answer
The text was updated successfully, but these errors were encountered: