Support multi-port services

[geiralund]

We do need to expose a gRPC endpoint for one of our services. The service does already expose an HTTP endpoint. Due to compatibility, we would like the service to support both protocols and reuse the same code in the service. Currently, we'll have to create two deploys, with different service manifest to expose both the gRPC endpoint and HTTP endpoint.

Kubernetes lets you configure multiple port definitions on a Service object and it would be great if we could have the same concept in naiserator.

Any ideas?

[gtcno]

@jhrv Foreslo workaround/løsning: Lag en egen svc med flere porter.
Som f.eks

kind: Service
metadata:
  labels:
    app: dp-inntekt-api-grpc
    team: teamdagpenger
  name: dp-inntekt-api-grpc
spec:
  ports:
  - name: http
    port: 80
    protocol: TCP
    targetPort: 8099
  - name: grpc
    port: 50051
    protocol: TCP
    targetPort: 50051
  selector:
    app: dp-inntekt-api

Da er problemet redusert til om nais deploy støtter services og om RBAC tillater deploy
av services

Error from server (Forbidden): error when creating "./nais/nais-dev-deploy.yaml": services is forbidden: User "system:serviceaccount:default:serviceuser-teamdagpenger" cannot create resource "services" in API group "" in the namespace "default"

[audunstrand]

When this was implementet in FIAAS, we realised you also need to make it possible to decalre which port is used for healthchecks and metrics

[mortenlj]

When this was implementet in FIAAS, we realised you also need to make it possible to decalre which port is used for healthchecks and metrics

..and which ports should get which ingress URL. The FIAAS spec is documented here, it might give some ideas:
https://github.com/fiaas/fiaas-deploy-daemon/blob/master/docs/v3_spec.md

[kimtore]

suggestion for v2?

spec:
  port: 80 // deprecated/removed
  ports:
  - name: http
    port: 80
    protocol: TCP // optional
    targetPort: 8099
  - name: grpc
    port: 50051
    protocol: TCP
    targetPort: 50051