-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
how can I allocate my service (type=NodePort) on nodePort: 80 #836
Comments
Hey, Looks like Port Range uses a custom type and parser. We have to add that to the extra-config parsing. I just sent #837 to do that, then you should be good to go :) |
Thank you but the error persits:
I send you logs outputs for checking. What is good string for it works? |
@dani8art You'll need to make sure you're consulting the right version of the k8s type. This struct changed between 1.4 and 1.5. You can check to see what version your minikube is running with This is the name of the struct for kubernetes 1.4.6, looks like the path would be |
Hi, I've downloaded the latest build version of minikube from: https://storage.googleapis.com/minikube-builds/837/minikube-windows-amd64.exe and I've executed:
I think is the build version with the changes that resolves this bug #836 and now the error is different it says:
have I downloaded the good version of minikube? |
I'll try this out now. |
Whoops, I figured out the issue. It was the last swap of imports. The types aren't the same: utilnet "k8s.io/kubernetes/pkg/util/net" |
That good, now it is working! |
Great! We'll try to get a release out this week. |
seems like the option has changed these days. |
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
Feature request
Minikube version (use
minikube version
): v0.12.2Environment:
docker -v
): Docker version 1.11.1, build 5604cbeWhat happened:
When I create a service (type=NodePort) and I want to allocate it to port 80 or 27017, kubectl responds:
The Service "pets-service" is invalid. spec.ports[0].nodePort: Invalid value: 80: provided port is not in the valid range
I've seem the documentation and I think that you can change some parameters on
minikube start
with--extra-config
and in other issues that I could see say that I must change theServiceNodePortRange
. I've tried to execute:minikube start --extra-config=apiserver.GenericServerRunOptions.ServerRunOptions.ServiceNodePortRange=1-30000
but this doesn't work.
I kwon I can set nodePort to other port in the range 30000-31000, but this solution isn't good for me.
any hint?
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Run minikube
minikube start
Create service
kubectl create -f pets-service.yaml
Anything else do we need to know:
My service file:
The text was updated successfully, but these errors were encountered: