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

Service object expose or disable. #852

Open
bencetamasbalint opened this issue Jul 8, 2024 · 2 comments
Open

Service object expose or disable. #852

bencetamasbalint opened this issue Jul 8, 2024 · 2 comments

Comments

@bencetamasbalint
Copy link

Hi Vertica team,

Please create an option for allowing/disabling or please expose the Kubernetes service object settings for the operator.
The service object created by the operator could not get the following settings for example:

  • externalTrafficPolicy
  • ipFamilies
  • service port
  • etc.
    If there is an option to disable the service object creation by the operator, then a custom one could be created.
    Preferably if the service object options are exposed, then we could customize the related settings.
    Thank you in advance!
@roypaulin
Copy link
Collaborator

Hi @bencetamasbalint, we already expose essential fields of a service object that we think are useful for Vertica on Kubernetes. Do you mind telling us some use cases where you would need to have more control over the service object?

@bencetamasbalint
Copy link
Author

Hi @roypaulin,
As an example for use case, we would like to see the host ip when connecting to vertica, and for that we need to set the externalTrafficPolicy to local.
For the IPfamilies and the servicePort, we have design rules in our product that it needs to be configurable.
Best regards, Bence

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

No branches or pull requests

2 participants