Merge pull request #32145 from afoster/remove-more-kompose-up-down
Remove kompose up and down command doc
This commit is contained in:
Kubernetes Prow Robot
GitHub
commit
f81bf804fb
|
|
@ -208,7 +208,6 @@ you need is an existing `docker-compose.yml` file.
|
||||||
- CLI
|
- CLI
|
||||||
- [`kompose convert`](#kompose-convert)
|
- [`kompose convert`](#kompose-convert)
|
||||||
- Documentation
|
- Documentation
|
||||||
- [Build and Push Docker Images](#build-and-push-docker-images)
|
|
||||||
- [Alternative Conversions](#alternative-conversions)
|
- [Alternative Conversions](#alternative-conversions)
|
||||||
- [Labels](#labels)
|
- [Labels](#labels)
|
||||||
- [Restart](#restart)
|
- [Restart](#restart)
|
||||||
|
|
@ -326,55 +325,6 @@ INFO OpenShift file "foo-buildconfig.yaml" created
|
||||||
If you are manually pushing the OpenShift artifacts using ``oc create -f``, you need to ensure that you push the imagestream artifact before the buildconfig artifact, to workaround this OpenShift issue: https://github.com/openshift/origin/issues/4518 .
|
If you are manually pushing the OpenShift artifacts using ``oc create -f``, you need to ensure that you push the imagestream artifact before the buildconfig artifact, to workaround this OpenShift issue: https://github.com/openshift/origin/issues/4518 .
|
||||||
{{< /note >}}
|
{{< /note >}}
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Build and Push Docker Images
|
|
||||||
|
|
||||||
Kompose supports both building and pushing Docker images. When using the `build` key within your Docker Compose file, your image will:
|
|
||||||
|
|
||||||
- Automatically be built with Docker using the `image` key specified within your file
|
|
||||||
- Be pushed to the correct Docker repository using local credentials (located at `.docker/config`)
|
|
||||||
|
|
||||||
Using an [example Docker Compose file](https://raw.githubusercontent.com/kubernetes/kompose/master/examples/buildconfig/docker-compose.yml):
|
|
||||||
|
|
||||||
```yaml
|
|
||||||
version: "2"
|
|
||||||
|
|
||||||
services:
|
|
||||||
foo:
|
|
||||||
build: "./build"
|
|
||||||
image: docker.io/foo/bar
|
|
||||||
```
|
|
||||||
|
|
||||||
Using `kompose up` with a `build` key:
|
|
||||||
|
|
||||||
```none
|
|
||||||
kompose up
|
|
||||||
INFO Build key detected. Attempting to build and push image 'docker.io/foo/bar'
|
|
||||||
INFO Building image 'docker.io/foo/bar' from directory 'build'
|
|
||||||
INFO Image 'docker.io/foo/bar' from directory 'build' built successfully
|
|
||||||
INFO Pushing image 'foo/bar:latest' to registry 'docker.io'
|
|
||||||
INFO Attempting authentication credentials 'https://index.docker.io/v1/
|
|
||||||
INFO Successfully pushed image 'foo/bar:latest' to registry 'docker.io'
|
|
||||||
INFO 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 apply -f' commands instead.
|
|
||||||
|
|
||||||
INFO Deploying application in "default" namespace
|
|
||||||
INFO Successfully created Service: foo
|
|
||||||
INFO Successfully created Deployment: foo
|
|
||||||
|
|
||||||
Your application has been deployed to Kubernetes. You can run 'kubectl get deployment,svc,pods,pvc' for details.
|
|
||||||
```
|
|
||||||
|
|
||||||
In order to disable the functionality, or choose to use BuildConfig generation (with OpenShift) `--build (local|build-config|none)` can be passed.
|
|
||||||
|
|
||||||
```sh
|
|
||||||
# Disable building/pushing Docker images
|
|
||||||
kompose up --build none
|
|
||||||
|
|
||||||
# Generate Build Config artifacts for OpenShift
|
|
||||||
kompose up --provider openshift --build build-config
|
|
||||||
```
|
|
||||||
|
|
||||||
## Alternative Conversions
|
## Alternative Conversions
|
||||||
|
|
||||||
The default `kompose` transformation will generate Kubernetes [Deployments](/docs/concepts/workloads/controllers/deployment/) and [Services](/docs/concepts/services-networking/service/), in yaml format. You have alternative option to generate json with `-j`. Also, you can alternatively generate [Replication Controllers](/docs/concepts/workloads/controllers/replicationcontroller/) objects, [Daemon Sets](/docs/concepts/workloads/controllers/daemonset/), or [Helm](https://github.com/helm/helm) charts.
|
The default `kompose` transformation will generate Kubernetes [Deployments](/docs/concepts/workloads/controllers/deployment/) and [Services](/docs/concepts/services-networking/service/), in yaml format. You have alternative option to generate json with `-j`. Also, you can alternatively generate [Replication Controllers](/docs/concepts/workloads/controllers/replicationcontroller/) objects, [Daemon Sets](/docs/concepts/workloads/controllers/daemonset/), or [Helm](https://github.com/helm/helm) charts.
|
||||||
|
|
|
||||||
|
|
@ -121,22 +121,7 @@ En quelques étapes, nous vous emmenons de Docker Compose à Kubernetes. Tous do
|
||||||
kompose.service.type: LoadBalancer
|
kompose.service.type: LoadBalancer
|
||||||
```
|
```
|
||||||
|
|
||||||
2. Lancez la commande `kompose up` pour déployer directement sur Kubernetes, ou passez plutôt à l'étape suivante pour générer un fichier à utiliser avec `kubectl`.
|
2. Pour convertir le fichier `docker-compose.yml` en fichiers que vous pouvez utiliser avec `kubectl`, lancez `kompose convert` et ensuite `kubectl apply -f <output file>`.
|
||||||
|
|
||||||
```bash
|
|
||||||
$ kompose up
|
|
||||||
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 apply -f' commands instead.
|
|
||||||
|
|
||||||
INFO Successfully created Service: redis
|
|
||||||
INFO Successfully created Service: web
|
|
||||||
INFO Successfully created Deployment: redis
|
|
||||||
INFO Successfully created Deployment: web
|
|
||||||
|
|
||||||
Your application has been deployed to Kubernetes. You can run 'kubectl get deployment,svc,pods,pvc' for details.
|
|
||||||
```
|
|
||||||
|
|
||||||
3. Pour convertir le fichier `docker-compose.yml` en fichiers que vous pouvez utiliser avec `kubectl`, lancez `kompose convert` et ensuite `kubectl apply -f <output file>`.
|
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
$ kompose convert
|
$ kompose convert
|
||||||
|
|
@ -160,7 +145,7 @@ En quelques étapes, nous vous emmenons de Docker Compose à Kubernetes. Tous do
|
||||||
|
|
||||||
Vos déploiements fonctionnent sur Kubernetes.
|
Vos déploiements fonctionnent sur Kubernetes.
|
||||||
|
|
||||||
4. Accédez à votre application.
|
3. Accédez à votre application.
|
||||||
|
|
||||||
Si vous utilisez déjà `minikube` pour votre processus de développement :
|
Si vous utilisez déjà `minikube` pour votre processus de développement :
|
||||||
|
|
||||||
|
|
@ -201,10 +186,7 @@ En quelques étapes, nous vous emmenons de Docker Compose à Kubernetes. Tous do
|
||||||
|
|
||||||
- CLI
|
- CLI
|
||||||
- [`kompose convert`](#kompose-convert)
|
- [`kompose convert`](#kompose-convert)
|
||||||
- [`kompose up`](#kompose-up)
|
|
||||||
- [`kompose down`](#kompose-down)
|
|
||||||
- Documentation
|
- Documentation
|
||||||
- [Construire et pousser des images de docker](#build-and-push-docker-images)
|
|
||||||
- [Conversions alternatives](#alternative-conversions)
|
- [Conversions alternatives](#alternative-conversions)
|
||||||
- [Etiquettes](#labels)
|
- [Etiquettes](#labels)
|
||||||
- [Redémarrage](#restart)
|
- [Redémarrage](#restart)
|
||||||
|
|
@ -301,152 +283,6 @@ INFO OpenShift file "foo-buildconfig.yaml" created
|
||||||
Si vous poussez manuellement les artefacts OpenShift en utilisant ``oc create -f``, vous devez vous assurer que vous poussez l'artefact imagestream avant l'artefact buildconfig, pour contourner ce problème OpenShift : https://github.com/openshift/origin/issues/4518 .
|
Si vous poussez manuellement les artefacts OpenShift en utilisant ``oc create -f``, vous devez vous assurer que vous poussez l'artefact imagestream avant l'artefact buildconfig, pour contourner ce problème OpenShift : https://github.com/openshift/origin/issues/4518 .
|
||||||
{{< /note >}}
|
{{< /note >}}
|
||||||
|
|
||||||
## `kompose up`
|
|
||||||
|
|
||||||
Kompose propose un moyen simple de déployer votre application "composée" sur Kubernetes ou OpenShift via `kompose up`.
|
|
||||||
|
|
||||||
|
|
||||||
### Kubernetes
|
|
||||||
```sh
|
|
||||||
$ kompose --file ./examples/docker-guestbook.yml up
|
|
||||||
We are going to create Kubernetes deployments and services for your Dockerized application.
|
|
||||||
If you need different kind of resources, use the 'kompose convert' and 'kubectl apply -f' commands instead.
|
|
||||||
|
|
||||||
INFO Successfully created service: redis-master
|
|
||||||
INFO Successfully created service: redis-slave
|
|
||||||
INFO Successfully created service: frontend
|
|
||||||
INFO Successfully created deployment: redis-master
|
|
||||||
INFO Successfully created deployment: redis-slave
|
|
||||||
INFO Successfully created deployment: frontend
|
|
||||||
|
|
||||||
Your application has been deployed to Kubernetes. You can run 'kubectl get deployment,svc,pods' for details.
|
|
||||||
|
|
||||||
$ kubectl get deployment,svc,pods
|
|
||||||
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
|
|
||||||
deployment.extensions/frontend 1 1 1 1 4m
|
|
||||||
deployment.extensions/redis-master 1 1 1 1 4m
|
|
||||||
deployment.extensions/redis-slave 1 1 1 1 4m
|
|
||||||
|
|
||||||
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
|
|
||||||
service/frontend ClusterIP 10.0.174.12 <none> 80/TCP 4m
|
|
||||||
service/kubernetes ClusterIP 10.0.0.1 <none> 443/TCP 13d
|
|
||||||
service/redis-master ClusterIP 10.0.202.43 <none> 6379/TCP 4m
|
|
||||||
service/redis-slave ClusterIP 10.0.1.85 <none> 6379/TCP 4m
|
|
||||||
|
|
||||||
NAME READY STATUS RESTARTS AGE
|
|
||||||
pod/frontend-2768218532-cs5t5 1/1 Running 0 4m
|
|
||||||
pod/redis-master-1432129712-63jn8 1/1 Running 0 4m
|
|
||||||
pod/redis-slave-2504961300-nve7b 1/1 Running 0 4m
|
|
||||||
```
|
|
||||||
|
|
||||||
**Note**:
|
|
||||||
|
|
||||||
- Vous devez avoir un cluster Kubernetes en cours d'exécution avec kubectl pré-configuré.
|
|
||||||
- Seuls les déploiements et les services sont générés et déployés dans Kubernetes. Si vous avez besoin d'autres types de ressources, utilisez les commandes `kompose convert` et `kubectl apply -f` à la place.
|
|
||||||
|
|
||||||
### OpenShift
|
|
||||||
```sh
|
|
||||||
$ kompose --file ./examples/docker-guestbook.yml --provider openshift up
|
|
||||||
We are going to create OpenShift DeploymentConfigs and Services for your Dockerized application.
|
|
||||||
If you need different kind of resources, use the 'kompose convert' and 'oc create -f' commands instead.
|
|
||||||
|
|
||||||
INFO Successfully created service: redis-slave
|
|
||||||
INFO Successfully created service: frontend
|
|
||||||
INFO Successfully created service: redis-master
|
|
||||||
INFO Successfully created deployment: redis-slave
|
|
||||||
INFO Successfully created ImageStream: redis-slave
|
|
||||||
INFO Successfully created deployment: frontend
|
|
||||||
INFO Successfully created ImageStream: frontend
|
|
||||||
INFO Successfully created deployment: redis-master
|
|
||||||
INFO Successfully created ImageStream: redis-master
|
|
||||||
|
|
||||||
Your application has been deployed to OpenShift. You can run 'oc get dc,svc,is' for details.
|
|
||||||
|
|
||||||
$ oc get dc,svc,is
|
|
||||||
NAME REVISION DESIRED CURRENT TRIGGERED BY
|
|
||||||
dc/frontend 0 1 0 config,image(frontend:v4)
|
|
||||||
dc/redis-master 0 1 0 config,image(redis-master:e2e)
|
|
||||||
dc/redis-slave 0 1 0 config,image(redis-slave:v1)
|
|
||||||
NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE
|
|
||||||
svc/frontend 172.30.46.64 <none> 80/TCP 8s
|
|
||||||
svc/redis-master 172.30.144.56 <none> 6379/TCP 8s
|
|
||||||
svc/redis-slave 172.30.75.245 <none> 6379/TCP 8s
|
|
||||||
NAME DOCKER REPO TAGS UPDATED
|
|
||||||
is/frontend 172.30.12.200:5000/fff/frontend
|
|
||||||
is/redis-master 172.30.12.200:5000/fff/redis-master
|
|
||||||
is/redis-slave 172.30.12.200:5000/fff/redis-slave v1
|
|
||||||
```
|
|
||||||
|
|
||||||
**Note**:
|
|
||||||
|
|
||||||
- Vous devez avoir un cluster OpenShift en cours d'exécution avec `oc` pré-configuré (`oc login`)
|
|
||||||
|
|
||||||
## `kompose down`
|
|
||||||
|
|
||||||
Une fois que vous avez déployé l'application "composée" sur Kubernetes, `$ kompose down` vous
|
|
||||||
facilitera la suppression de l'application en supprimant ses déploiements et services. Si vous avez besoin de supprimer d'autres ressources, utilisez la commande 'kubectl'.
|
|
||||||
|
|
||||||
```sh
|
|
||||||
$ kompose --file docker-guestbook.yml down
|
|
||||||
INFO Successfully deleted service: redis-master
|
|
||||||
INFO Successfully deleted deployment: redis-master
|
|
||||||
INFO Successfully deleted service: redis-slave
|
|
||||||
INFO Successfully deleted deployment: redis-slave
|
|
||||||
INFO Successfully deleted service: frontend
|
|
||||||
INFO Successfully deleted deployment: frontend
|
|
||||||
```
|
|
||||||
|
|
||||||
**Note**:
|
|
||||||
|
|
||||||
- Vous devez avoir un cluster Kubernetes en cours d'exécution avec kubectl pré-configuré.
|
|
||||||
|
|
||||||
## Construire et pousser des images de docker
|
|
||||||
|
|
||||||
Kompose permet de construire et de pousser des images Docker. Lorsque vous utilisez la clé `build` dans votre fichier Docker Compose, votre image sera :
|
|
||||||
|
|
||||||
- Automatiquement construite avec le Docker en utilisant la clé "image" spécifiée dans votre fichier
|
|
||||||
- Être poussé vers le bon dépôt Docker en utilisant les identifiants locaux (situés dans `.docker/config`)
|
|
||||||
|
|
||||||
Utilisation d'un [exemple de fichier Docker Compose](https://raw.githubusercontent.com/kubernetes/kompose/master/examples/buildconfig/docker-compose.yml):
|
|
||||||
|
|
||||||
```yaml
|
|
||||||
version: "2"
|
|
||||||
|
|
||||||
services:
|
|
||||||
foo:
|
|
||||||
build: "./build"
|
|
||||||
image: docker.io/foo/bar
|
|
||||||
```
|
|
||||||
|
|
||||||
En utilisant `kompose up` avec une clé `build` :
|
|
||||||
|
|
||||||
```none
|
|
||||||
$ kompose up
|
|
||||||
INFO Build key detected. Attempting to build and push image 'docker.io/foo/bar'
|
|
||||||
INFO Building image 'docker.io/foo/bar' from directory 'build'
|
|
||||||
INFO Image 'docker.io/foo/bar' from directory 'build' built successfully
|
|
||||||
INFO Pushing image 'foo/bar:latest' to registry 'docker.io'
|
|
||||||
INFO Attempting authentication credentials 'https://index.docker.io/v1/
|
|
||||||
INFO Successfully pushed image 'foo/bar:latest' to registry 'docker.io'
|
|
||||||
INFO 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 apply -f' commands instead.
|
|
||||||
|
|
||||||
INFO Deploying application in "default" namespace
|
|
||||||
INFO Successfully created Service: foo
|
|
||||||
INFO Successfully created Deployment: foo
|
|
||||||
|
|
||||||
Your application has been deployed to Kubernetes. You can run 'kubectl get deployment,svc,pods,pvc' for details.
|
|
||||||
```
|
|
||||||
|
|
||||||
Afin de désactiver cette fonctionnalité, ou de choisir d'utiliser la génération de BuildConfig (avec OpenShift) `--build (local|build-config|none)` peut être passé.
|
|
||||||
|
|
||||||
```sh
|
|
||||||
# Désactiver la construction/poussée d'images Docker
|
|
||||||
$ kompose up --build none
|
|
||||||
|
|
||||||
# Générer des artefacts de Build Config pour OpenShift
|
|
||||||
$ kompose up --provider openshift --build build-config
|
|
||||||
```
|
|
||||||
|
|
||||||
## Autres conversions
|
## Autres conversions
|
||||||
|
|
||||||
La transformation par défaut `komposer` va générer des [Déploiements](/docs/concepts/workloads/controllers/deployment/) et [Services](/docs/concepts/services-networking/service/) de Kubernetes, au format yaml. Vous avez une autre option pour générer json avec `-j`. Vous pouvez aussi générer des objets de [Replication Controllers](/docs/concepts/workloads/controllers/replicationcontroller/), [Daemon Sets](/docs/concepts/workloads/controllers/daemonset/), ou [Helm](https://github.com/helm/helm) charts.
|
La transformation par défaut `komposer` va générer des [Déploiements](/docs/concepts/workloads/controllers/deployment/) et [Services](/docs/concepts/services-networking/service/) de Kubernetes, au format yaml. Vous avez une autre option pour générer json avec `-j`. Vous pouvez aussi générer des objets de [Replication Controllers](/docs/concepts/workloads/controllers/replicationcontroller/), [Daemon Sets](/docs/concepts/workloads/controllers/daemonset/), ou [Helm](https://github.com/helm/helm) charts.
|
||||||
|
|
|
||||||
|
|
@ -285,10 +285,7 @@ you need is an existing `docker-compose.yml` file.
|
||||||
<!--
|
<!--
|
||||||
- CLI
|
- CLI
|
||||||
- [`kompose convert`](#kompose-convert)
|
- [`kompose convert`](#kompose-convert)
|
||||||
- [`kompose up`](#kompose-up)
|
|
||||||
- [`kompose down`](#kompose-down)
|
|
||||||
- Documentation
|
- Documentation
|
||||||
- [Build and Push Docker Images](#build-and-push-docker-images)
|
|
||||||
- [Alternative Conversions](#alternative-conversions)
|
- [Alternative Conversions](#alternative-conversions)
|
||||||
- [Labels](#labels)
|
- [Labels](#labels)
|
||||||
- [Restart](#restart)
|
- [Restart](#restart)
|
||||||
|
|
@ -296,11 +293,8 @@ you need is an existing `docker-compose.yml` file.
|
||||||
-->
|
-->
|
||||||
- CLI
|
- CLI
|
||||||
- [`kompose convert`](#kompose-convert)
|
- [`kompose convert`](#kompose-convert)
|
||||||
- [`kompose up`](#kompose-up)
|
|
||||||
- [`kompose down`](#kompose-down)
|
|
||||||
|
|
||||||
- 文档
|
- 文档
|
||||||
- [构建和推送 Docker 镜像](#build-and-push-docker-images)
|
|
||||||
- [其他转换方式](#其他转换方式)
|
- [其他转换方式](#其他转换方式)
|
||||||
- [标签](#labels)
|
- [标签](#labels)
|
||||||
- [重启](#restart)
|
- [重启](#restart)
|
||||||
|
|
@ -447,219 +441,6 @@ If you are manually pushing the Openshift artifacts using ``oc create -f``, you
|
||||||
imagestream 工件，以解决 Openshift 的这个问题：https://github.com/openshift/origin/issues/4518 。
|
imagestream 工件，以解决 Openshift 的这个问题：https://github.com/openshift/origin/issues/4518 。
|
||||||
{{< /note >}}
|
{{< /note >}}
|
||||||
|
|
||||||
## `kompose up`
|
|
||||||
|
|
||||||
<!--
|
|
||||||
Kompose supports a straightforward way to deploy your "composed" application to Kubernetes or OpenShift via `kompose up`.
|
|
||||||
-->
|
|
||||||
Kompose 支持通过 `kompose up` 直接将你的"复合的（composed）" 应用程序
|
|
||||||
部署到 Kubernetes 或 OpenShift。
|
|
||||||
|
|
||||||
<!--
|
|
||||||
### Kubernetes `kompose up` example
|
|
||||||
-->
|
|
||||||
### Kubernetes `kompose up` 示例
|
|
||||||
|
|
||||||
```shell
|
|
||||||
kompose --file ./examples/docker-guestbook.yml up
|
|
||||||
```
|
|
||||||
|
|
||||||
```none
|
|
||||||
We are going to create Kubernetes deployments and services for your Dockerized application.
|
|
||||||
If you need different kind of resources, use the 'kompose convert' and 'kubectl create -f' commands instead.
|
|
||||||
|
|
||||||
INFO Successfully created service: redis-master
|
|
||||||
INFO Successfully created service: redis-slave
|
|
||||||
INFO Successfully created service: frontend
|
|
||||||
INFO Successfully created deployment: redis-master
|
|
||||||
INFO Successfully created deployment: redis-slave
|
|
||||||
INFO Successfully created deployment: frontend
|
|
||||||
|
|
||||||
Your application has been deployed to Kubernetes. You can run 'kubectl get deployment,svc,pods' for details.
|
|
||||||
```
|
|
||||||
|
|
||||||
```shell
|
|
||||||
kubectl get deployment,svc,pods
|
|
||||||
```
|
|
||||||
|
|
||||||
```
|
|
||||||
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
|
|
||||||
deployment.extensions/frontend 1 1 1 1 4m
|
|
||||||
deployment.extensions/redis-master 1 1 1 1 4m
|
|
||||||
deployment.extensions/redis-slave 1 1 1 1 4m
|
|
||||||
|
|
||||||
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
|
|
||||||
service/frontend ClusterIP 10.0.174.12 <none> 80/TCP 4m
|
|
||||||
service/kubernetes ClusterIP 10.0.0.1 <none> 443/TCP 13d
|
|
||||||
service/redis-master ClusterIP 10.0.202.43 <none> 6379/TCP 4m
|
|
||||||
service/redis-slave ClusterIP 10.0.1.85 <none> 6379/TCP 4m
|
|
||||||
|
|
||||||
NAME READY STATUS RESTARTS AGE
|
|
||||||
pod/frontend-2768218532-cs5t5 1/1 Running 0 4m
|
|
||||||
pod/redis-master-1432129712-63jn8 1/1 Running 0 4m
|
|
||||||
pod/redis-slave-2504961300-nve7b 1/1 Running 0 4m
|
|
||||||
```
|
|
||||||
|
|
||||||
|
|
||||||
{{< note >}}
|
|
||||||
<!--
|
|
||||||
- You must have a running Kubernetes cluster with a pre-configured kubectl context.
|
|
||||||
- Only deployments and services are generated and deployed to Kubernetes. If you need different kind of resources, use the `kompose convert` and `kubectl create -f` commands instead.
|
|
||||||
-->
|
|
||||||
- 你必须有一个运行正常的 Kubernetes 集群，该集群具有预先配置的 kubectl 上下文。
|
|
||||||
- 此操作仅生成 Deployment 和 Service 对象并将其部署到 Kubernetes。
|
|
||||||
如果需要部署其他不同类型的资源，请使用 `kompose convert` 和 `kubectl create -f` 命令。
|
|
||||||
{{< /note >}}
|
|
||||||
|
|
||||||
<!--
|
|
||||||
### OpenShift `kompose up` example
|
|
||||||
-->
|
|
||||||
### OpenShift `kompose up` 示例
|
|
||||||
|
|
||||||
```shell
|
|
||||||
kompose --file ./examples/docker-guestbook.yml --provider openshift up
|
|
||||||
```
|
|
||||||
|
|
||||||
```none
|
|
||||||
We are going to create OpenShift DeploymentConfigs and Services for your Dockerized application.
|
|
||||||
If you need different kind of resources, use the 'kompose convert' and 'oc create -f' commands instead.
|
|
||||||
|
|
||||||
INFO Successfully created service: redis-slave
|
|
||||||
INFO Successfully created service: frontend
|
|
||||||
INFO Successfully created service: redis-master
|
|
||||||
INFO Successfully created deployment: redis-slave
|
|
||||||
INFO Successfully created ImageStream: redis-slave
|
|
||||||
INFO Successfully created deployment: frontend
|
|
||||||
INFO Successfully created ImageStream: frontend
|
|
||||||
INFO Successfully created deployment: redis-master
|
|
||||||
INFO Successfully created ImageStream: redis-master
|
|
||||||
|
|
||||||
Your application has been deployed to OpenShift. You can run 'oc get dc,svc,is' for details.
|
|
||||||
```
|
|
||||||
|
|
||||||
```shell
|
|
||||||
oc get dc,svc,is
|
|
||||||
```
|
|
||||||
|
|
||||||
```none
|
|
||||||
NAME REVISION DESIRED CURRENT TRIGGERED BY
|
|
||||||
dc/frontend 0 1 0 config,image(frontend:v4)
|
|
||||||
dc/redis-master 0 1 0 config,image(redis-master:e2e)
|
|
||||||
dc/redis-slave 0 1 0 config,image(redis-slave:v1)
|
|
||||||
NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE
|
|
||||||
svc/frontend 172.30.46.64 <none> 80/TCP 8s
|
|
||||||
svc/redis-master 172.30.144.56 <none> 6379/TCP 8s
|
|
||||||
svc/redis-slave 172.30.75.245 <none> 6379/TCP 8s
|
|
||||||
NAME DOCKER REPO TAGS UPDATED
|
|
||||||
is/frontend 172.30.12.200:5000/fff/frontend
|
|
||||||
is/redis-master 172.30.12.200:5000/fff/redis-master
|
|
||||||
is/redis-slave 172.30.12.200:5000/fff/redis-slave v1
|
|
||||||
```
|
|
||||||
|
|
||||||
{{< note >}}
|
|
||||||
<!--
|
|
||||||
You must have a running OpenShift cluster with a pre-configured `oc` context (`oc login`)
|
|
||||||
-->
|
|
||||||
你必须有一个运行正常的 OpenShift 集群，该集群具有预先配置的 `oc` 上下文 (`oc login`)。
|
|
||||||
{{< /note >}}
|
|
||||||
|
|
||||||
## `kompose down`
|
|
||||||
|
|
||||||
<!--
|
|
||||||
Once you have deployed "composed" application to Kubernetes, `$ kompose down` will help you to take the application out by deleting its deployments and services. If you need to remove other resources, use the 'kubectl' command.
|
|
||||||
-->
|
|
||||||
你一旦将"复合(composed)" 应用部署到 Kubernetes，`kompose down`
|
|
||||||
命令将能帮你通过删除 Deployment 和 Service 对象来删除应用。
|
|
||||||
如果需要删除其他资源，请使用 'kubectl' 命令。
|
|
||||||
|
|
||||||
```shell
|
|
||||||
kompose --file docker-guestbook.yml down
|
|
||||||
```
|
|
||||||
|
|
||||||
```
|
|
||||||
INFO Successfully deleted service: redis-master
|
|
||||||
INFO Successfully deleted deployment: redis-master
|
|
||||||
INFO Successfully deleted service: redis-slave
|
|
||||||
INFO Successfully deleted deployment: redis-slave
|
|
||||||
INFO Successfully deleted service: frontend
|
|
||||||
INFO Successfully deleted deployment: frontend
|
|
||||||
```
|
|
||||||
|
|
||||||
{{< note >}}
|
|
||||||
<!--
|
|
||||||
You must have a running Kubernetes cluster with a pre-configured kubectl context.
|
|
||||||
-->
|
|
||||||
- 你必须有一个运行正常的 Kubernetes 集群，该集群具有预先配置的 kubectl 上下文。
|
|
||||||
{{< /note >}}
|
|
||||||
|
|
||||||
<!--
|
|
||||||
## Build and Push Docker Images
|
|
||||||
|
|
||||||
Kompose supports both building and pushing Docker images. When using the `build` key within your Docker Compose file, your image will:
|
|
||||||
|
|
||||||
- Automatically be built with Docker using the `image` key specified within your file
|
|
||||||
- Be pushed to the correct Docker repository using local credentials (located at `.docker/config`)
|
|
||||||
|
|
||||||
Using an [example Docker Compose file](https://raw.githubusercontent.com/kubernetes/kompose/master/examples/buildconfig/docker-compose.yml):
|
|
||||||
-->
|
|
||||||
## 构建和推送 Docker 镜像 {#build-and-push-docker-images}
|
|
||||||
|
|
||||||
Kompose 支持构建和推送 Docker 镜像。如果 Docker Compose 文件中使用了 `build`
|
|
||||||
关键字，你的镜像将会：
|
|
||||||
|
|
||||||
- 使用文档中指定的 `image` 键自动构建 Docker 镜像
|
|
||||||
- 使用本地凭据推送到正确的 Docker 仓库
|
|
||||||
|
|
||||||
使用 [Docker Compose 文件示例](https://raw.githubusercontent.com/kubernetes/kompose/master/examples/buildconfig/docker-compose.yml)
|
|
||||||
|
|
||||||
```yaml
|
|
||||||
version: "2"
|
|
||||||
|
|
||||||
services:
|
|
||||||
foo:
|
|
||||||
build: "./build"
|
|
||||||
image: docker.io/foo/bar
|
|
||||||
```
|
|
||||||
|
|
||||||
<!--
|
|
||||||
Using `kompose up` with a `build` key:
|
|
||||||
-->
|
|
||||||
使用带有 `build` 键的 `kompose up` 命令：
|
|
||||||
|
|
||||||
```shell
|
|
||||||
kompose up
|
|
||||||
```
|
|
||||||
|
|
||||||
```none
|
|
||||||
INFO Build key detected. Attempting to build and push image 'docker.io/foo/bar'
|
|
||||||
INFO Building image 'docker.io/foo/bar' from directory 'build'
|
|
||||||
INFO Image 'docker.io/foo/bar' from directory 'build' built successfully
|
|
||||||
INFO Pushing image 'foo/bar:latest' to registry 'docker.io'
|
|
||||||
INFO Attempting authentication credentials 'https://index.docker.io/v1/
|
|
||||||
INFO Successfully pushed image 'foo/bar:latest' to registry 'docker.io'
|
|
||||||
INFO 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: foo
|
|
||||||
INFO Successfully created Deployment: foo
|
|
||||||
|
|
||||||
Your application has been deployed to Kubernetes. You can run 'kubectl get deployment,svc,pods,pvc' for details.
|
|
||||||
```
|
|
||||||
|
|
||||||
<!--
|
|
||||||
In order to disable the functionality, or choose to use BuildConfig generation (with OpenShift) `--build (local|build-config|none)` can be passed.
|
|
||||||
-->
|
|
||||||
要想禁用该功能，或者使用 BuildConfig 中的版本（在 OpenShift 中），
|
|
||||||
可以通过传递 `--build (local|build-config|none)` 参数来实现。
|
|
||||||
|
|
||||||
```shell
|
|
||||||
# 禁止构造和推送 Docker 镜像
|
|
||||||
kompose up --build none
|
|
||||||
|
|
||||||
# 为 OpenShift 生成 Build Config 工件
|
|
||||||
kompose up --provider openshift --build build-config
|
|
||||||
```
|
|
||||||
|
|
||||||
<!--
|
<!--
|
||||||
## Alternative Conversions
|
## Alternative Conversions
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue