Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

elaborating on the new target service and port selection functionality #80

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

Merged
robertpatrick merged 2 commits into main from target-svc-doc-change
Jan 28, 2022

Conversation

@robertpatrick
Copy link
Member

@robertpatrick robertpatrick commented Jan 28, 2022

No description provided.

Copy link
Contributor

@rosemarymarano rosemarymarano left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

minor edits

- Use the `Virtual Host` and `Path Expression` fields to define the matching rules that determine which requests match this route.
- All requests in the defined rules are routed to the service specified by the `Target Service` field that resides in the namespace specified by the read-only
`Target Service Namespace` field and the port specified by the `Target Port` field. Once the domain has been deployed, you can also select the values from the drop down list.
`Target Service Namespace` field and the port specified by the `Target Port` field. Once the domain has been deployed, you can select the `Target Service`
Copy link
Contributor

@rosemarymarano rosemarymarano Jan 28, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Once -> After (from Oracle editors, once – don’t use to mean after; use only to mean less than twice.)

Copy link
Member Author

@robertpatrick robertpatrick Jan 28, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

- All requests in the defined rules are routed to the service specified by the `Target Service` field that resides in the namespace specified by the read-only
`Target Service Namespace` field and the port specified by the `Target Port` field. Once the domain has been deployed, you can also select the values from the drop down list.
`Target Service Namespace` field and the port specified by the `Target Port` field. Once the domain has been deployed, you can select the `Target Service`
value from the drop-down list of available service in the WebLogic Kubernetes Operator domain's namespace. Once the `Target Service` is selected,
Copy link
Contributor

@rosemarymarano rosemarymarano Jan 28, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

available service -> available services
Once the Target Service is selected -> After the Target Service is selected

Copy link
Member Author

@robertpatrick robertpatrick Jan 28, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

@robertpatrick robertpatrick deleted the target-svc-doc-change branch January 28, 2022 16:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@jshum2479 jshum2479 Awaiting requested review from jshum2479

1 more reviewer

@rosemarymarano rosemarymarano rosemarymarano approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

AltStyle によって変換されたページ (->オリジナル) /