Skip to content

Service Configuration is very limiting #89

@jseiser

Description

@jseiser

The configuration for the services is very limited.

Take the below. To be able to use this chart, I would need to be able to remove the traefik annotation, provide correct annotations to each service, as well as the correct labels. I would then need to be able to set the service type for GRPC to a difference type than the standard service.

apiVersion: v1
kind: Service
metadata:
  annotations:
    traefik.ingress.kubernetes.io/service.serversscheme: h2c
  name: {{ include "defguard.fullname" . }}-grpc
  labels:
    {{- include "defguard.labels" . | nindent 4 }}
spec:
  type: {{ .Values.service.type }}
apiVersion: v1
kind: Service
metadata:
  name: {{ include "defguard.fullname" . }}-web
  labels:
    {{- include "defguard.labels" . | nindent 4 }}
spec:
  type: {{ .Values.service.type }}

e.g. something like

service:
  grpc:
    annotations: {}
    labels: {}
    port: 50051
    type: ClusterIP
  http:
    annotations: {}
    labels: {}
    port: 8080
    type: ClusterIP
apiVersion: v1
kind: Service
metadata:
  annotations:
    {{- include "defguard.service.grpc.annotations" . | nindent 4 }}
  name: {{ include "defguard.fullname" . }}-grpc
  labels:
    {{- include "defguard.labels" . | nindent 4 }}
    {{- include "defguard.service.grpc.labels" . | nindent 4 }}
spec:
  type: {{ .Values.service.grpc.type }}

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

Status

Ready to release

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions