kompose not exposing NodePort - Docker for Desktop Windows

Question

我有这个docker-compose.yml和Docker for Desktop Windows，运行本地kubernetes集群(默认的docker-desktop上下文(：

version: '3'
services:
web:
image: customnode
ports:
- "3000:3000"
labels:
kompose.service.type: nodeport
datastore:
image: custommongo
ports:
- "27017:27017"

docker-compose up -d运行良好，并在端口3000上公开我的 NodeJS127.0.0.1.

我正在尝试迁移我的 k8s 集群，因此遵循 https://kompose.io/getting-started/

上面的页面说"如果你还没有运行 Kubernetes 集群，minikube 是最好的入门方式"......我已经在运行桌面集群的OOTB Docker，所以我假设我不需要minikube。

kompose convert
INFO Kubernetes file "datastore-service.yaml" created
INFO Kubernetes file "web-service.yaml" created
INFO Kubernetes file "datastore-deployment.yaml" created
INFO Kubernetes file "web-deployment.yaml" created

以下是 Web 部署和 Web 服务 YAMLS：

apiVersion: extensions/v1beta1
kind: Deployment
metadata:
annotations:
kompose.cmd: kompose convert
kompose.service.type: nodeport
kompose.version: 1.16.0 (0c01309)
creationTimestamp: null
labels:
io.kompose.service: web
name: web
spec:
replicas: 1
strategy: {}
template:
metadata:
creationTimestamp: null
labels:
io.kompose.service: web
spec:
containers:
image: customnode
name: web
ports:
- containerPort: 3000
resources: {}
restartPolicy: Always
status: {}
apiVersion: v1
kind: Service
metadata:
annotations:
kompose.cmd: kompose convert
kompose.service.type: nodeport
kompose.version: 1.16.0 (0c01309)
creationTimestamp: null
labels:
io.kompose.service: web
name: web
spec:
ports:
- name: "3000"
port: 3000
targetPort: 3000
selector:
io.kompose.service: web
type: NodePort
status:
loadBalancer: {}

最后，运行kompose up：

kompose up
[36mINFO[0m We are going to create Kubernetes Deployments, Services and PersistentVolumeClaims for your Dockerized application. If you need different kind of resources, use the 'kompose convert' and 'kubectl create -f' commands instead.
INFO Deploying application in "default" namespace
INFO Successfully created Service: datastore
INFO Successfully created Service: web
INFO Successfully created Deployment: datastore
INFO Successfully created Deployment: web

kubectl get svc输出 ：

kubectl get svc
NAME         TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)          AGE
datastore    ClusterIP   10.103.***.***   <none>        27017/TCP        76s
kubernetes   ClusterIP   10.96.0.1        <none>        443/TCP          23m
web          NodePort    10.106.***.***     <none>        3000:32033/TCP   76s

如您所见，没有我期望的外部IP。我敢肯定这是我缺乏知识，而不是错误，所以我错过了什么？

Answer 1

External IP 仅分配给LoadBalancer类型服务。必须在群集上安装LoadBalancer控制器LoadBalancer服务才能正常工作。否则LoadBalancer服务的行为与NodePort服务完全相同。大多数云提供商都支持LoadBalancer服务。

对于NodePort类型的服务，服务绑定到所有节点上节点端口范围内的随机端口。在您的情况下，您可以看到，该服务绑定到端口 32033 -3000:32033/TCP。

节点端口范围配置为 Kubernetes API 服务器的参数，选项为--service-node-port-range(默认为 30000-32767(。创建 NodePort 类型服务时，将从此范围中选取一个随机空闲端口。如果要选择自定义端口，可以在Port对象中指定nodePort属性。

例如：

apiVersion: v1
kind: Service
metadata:
annotations:
kompose.cmd: kompose convert
kompose.service.type: nodeport
kompose.version: 1.16.0 (0c01309)
creationTimestamp: null
labels:
io.kompose.service: web
name: web
spec:
ports:
- name: "3000"
port: 3000
targetPort: 3000
nodePort: 30002         ###### You can choose node port here if needed
selector:
io.kompose.service: web
type: NodePort           ####### Change this line to LoadBalancer if you want an external IP
status:
loadBalancer: {}