Skip to content

feat: add support for specifying LoadBalancer class name #15838

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

Merged
merged 3 commits into from
Dec 13, 2024

Conversation

jamezrin
Copy link
Contributor

@jamezrin jamezrin commented Dec 11, 2024

This PR adds support for configuring the loadBalancerClass via the chart values.

@cdr-bot cdr-bot bot added the community Pull Requests and issues created by the community. label Dec 11, 2024
Copy link

github-actions bot commented Dec 11, 2024

All contributors have signed the CLA ✍️ ✅
Posted by the CLA Assistant Lite bot.

@jamezrin
Copy link
Contributor Author

I have read the CLA Document and I hereby sign the CLA

cdrci2 added a commit to coder/cla that referenced this pull request Dec 11, 2024
@jamezrin jamezrin changed the title Add support for specifying LoadBalancer class name feat: Add support for specifying LoadBalancer class name Dec 11, 2024
@jamezrin jamezrin changed the title feat: Add support for specifying LoadBalancer class name feat: add support for specifying LoadBalancer class name Dec 11, 2024
@@ -281,6 +281,9 @@ coder:
# your cloud and specify it here in production to avoid accidental IP
# address changes.
loadBalancerIP: ""
# coder.service.className -- The class name of the LoadBalancer. See:
# https://kubernetes.io/docs/concepts/services-networking/service/#load-balancer-class
className: ""
Copy link
Member

Choose a reason for hiding this comment

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

Can this be changed to loadBalancerClass to match the field in the k8s yaml?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done

Copy link
Member

@johnstcn johnstcn 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!

Before merging, please add some new test cases to cover this new field:

  • Add a corresponding values YAML and golden file in helm/coder/tests/testdata/. You can copy an existing golden file and modify it to suit.
  • Add the corresponding test case in helm/coder/tests/chart_test.go
  • Modify the golden file and/or changes until the output is as expected.

I would also suggest modifying the service template such that if new field is not specified, no changes should be made to existing test cases.

I also agree with @deansheather 's suggestion regarding the naming of the new field.

Thanks!

@jamezrin
Copy link
Contributor Author

Thanks for reviewing, I made the changes. The tests are passing locally, but I don't think the CI is running them, is that normal?

@johnstcn
Copy link
Member

Thanks for reviewing, I made the changes. The tests are passing locally, but I don't think the CI is running them, is that normal?

It is! I just pushed the button to make them run.

@johnstcn johnstcn merged commit d504e0e into coder:main Dec 13, 2024
29 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Dec 13, 2024
@johnstcn
Copy link
Member

Merged, thanks @jamezrin !

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
community Pull Requests and issues created by the community.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants