Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add nodeport/ingress service options #1

Open
ddieruf opened this issue Aug 21, 2023 · 1 comment
Open

Add nodeport/ingress service options #1

ddieruf opened this issue Aug 21, 2023 · 1 comment

Comments

@ddieruf
Copy link
Member

ddieruf commented Aug 21, 2023

Currently 'control-plane-deployment.yaml' gives the primary container the following option for port numbering:

ports:
  - name: http
    containerPort: {{ .Values.controlPlane.service.port }}
    protocol: TCP

The 'control-plane-service.yaml' uses the same port value to set the service.

spec:
  type: {{ .Values.controlPlane.service.type }}
  ports:
    - port: {{ .Values.controlPlane.service.port }}
      targetPort: http
      protocol: TCP
      name: http

If I set the 'type' to NodePort, but can't set a NodePort value then K8s will choose one for me. But I have no way of setting the container port so it will default to "8090". Which renders the service unhealthy and the control plane pod inaccessible.

@ddieruf ddieruf changed the title Add nodeport service options Add nodeport/ingress service options Aug 30, 2023
@ddieruf
Copy link
Member Author

ddieruf commented Aug 30, 2023

Additionally it would be nice to have the option of creating an ingress for the control plane and the gateway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant