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

feat(vector): Allow configuration of service port overrides via vector.portsOverrides #434

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

bderrly
Copy link

@bderrly bderrly commented Dec 6, 2024

This template is meant for those users that want the automatically generated port definitions in the Service manifests but also needs to make some overrides, or additions, to those definitions.

Example changes:

values.yaml

service:
  portsOverrides:
    - name: vector
      appProtocol: grpc

customConfig:
  api:
    enabled: true
    address: 127.0.0.1:8686
  sources:
    vector:
      address: 0.0.0.0:6000
      type: vector

results in a Service like the following:

kind: Service
clusterIP: None
ports:
  - appProtocol: grpc
    name: vector
    port: 6000
    protocol: TCP
    targetPort: 6000
  - name: api
    port: 8686
    protocol: TCP
    targetPort: 8686
selector:
  app.kubernetes.io/name: vector
  app.kubernetes.io/instance: release-name
  app.kubernetes.io/component: Aggregator
type: ClusterIP

This template is meant for those users that want the automatically
generated port definitions in the Service manifests but also needs to
make some overrides, or additions, to those definitions.
@jszwedko jszwedko changed the title Add vector.portsOverrides named template. feat(vector): Allow configuration of service port overrides via vector.portsOverrides Dec 6, 2024
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

Successfully merging this pull request may close these issues.

1 participant