Closed langecode closed 2 years ago
Definitely! I'm less familiar with NodePorts
@langecode but I thought you really just needed to change the Service's spec.type
to be NodePort
- which should be doable on the regular Service today with .Values.service.type
(the headless variant is hardcoded to ClusterIP which I thought was expected, but it's been a while since I looked).
Closing due to inactivity.
Migrating from the aggregator chart to the generic Vector chart I was wondering how to control the node port. It seems pretty clever to find the ports based on the custom config - however as we are running the aggregator inside of Kubernetes I need to expose it externally. Currently we have done so by defining a fixed node-port which we use for data ingestion. Do you have any plans to support something similar for the new generic chart?