我使用 Kompose 將 docker-compose 轉換為 Kubernetes 檔案。當我使用在 Docker（沒有 Kubernetes）上運行的影像時，它使用 postgres 卷來保存持久資料。現在，使用相同的 docker-compose，如果我使用 Kompose 創建的檔案在 Kubernetes 上運行，每次啟動 Kubernetes 時，資料庫都是空的。這怎么可能？事實上，如果我查看 Docker Desktop，我發現這些卷沒有“IN USE”標簽。
我怎么做？
先感謝您！
碼頭工人-compose.yaml：
version: '3'
services:
eureka-server:
image: com.petcare/eureka-server:0.0.1-SNAPSHOT
container_name: eureka-server
expose:
- 8761
auth-service:
image: com.petcare/auth-service:0.0.1-SNAPSHOT
container_name: auth-service
expose:
- 8081
depends_on:
- eureka-server
- postgresqldb
map-service:
image: com.petcare/map-service:0.0.1-SNAPSHOT
container_name: map-service
expose:
- 8082
depends_on:
- eureka-server
- postgresqldb
reservation-service:
image: com.petcare/reservation-service:0.0.1-SNAPSHOT
container_name: reservation-service
expose:
- 8083
depends_on:
- eureka-server
- postgresqldb
user-service:
image: com.petcare/user-service:0.0.1-SNAPSHOT
container_name: user-service
expose:
- 8084
depends_on:
- eureka-server
- postgresqldb
api-gateway:
image: com.petcare/api-gateway:0.0.1-SNAPSHOT
container_name: api-gateway
expose:
- 8080
depends_on:
- eureka-server
labels:
kompose.service.type: NodePort
kompose.service.nodeport.port: "30000"
postgresqldb:
image: postgres
container_name: postgres
ports:
- "5432:5432"
environment:
- POSTGRES_PASSWORD=postgres
- POSTGRES_USER=postgres
- POSTGRES_DB=websitepetcare
volumes:
- database-data:/var/lib/postgresql/data/
labels:
kompose.service.type: NodePort
kompose.service.nodeport.port: "30002"
pgadmin:
container_name: pgadmin4_container
image: dpage/pgadmin4
environment:
PGADMIN_DEFAULT_EMAIL: [email protected]
PGADMIN_DEFAULT_PASSWORD: root
PGADMIN_LISTEN_PORT: 50
ports:
- "5050:50"
volumes:
- pgadmin-data:/var/lib/pgadmin
links:
- "postgresqldb:pgsql-server"
depends_on:
- postgresqldb
labels:
kompose.service.type: NodePort
kompose.service.nodeport.port: "30001"
volumes:
database-data:
external: true
pgadmin-data:
external: true
使用 kompose convert 創建的檔案：
apiVersion: v1
items:
- apiVersion: apps/v1
kind: Deployment
metadata:
annotations:
kompose.cmd: C:\ProgramData\chocolatey\lib\kubernetes-kompose\tools\kompose.exe convert -o kubernetes-services-deployments.yaml
kompose.service.nodeport.port: "30001"
kompose.service.type: NodePort
kompose.version: 1.26.0 (40646f47)
creationTimestamp: null
labels:
io.kompose.service: pgadmin
name: pgadmin
spec:
replicas: 1
selector:
matchLabels:
io.kompose.service: pgadmin
strategy:
type: Recreate
template:
metadata:
annotations:
kompose.cmd: C:\ProgramData\chocolatey\lib\kubernetes-kompose\tools\kompose.exe convert -o kubernetes-services-deployments.yaml
kompose.service.nodeport.port: "30001"
kompose.service.type: NodePort
kompose.version: 1.26.0 (40646f47)
creationTimestamp: null
labels:
io.kompose.service: pgadmin
spec:
containers:
- env:
- name: PGADMIN_DEFAULT_EMAIL
value: [email protected]
- name: PGADMIN_DEFAULT_PASSWORD
value: root
- name: PGADMIN_LISTEN_PORT
value: "50"
image: dpage/pgadmin4
name: pgadmin4-container
ports:
- containerPort: 50
resources: {}
volumeMounts:
- mountPath: /var/lib/pgadmin
name: pgadmin-data
restartPolicy: Always
volumes:
- name: pgadmin-data
persistentVolumeClaim:
claimName: pgadmin-data
status: {}
- apiVersion: v1
kind: PersistentVolumeClaim
metadata:
creationTimestamp: null
labels:
io.kompose.service: pgadmin-data
name: pgadmin-data
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 100Mi
status: {}
- apiVersion: apps/v1
kind: Deployment
metadata:
annotations:
kompose.cmd: C:\ProgramData\chocolatey\lib\kubernetes-kompose\tools\kompose.exe convert -o kubernetes-services-deployments.yaml
kompose.service.nodeport.port: "30002"
kompose.service.type: NodePort
kompose.version: 1.26.0 (40646f47)
creationTimestamp: null
labels:
io.kompose.service: postgresqldb
name: postgresqldb
spec:
replicas: 1
selector:
matchLabels:
io.kompose.service: postgresqldb
strategy:
type: Recreate
template:
metadata:
annotations:
kompose.cmd: C:\ProgramData\chocolatey\lib\kubernetes-kompose\tools\kompose.exe convert -o kubernetes-services-deployments.yaml
kompose.service.nodeport.port: "30002"
kompose.service.type: NodePort
kompose.version: 1.26.0 (40646f47)
creationTimestamp: null
labels:
io.kompose.service: postgresqldb
spec:
containers:
- env:
- name: POSTGRES_DB
value: websitepetcare
- name: POSTGRES_PASSWORD
value: postgres
- name: POSTGRES_USER
value: postgres
image: postgres
name: postgres
ports:
- containerPort: 5432
resources: {}
volumeMounts:
- mountPath: /var/lib/postgresql/data/
name: database-data
restartPolicy: Always
volumes:
- name: database-data
persistentVolumeClaim:
claimName: database-data
status: {}
- apiVersion: v1
kind: PersistentVolumeClaim
metadata:
creationTimestamp: null
labels:
io.kompose.service: database-data
name: database-data
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 100Mi
status: {}
kind: List
metadata: {}
uj5u.com熱心網友回復：
您在評論中寫道：
當我想全部洗掉時，我運行以下命令：
kubectl delete -f kubernetesFile.yaml當我再次啟動所有服務時：
kubectl apply -f kubernetesFile.yaml我的資料庫是空的。
Kompose-convertedkubernetesFile.yaml包含所有 Kubernetes 資源，包括告訴它保存持久資料的 PersistentVolumeClaim。因此，當您kubectl delete -f kubernetesFile.yaml洗掉 PersistentVolumeClaim 和資料時，當您重新洗掉時apply，您將獲得一個新的空卷。
你不需要在kubectl delete這里跑。只需kubectl apply -f kubernetesFile.yaml在您的設定更改時運行。任何更新的內容都將被更改，并且集群將根據需要洗掉并重新創建 Pod。任何未更新的內容都將保持不變。如果您洗掉部署或其他資源，則必須手動洗掉 ( kubectl delete deployment unused-deployment)。
轉載請註明出處，本文鏈接：https://www.uj5u.com/houduan/406325.html
標籤：