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

unable to use nodePort service without setting a nodePort #44

Open
si458 opened this issue Nov 18, 2020 · 2 comments · May be fixed by #606
Open

unable to use nodePort service without setting a nodePort #44

si458 opened this issue Nov 18, 2020 · 2 comments · May be fixed by #606

Comments

@si458
Copy link

si458 commented Nov 18, 2020

nodePort should be optional and not required for nodePort Service
https://kubernetes.io/docs/concepts/services-networking/service/#type-nodeport
my nextcloud.yaml file for helm helm install nextcloud nextcloud/nextcloud -f nextcloud.yaml

persistence:
  enabled: true
service:
  type: NodePort

ERROR:

Error: unable to build kubernetes objects from release manifest: error validating "":
error validating data: ValidationError(Service.spec.ports[0].nodePort):
invalid type for io.k8s.api.core.v1.ServicePort.nodePort: got "string", expected "integer"
@willzhang
Copy link

willzhang commented Aug 21, 2023

same here, i must use this method

helm install nextcloud
 nextcloud/nextcloud -n nextcloud --create-namespace \
--set persistence.enabled=true \
--set service.type=NodePort \
--set service.nodePort=30808 \
--set nextcloud.host=192.168.72.17.nip.io:30080

but i find nodeport is not need in nextcloud.host, just nextcloud.host=192.168.72.17.nip.io is ok.

@jessebot
Copy link
Collaborator

jessebot commented Sep 1, 2023

We'd love a PR on this if it's still a problem. We recently had this similar PR for reference: #430

@jessebot jessebot added 1. to develop Accepted and waiting to be taken care of good first issue Small tasks with clear documentation about how and in which place you need to fix things in. labels Jul 25, 2024
jessebot added a commit to jessebot/nextcloud-helm that referenced this issue Jul 26, 2024
fixes nextcloud#44

Signed-off-by: jessebot <jessebot@linux.com>
@jessebot jessebot linked a pull request Jul 26, 2024 that will close this issue
4 tasks
@jessebot jessebot removed 1. to develop Accepted and waiting to be taken care of good first issue Small tasks with clear documentation about how and in which place you need to fix things in. labels Jul 26, 2024
jessebot added a commit to jessebot/nextcloud-helm that referenced this issue Jul 26, 2024
fixes nextcloud#44

Signed-off-by: jessebot <jessebot@linux.com>
jessebot added a commit to jessebot/nextcloud-helm that referenced this issue Jul 28, 2024
fixes nextcloud#44

Signed-off-by: jessebot <jessebot@linux.com>
jessebot added a commit to jessebot/nextcloud-helm that referenced this issue Jul 29, 2024
fixes nextcloud#44

Signed-off-by: jessebot <jessebot@linux.com>
jessebot added a commit to jessebot/nextcloud-helm that referenced this issue Jul 29, 2024
fixes nextcloud#44

Signed-off-by: jessebot <jessebot@linux.com>
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

Successfully merging a pull request may close this issue.

3 participants