-
Notifications
You must be signed in to change notification settings - Fork 244
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
List Routes/Ingresses created by odo deploy
in odo describe component
#6244
List Routes/Ingresses created by odo deploy
in odo describe component
#6244
Conversation
✅ Deploy Preview for odo-docusaurus-preview ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
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.
Added a few comments below.
Also, can you update the "Deploying application" User Guides to mention this new capability? At least for OpenShift, this will be helpful to determine how to access the application, which was one of the main reasons behind this issue.
…instead by add a selector argument to it Signed-off-by: Parthvi Vala <[email protected]>
Co-authored-by: Armel Soro <[email protected]>
4b5f544
to
129fa38
Compare
Co-authored-by: Philippe Martin <[email protected]>
/retest-required |
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.
Thanks for your work on this. LGTM feature-wise.
Added a few minor comments.
Also, I think there is one last thing missing from the Acceptance Criteria:
We should update the Quickstart Guide accordingly, by showing how to access the deployed application
Could you update the "Deploying application" guides accordingly? Currently, they are mentioning Test your application by visiting the DOMAIN_NAME variable that you had set in the devfile.yaml.
, but this won't work with OpenShift (we are not using DOMAIN_NAME
). So using odo describe component
could be helpful (at least for OpenShift)
Maybe by adding a "Step 5. Accessing the application" section in those guides, and tabs for Kubernetes and OpenShift?
(But this can be done in a subsequent PR if you prefer to have this merged first).
Yes, please. I'll open a separate PR for this. |
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.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rm3l The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Ok. I created this issue for the record: #6319 |
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
/override ci/prow/v4.11-integration-e2e Tests passing on IBM Cloud. |
@rm3l: Overrode contexts on behalf of rm3l: ci/prow/v4.11-integration-e2e In 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. |
What type of PR is this:
/kind feature
What does this PR do / why we need it:
Which issue(s) this PR fixes:
Fixes #5990
PR acceptance criteria:
Unit test
Integration test
Documentation
How to test changes / Special notes to the reviewer:
odo deploy
.odo describe component
to see if the URLs are printed.