Add doc and blog post about using in-cluster Devfile registries#6689
Conversation
…red in the cluster
✅ Deploy Preview for odo-docusaurus-preview ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
openshift-ci
bot
added
the
area/documentation
rm3l
force-pushed
the
6646-blog-post-devfile-registry-operator-using-in-cluster-registries-with-odo
branch
from
37a4a41 to
7fa2d16
Compare
rm3l
force-pushed
the
6646-blog-post-devfile-registry-operator-using-in-cluster-registries-with-odo
branch
from
7fa2d16 to
09e59cc
Compare
| - `ClusterDevfileRegistriesList`: installable at the cluster level | ||
| - `DevfileRegistriesList`: installable at the namespace level | ||
|
|
||
| More details on the [Devfile Registry Operator documentation](https://github.com/devfile/registry-operator/blob/main/REGISTRIES_LISTS.md). |
There was a problem hiding this comment.
You could add a note that such registries are not necessarily running into the cluster.
|
|
||
| On Kubernetes, the Helm Chart installed above will create an Ingress reachable via a DNS domain named as follows: `devfile-registry-<namespace>.<ingressDomain>`. | ||
|
|
||
| You can get the actual Host by getting the Ingress Resource, via the following command: `kubectl get ingress <registryName>`. |
There was a problem hiding this comment.
nit:
I would add the command in a code block so that it can be copied and is consistent with other code blocks. Same comment for oc get route
| You can get the actual Host by getting the Ingress Resource, via the following command: `kubectl get ingress <registryName>`. | |
| You can get the actual Host by getting the Ingress Resource, via the following command: | |
| ```sh | |
| kubectl get ingress <registryName> |
| DefaultDevfileRegistry https://registry.devfile.io Yes | ||
|
|
||
| ``` | ||
| </details> |
There was a problem hiding this comment.
Perhaps you can add a link to the blog at the end?
| devfile-registry-default.172.20.0.2.nip.io | ||
| ``` | ||
|
|
||
| In this example, the Devfile Registry is now reachable at http://devfile-registry-default.172.20.0.2.nip.io |
There was a problem hiding this comment.
Do you think it would be helpful to add a note that it may take 1 or 2 minutes before the address is accessible?
There was a problem hiding this comment.
Indeed - that could be helpful. Added in 9257b82 (#6689)
…r Devfile registry
…s declared in the cluster
…r Devfile registry
…s declared in the cluster
|
Kudos, SonarCloud Quality Gate passed!
|
openshift-ci
bot
added
the
lgtm
|
/override OpenShift-Integration-tests/OpenShift-Integration-tests Doc-only PR. |
|
@rm3l: /override requires failed status contexts, check run or a prowjob name to operate on.
Only the following failed contexts/checkruns were expected:
If you are trying to override a checkrun that has a space in it, you must put a double quote on the context. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/override ODO-PODMAN-TEST |
|
@rm3l: Overrode contexts on behalf of rm3l: ODO-PODMAN-TEST DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/override OpenShift-Integration-tests/OpenShift-Integration-tests |
|
@rm3l: Overrode contexts on behalf of rm3l: OpenShift-Integration-tests/OpenShift-Integration-tests DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
rm3l
deleted the
6646-blog-post-devfile-registry-operator-using-in-cluster-registries-with-odo
branch
4 participants
What type of PR is this:
/area documentation
What does this PR do / why we need it:
Which issue(s) this PR fixes:
Fixes #6646
PR acceptance criteria:
Unit test
Integration test
Documentation
How to test changes / Special notes to the reviewer: