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

Configure end-point probe-time,retry values etc from kube-loxilb #546

Closed
UltraInstinct14 opened this issue Feb 23, 2024 · 1 comment
Closed
Labels
enhancement New feature or request

Comments

@UltraInstinct14
Copy link
Contributor

Is your feature request related to a problem? Please describe.
Currently, some values needed to configure end-points like probing timer and retry values need to be manually configured using loxicmd. Otherwise the default values in loxilb are used which may not be suitable for everyone.

Describe the solution you'd like
When using kube-loxilb, one should be able to specify default values using some annotation

Describe alternatives you've considered
N/A

Additional context
N/A

@UltraInstinct14 UltraInstinct14 added the enhancement New feature or request label Feb 23, 2024
UltraInstinct14 added a commit that referenced this issue Feb 23, 2024
gh-546: probetimeo/retry count configuration on LB creation
@TrekkieCoder
Copy link
Collaborator

The support has been added. The service can be configured with the following annotations -

apiVersion: v1
kind: Service
metadata:
  name: iperf-service
  annotations:
    loxilb.io/lbmode: "fullnat"
    loxilb.io/liveness: "yes"
    loxilb.io/probetimeout: "10"
    loxilb.io/proberetries: "2"
spec:
  externalTrafficPolicy: Local
  loadBalancerClass: loxilb.io/loxilb
  selector:
    what: the
  ports:
    - port: 55001
      targetPort: 5001
  type: LoadBalancer

In the above example, there will be two retries in interval of 10 seconds before considering the end-point as inoperative.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants