有没有办法让kubernetes-dashboard显示使用kubectl命令创建的部署和服务,还是只能显示通过其web ui创建的内容?
是否可能需要修改yaml文件中的设置以使其对Web ui可见?我在googles容器引擎中运行kubernetes(1.2.5)。我知道后端过去只支持RC,但这是固定的。
这是我用来创建服务和部署的yaml:
apiVersion: v1
kind: Service
metadata:
name: app-name
labels:
app: nginx
role: api
tier: backend
spec:
type: LoadBalancer
ports:
- port: 80
name: http
- port: 443
name: https
selector:
app: nginx
role: api
tier: backend
---
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
name: app-name
spec:
replicas: 6
template:
metadata:
labels:
app: nginx
role: api
tier: backend
spec:
containers:
- name: survey-node
image: gcr.io/project/app-name:v0.0.1
resources:
requests:
cpu: 300m
memory: 500Mi
这是创建后的部署:
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
annotations:
deployment.kubernetes.io/revision: "3"
creationTimestamp: 2016-07-07T23:22:16Z
generation: 9
labels:
app: app-name
role: app
tier: backend
name: app-name
namespace: default
resourceVersion: "4403"
selfLink: /apis/extensions/v1beta1/namespaces/default/deployments/app-name
uid: *********-***-****-****-************
spec:
replicas: 14
selector:
matchLabels:
app: app-name
role: app
tier: backend
strategy:
rollingUpdate:
maxSurge: 1
maxUnavailable: 1
type: RollingUpdate
template:
metadata:
creationTimestamp: null
labels:
app: app-name
role: app
tier: backend
spec:
containers:
- image: gcr.io/project-name/app-name:v0.0.1
imagePullPolicy: IfNotPresent
name: app-name
resources:
requests:
cpu: 300m
memory: 500Mi
terminationMessagePath: /dev/termination-log
dnsPolicy: ClusterFirst
nodeSelector:
cloud.google.com/gke-nodepool: beef
restartPolicy: Always
securityContext: {}
terminationGracePeriodSeconds: 30
status:
availableReplicas: 14
observedGeneration: 9
replicas: 14
updatedReplicas: 14
答案 0 :(得分:2)
将群集升级到1.3版时,您将自动拥有显示部署和服务的新仪表板。