Skip to content

Commit a383814

Browse files
committed
OKD lab
1 parent e5d3a08 commit a383814

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

README.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ If any of these are not installed:
3434
## What is **OKD**?
3535

3636
From [okd.io](https://www.okd.io):
37-
>OKD is a distribution of Kubernetes optimized for continuous application development and multi-tenant deployment. OKD adds developer and operations-centric tools on top of Kubernetes to enable rapid application development, easy deployment and scaling, and long-term lifecycle maintenance for small and large teams. OKD is the upstream Kubernetes distribution embedded in Red Hat OpenShift. OKD embeds Kubernetes and extends it with security and other integrated concepts. OKD is also referred to as Origin in github and in the documentation. An OKD release corresponds to the Kubernetes distribution - for example, OKD 1.10 includes Kubernetes 1.10. If you are looking for enterprise-level support, or information on partner certification, Red Hat also offers Red Hat OpenShift Container Platform.
37+
> OKD is a distribution of Kubernetes optimized for continuous application development and multi-tenant deployment. OKD adds developer and operations-centric tools on top of Kubernetes to enable rapid application development, easy deployment and scaling, and long-term lifecycle maintenance for small and large teams. OKD is the upstream Kubernetes distribution embedded in Red Hat OpenShift. OKD embeds Kubernetes and extends it with security and other integrated concepts. OKD is also referred to as Origin in github and in the documentation. An OKD release corresponds to the Kubernetes distribution - for example, OKD 1.10 includes Kubernetes 1.10. If you are looking for enterprise-level support, or information on partner certification, Red Hat also offers Red Hat OpenShift Container Platform.
3838
3939
## What are **Operators**?
4040

@@ -135,9 +135,9 @@ The following steps will build the sample application and create a Docker image
135135
```
136136
If things have gone well, the output should look like this:
137137
```console
138-
REPOSITORY TAG IMAGE ID CREATED SIZE
139-
microservice-vote 1.0.0 8fe8ff1be07d 24 hours ago 369 MB
140-
microservice-enterprise-web 1.0.0 61d03c45ca21 25 hours ago 350 MB
138+
REPOSITORY TAG IMAGE ID CREATED SIZE
139+
microservice-vote 1.0.0 8fe8ff1be07d 24 hours ago 369 MB
140+
microservice-enterprise-web 1.0.0 61d03c45ca21 25 hours ago 350 MB
141141
```
142142

143143
## Part 1B: Upload the Docker image to OKD's internal registry
@@ -175,7 +175,7 @@ If you are using the same VM as the OKD VM, your images will be available in OKD
175175
```
176176
1. Push your image into the registry:
177177
```console
178-
docker push docker-registry.default.svc:5000/myproject/microservice-vote:1.0.0
178+
$ docker push docker-registry.default.svc:5000/myproject/microservice-vote:1.0.0
179179
```
180180
1. You can also see your image the OKD's Registry Dashboard available at `https://registry-console-default.apps.<okd_ip>.nip.io/registry`. You can use the same username and password as the one used in `oc login` command.
181181
1. You skip the next few commands and go to [Part 2](https://github.com/microservices-api/kubernetes-microprofile-lab#part-2-deploy-open-liberty-operator-and-and-couchdb-helm-chart).

0 commit comments

Comments
 (0)