feat: service.{http,ssh}.loadBalancerClass
#640
No reviewers
Labels
No Label
has
backport
in progress
invalid
kind
breaking
kind
bug
kind
build
kind
dependency
kind
deployment
kind
docs
kind
enhancement
kind
feature
kind
lint
kind
proposal
kind
question
kind
refactor
kind
security
kind
testing
kind
translation
kind
ui
need
backport
priority
critical
priority
low
priority
maybe
priority
medium
reviewed
duplicate
reviewed
invalid
reviewed
wontfix
skip-changelog
status
blocked
status
needs-feedback
status
needs-reviews
status
wip
upstream
gitea
upstream
other
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/helm-chart#640
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "Karitham/helm-chart:main"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description of the change
Introduce
service.{http,ssh}.loadBalancerClass
Benefits
Feature was not supported before. This is required if your cluster has multiple loadBalancer options and you want to select one
Possible drawbacks
More yaml.
Checklist
values.yaml
and added to theREADME.md
using readme-generator-for-helmservice.{http,ssh}.loadBalancerClass
Thanks for contributing. It would be great to add unit tests for this feature. To ensure it is rendered correctly in different scenarios.
type: LoadBalancer
propertiesThese tests should roughly cover the changes, namely making sure
type: LoadBalancer
properties aren't set when we aren't in aLoadBalancer
and thatloadBalancerClass
exists (only) when it's set.@ -52,0 +54,4 @@
template: templates/gitea/ssh-svc.yaml
set:
service:
ssh:
Thanks for adding tests!
Can we expand the tests to check for existence/non-existence for both
ssh
andhttp
?ping @Karitham
oop sorry forgot about this
I've added a test but I'm generally unhappy about using regex to test this, unfortunately I don't really have a better solution. Let me know if I can make them better
You could split the
it
with the regex and just duplicate that spec. Duplicating within tests is totally fine, IMO.5851f9a65c
to1707c56fd1
@Karitham Thanks for your patience. LGTM now.
@justusbunsi Feel free to add more comments or merge!