You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I our company we use a strict admission controller policy where all our delploys, sts, jobs, pods and services require a specific set of labels to allow the creation of those API objects.
I'm unable to complete the installation of sumologic-kubernetes-collection with out an option to include custom labels in this fluentd services like.
sumologic-sumologic-fluentd-logs-headless service
sumologic-sumologic-fluentd-events-headless service
sumologic-sumologic-fluentd-metrics-headless service
Describe the solution you'd like
Add an option to include custom labels in the values.yaml file for those fluentd headless services.
Could something like this.
fluentd:
events:
service:
labels:
label:1
label:2
Other option can be to include these labels from values.fluentd.podlabels:
{{- if .Values.fluentd.podLabels }}
{{ toYaml .Values.fluentd.podLabels | indent 4 }}
{{- end }}
mozz-lx
changed the title
add an option to include custom labels for headless services
add an option to include custom labels for fluentd services
Apr 8, 2021
Is your feature request related to a problem? Please describe.
I our company we use a strict admission controller policy where all our delploys, sts, jobs, pods and services require a specific set of labels to allow the creation of those API objects.
I'm unable to complete the installation of sumologic-kubernetes-collection with out an option to include custom labels in this fluentd services like.
Describe the solution you'd like
Add an option to include custom labels in the values.yaml file for those fluentd headless services.
Could something like this.
Other option can be to include these labels from values.fluentd.podlabels:
in the fluentd services.
metrics-service-headless
logs-service-headless
events-service-headless
events-service
metrics-service
logs-service
The text was updated successfully, but these errors were encountered: