-
Notifications
You must be signed in to change notification settings - Fork 33
new doc on container registries for Codewind #251
new doc on container registries for Codewind #251
Conversation
Signed-off-by: Jacob Berger <jacob.berger@ibm.com>
| @@ -0,0 +1,21 @@ | |||
| --- | |||
| layout: docs | |||
| title: Container registry credentials for Codewind | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We had a discussion with design last week and decided to call them "Image Registries" rather than "Container Registries"
|
|
||
| There are two scenarios in Codewind where you need to specify what container registry to use: | ||
|
|
||
| 1. If you are running in Che and creating a Codewind style project, you need to specify zero or one container registry so Codewind can push images to that specific registry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If they are creating codewind style projects, the definitely need to specify a registry to push to, so change ...you need to specify zero or one container registry... to ...you need to specify an image registry...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jopit also, is it only for Che? I thought it was the same situation for VScode and Eclipse. (all IDE's)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's for Che and for hybrid.
| There are two scenarios in Codewind where you need to specify what container registry to use: | ||
|
|
||
| 1. If you are running in Che and creating a Codewind style project, you need to specify zero or one container registry so Codewind can push images to that specific registry. | ||
| 2. If you are developing an Appsody style project, you need to specify zero or more container registries for Appsody to pull stack images from that specific registry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It might be better to say something like If you are using Codewind running on a remote Kubernetes cluster to develop an Appsody style project and the image registry for the Appsody stack requires credentials, you will need to configure Codewind to use the credentials for the registry
There is also a third scenario, which was added/discovered late last week, If you wish to use Codewind running locally to develop an Appsody style project and the image registry for the Appsody stack requires credentials, you will need to 'docker login' to the registry from the command line before creating the Appsody project
| --- | ||
| # Specifying Container Registries for Codewind | ||
|
|
||
| When you run Codewind on Kubernetes, Codewind uses [`buildah`](https://github.com/containers/buildah) to build container images from Dockerfiles and then push the images to a container registry that you specify. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add a sentence, something like You can use the Image Registry Manager in your Codewind IDE to configure the registry to use
| 1. If you are running in Che and creating a Codewind style project, you need to specify zero or one container registry so Codewind can push images to that specific registry. | ||
| 2. If you are developing an Appsody style project, you need to specify zero or more container registries for Appsody to pull stack images from that specific registry. | ||
|
|
||
| If you are not developing any Codewind style projects, then you are using a public registry with images; in which case, you do not need to specify a container registry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Change then you are using a public registry with images; to something like and you are using an image registry that does not require credentials, then you do not need to specify any image registry
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jopit i slightly disagree with:
and you are using an image registry that does not require credentials, then you do not need to specify any image registry
If they are using an IDE, they dont even know what is being done. Using the an image registry that does not require credentials is simply the default. so maybe it could be something like "and your project does not need the use of an of a private image registry, then the Codewind extension will use a default public registry and you do not need to specify any image registry."
|
@j-c-berger Because the container registries are now called "image registries," please change the file name to |
|
Closing, work being undertaken on PR #261 |
For issue # 1178: eclipse-archived/codewind#1178
@jopit and/or @tetchel here's a first jab at a doc specifying which container registry for the user to use. Let me know if I'm on the right track.
Thanks for all your help.
Signed-off-by: Jacob Berger jacob.berger@ibm.com