Implement new features

- Allow defining custom containerPorts in both the forwarders and the
aggregators
  - Add services for the forwarders and the aggregator
  - Allow exposing custom ports in the services
  - Add an option to deploy only the aggregator

Signed-off-by: Alejandro Moreno <amoreno@bitnami.com>
This commit is contained in:
Alejandro Moreno
2019-11-06 11:42:46 +00:00
parent 5d041c877f
commit 43f391dfa3
13 changed files with 331 additions and 18 deletions

View File

@@ -38,6 +38,7 @@ image:
clusterDomain: cluster.local
forwarder:
enabled: true
## Name of the config file that will be used by Fluentd at launch
## Fluentd will look for it under the /opt/bitnami/fluentd/conf directory
##
@@ -59,6 +60,68 @@ forwarder:
##
extraEnv: {}
containerPorts:
- name: http
containerPort: 9880
protocol: TCP
# - name: syslog-tcp
# containerPort: 5140
# protocol: TCP
# - name: syslog-udp
# containerPort: 5140
# protocol: UDP
# - name: tcp
# containerPort: 24224
# protocol: TCP
## Service parameters
##
service:
## Service type
##
type: ClusterIP
## Service ports
##
ports:
# http:
# port: 9880
# targetPort: http
# protocol: TCP
# syslog-udp:
# port: 5140
# targetPort: syslog-udp
# protocol: UDP
# nodePort: 31514
# syslog-tcp:
# port: 5140
# targetPort: syslog-tcp
# protocol: TCP
# nodePort: 31514
# tcp:
# port: 24224
# targetPort: tcp
# protocol: TCP
## loadBalancerIP for the forwarders service (optional, cloud specific)
## ref: http://kubernetes.io/docs/user-guide/services/#type-loadbalancer
# loadBalancerIP:
## Load Balancer sources
## https://kubernetes.io/docs/tasks/access-application-cluster/configure-cloud-provider-firewall/#restrict-access-for-loadbalancer-service
##
# loadBalancerSourceRanges:
# - 10.10.10.0/24
## Set the Cluster IP to use
## ref: https://kubernetes.io/docs/concepts/services-networking/service/#choosing-your-own-ip-address
##
# clusterIP: None
## Provide any additional annotations which may be required
##
annotations: {}
## Configure extra options for liveness and readiness probes
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes)
##
@@ -133,7 +196,8 @@ aggregator:
## If not specified, one will be created by default
# configMap:
## Port which the forwarders will connect to to send the logs
## Port the aggregator container will listen for logs. Leave it blank to ignore.
## You can specify other ports in the aggregator.containerPorts parameter
##
port: 24224
@@ -149,6 +213,52 @@ aggregator:
##
extraEnv: {}
containerPorts:
# - name: my-port
# containerPort: 24222
# protocol: TCP
- name: http
containerPort: 9880
protocol: TCP
## Service parameters
##
service:
## Service type
##
type: ClusterIP
## Service ports
##
ports:
tcp:
port: 24224
targetPort: tcp
protocol: TCP
# http:
# port: 9880
# targetPort: http
# protocol: TCP
## loadBalancerIP for the forwarders service (optional, cloud specific)
## ref: http://kubernetes.io/docs/user-guide/services/#type-loadbalancer
# loadBalancerIP:
## Load Balancer sources
## https://kubernetes.io/docs/tasks/access-application-cluster/configure-cloud-provider-firewall/#restrict-access-for-loadbalancer-service
##
# loadBalancerSourceRanges:
# - 10.10.10.0/24
## Set the Cluster IP to use
## ref: https://kubernetes.io/docs/concepts/services-networking/service/#choosing-your-own-ip-address
##
# clusterIP: None
## Provide any additional annotations which may be required
##
annotations: {}
## Configure extra options for liveness and readiness probes
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes)
##