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

[bitnami/testlink]how to add service annotation to create a internal load balancer #1879

Closed
Yamini-TWG opened this issue Feb 3, 2020 · 4 comments · Fixed by helm/charts#20531
Labels
stale 15 days without activity

Comments

@Yamini-TWG
Copy link

hello,

I am trying to install test-link in kubernets cluster using bitnami charts, I am trying to understand how to add a service.annotation to bring up the internal load balancer. I no where seen that option in values file.

Charts: testlink

thank you

@Yamini-TWG Yamini-TWG changed the title how to add service annotation to create a internal load balancer [bitnami/testlink]how to add service annotation to create a internal load balancer Feb 3, 2020
@dani8art
Copy link
Contributor

dani8art commented Feb 4, 2020

Hi @Yamini-TWG

Thank you for opening this issue. I've created a PR in the stable repository in order to add the possibility of passing annotations to the service.

Regards.

@Yamini-TWG
Copy link
Author

well, Thank you so much. I really appreciate the quick response

@stale
Copy link

stale bot commented Feb 19, 2020

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

@stale stale bot added the stale 15 days without activity label Feb 19, 2020
@carrodher
Copy link
Member

Thanks for reporting the issue. It should be fixed as part of helm/charts#20531, please don't hesitate to reopen this issue if the solution doesn't work as expected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale 15 days without activity
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants