minikube expose service on specific port
Is it possible to expose a service on a specific port using minikube?
kubectl expose deployment my-deployment --type=NodePort --port=80 does not throw an error but when calling
minikube service my-deployment --url
it results in something like:
http://192.168.99.100:31512 and it is not available on port 80 but on port 31512 instead.
minikube
asked Nov 13 '18 at 1:04
Alexander ZeitlerAlexander Zeitler
3,91242955
add a comment |
Is it possible to expose a service on a specific port using minikube?
kubectl expose deployment my-deployment --type=NodePort --port=80 does not throw an error but when calling
minikube service my-deployment --url
it results in something like:
http://192.168.99.100:31512 and it is not available on port 80 but on port 31512 instead.
minikube
asked Nov 13 '18 at 1:04
Alexander ZeitlerAlexander Zeitler
3,91242955
add a comment |
Is it possible to expose a service on a specific port using minikube?
kubectl expose deployment my-deployment --type=NodePort --port=80 does not throw an error but when calling
minikube service my-deployment --url
it results in something like:
http://192.168.99.100:31512 and it is not available on port 80 but on port 31512 instead.
minikube
asked Nov 13 '18 at 1:04
Alexander ZeitlerAlexander Zeitler
3,91242955
Is it possible to expose a service on a specific port using minikube?
kubectl expose deployment my-deployment --type=NodePort --port=80 does not throw an error but when calling
minikube service my-deployment --url
it results in something like:
http://192.168.99.100:31512 and it is not available on port 80 but on port 31512 instead.
minikube
minikube
asked Nov 13 '18 at 1:04
Alexander ZeitlerAlexander Zeitler
3,91242955
asked Nov 13 '18 at 1:04
Alexander ZeitlerAlexander Zeitler
3,91242955
asked Nov 13 '18 at 1:04
Alexander ZeitlerAlexander Zeitler
3,91242955
asked Nov 13 '18 at 1:04
Alexander ZeitlerAlexander Zeitler
3,91242955
asked Nov 13 '18 at 1:04
Alexander ZeitlerAlexander Zeitler
3,91242955
3,91242955
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Valid ports for minikube of type nodePort by default are 30000-32767 according to https://kubernetes.io/docs/concepts/services-networking/service/#nodeport
I was able to specify a particular port (here: 30000 in that range using this services.yaml:
apiVersion: v1
kind: Service
metadata:
name: my-deployment
labels:
app: my-deployment
spec:
type: NodePort
ports:
- port: 80
targetPort: 80
nodePort: 30000
protocol: TCP
selector:
app: my-deployment
When starting minikube this way:
minikube start --extra-config=apiserver.service-node-port-range=80-30000, port 80 can be used as well:
apiVersion: v1
kind: Service
metadata:
name: my-deployment
labels:
app: my-deployment
spec:
type: NodePort
ports:
- port: 80
targetPort: 80
nodePort: 80
protocol: TCP
selector:
app: my-deployment
minikube service my-deployment --url now returns http://192.168.99.100:80 as expected and the application is available on port 80.
answered Nov 13 '18 at 1:30
Alexander ZeitlerAlexander Zeitler
3,91242955
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53272296%2fminikube-expose-service-on-specific-port%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Valid ports for minikube of type nodePort by default are 30000-32767 according to https://kubernetes.io/docs/concepts/services-networking/service/#nodeport
I was able to specify a particular port (here: 30000 in that range using this services.yaml:
apiVersion: v1
kind: Service
metadata:
name: my-deployment
labels:
app: my-deployment
spec:
type: NodePort
ports:
- port: 80
targetPort: 80
nodePort: 30000
protocol: TCP
selector:
app: my-deployment
When starting minikube this way:
minikube start --extra-config=apiserver.service-node-port-range=80-30000, port 80 can be used as well:
apiVersion: v1
kind: Service
metadata:
name: my-deployment
labels:
app: my-deployment
spec:
type: NodePort
ports:
- port: 80
targetPort: 80
nodePort: 80
protocol: TCP
selector:
app: my-deployment
minikube service my-deployment --url now returns http://192.168.99.100:80 as expected and the application is available on port 80.
answered Nov 13 '18 at 1:30
Alexander ZeitlerAlexander Zeitler
3,91242955
add a comment |
Valid ports for minikube of type nodePort by default are 30000-32767 according to https://kubernetes.io/docs/concepts/services-networking/service/#nodeport
I was able to specify a particular port (here: 30000 in that range using this services.yaml:
apiVersion: v1
kind: Service
metadata:
name: my-deployment
labels:
app: my-deployment
spec:
type: NodePort
ports:
- port: 80
targetPort: 80
nodePort: 30000
protocol: TCP
selector:
app: my-deployment
When starting minikube this way:
minikube start --extra-config=apiserver.service-node-port-range=80-30000, port 80 can be used as well:
apiVersion: v1
kind: Service
metadata:
name: my-deployment
labels:
app: my-deployment
spec:
type: NodePort
ports:
- port: 80
targetPort: 80
nodePort: 80
protocol: TCP
selector:
app: my-deployment
minikube service my-deployment --url now returns http://192.168.99.100:80 as expected and the application is available on port 80.
answered Nov 13 '18 at 1:30
Alexander ZeitlerAlexander Zeitler
3,91242955
add a comment |
Valid ports for minikube of type nodePort by default are 30000-32767 according to https://kubernetes.io/docs/concepts/services-networking/service/#nodeport
I was able to specify a particular port (here: 30000 in that range using this services.yaml:
apiVersion: v1
kind: Service
metadata:
name: my-deployment
labels:
app: my-deployment
spec:
type: NodePort
ports:
- port: 80
targetPort: 80
nodePort: 30000
protocol: TCP
selector:
app: my-deployment
When starting minikube this way:
minikube start --extra-config=apiserver.service-node-port-range=80-30000, port 80 can be used as well:
apiVersion: v1
kind: Service
metadata:
name: my-deployment
labels:
app: my-deployment
spec:
type: NodePort
ports:
- port: 80
targetPort: 80
nodePort: 80
protocol: TCP
selector:
app: my-deployment
minikube service my-deployment --url now returns http://192.168.99.100:80 as expected and the application is available on port 80.
answered Nov 13 '18 at 1:30
Alexander ZeitlerAlexander Zeitler
3,91242955
Valid ports for minikube of type nodePort by default are 30000-32767 according to https://kubernetes.io/docs/concepts/services-networking/service/#nodeport
I was able to specify a particular port (here: 30000 in that range using this services.yaml:
apiVersion: v1
kind: Service
metadata:
name: my-deployment
labels:
app: my-deployment
spec:
type: NodePort
ports:
- port: 80
targetPort: 80
nodePort: 30000
protocol: TCP
selector:
app: my-deployment
When starting minikube this way:
minikube start --extra-config=apiserver.service-node-port-range=80-30000, port 80 can be used as well:
apiVersion: v1
kind: Service
metadata:
name: my-deployment
labels:
app: my-deployment
spec:
type: NodePort
ports:
- port: 80
targetPort: 80
nodePort: 80
protocol: TCP
selector:
app: my-deployment
minikube service my-deployment --url now returns http://192.168.99.100:80 as expected and the application is available on port 80.
answered Nov 13 '18 at 1:30
Alexander ZeitlerAlexander Zeitler
3,91242955
edited Nov 13 '18 at 1:39
answered Nov 13 '18 at 1:30
Alexander ZeitlerAlexander Zeitler
3,91242955
answered Nov 13 '18 at 1:30
Alexander ZeitlerAlexander Zeitler
3,91242955
answered Nov 13 '18 at 1:30
Alexander ZeitlerAlexander Zeitler
3,91242955
3,91242955
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53272296%2fminikube-expose-service-on-specific-port%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown