-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
OSSMDOC-259: OSD changes. Peer review done, waiting for coordination with other teams. #30066
Conversation
neal-timpe
commented
Mar 3, 2021
•
edited
edited
- Aligned team: Service mesh
- For branches: 4.6, 4.7, 4.8
- https://issues.redhat.com/browse/OSSMDOC-259
- At each mention of cluster-admin, adds a sentence that says if you're using dedicated, the role is dedicated admin.
- This work makes changes so we can use this content for OSD also.
- SME review: knrc
- QE review: tvieira, gbaufake
- Peer review: JStickler, mikemckiernan
✔️ Deploy Preview for osdocs ready! 🔨 Explore the source changes: e5d36ee 🔍 Inspect the deploy log: https://app.netlify.com/sites/osdocs/deploys/60d4f16db317fe00082cb3ea 😎 Browse the preview: https://deploy-preview-30066--osdocs.netlify.app |
@neal-timpe Was it not possible to go with a generic admin term and then define that to be cluster-admin/dedicated-admin in a single location? For example
Then we could just refer to an admin account in the body of the docs. |
@knrc Heather and I considered that approach, but decided that the way the our content is structured that it would be better to do it this way. |
@neal-timpe okay thanks, in that case lgtm |
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.
LGTM
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.
The installing-ossm assembly pulls in jaeger-install-elasticsearch and jaeger-install, which haven't been updated by this PR.
6068182
to
5c829ff
Compare
modules/ossm-vs-istio.adoc
Outdated
@@ -106,7 +106,7 @@ A {ProductName} control plane component called Istio OpenShift Routing (IOR) syn | |||
|
|||
[id="ossm-catch-all-domains_{context}"] | |||
=== Catch-all domains | |||
Catch-all domains ("\*") are not supported. If one is found in the Gateway definition, {ProductName} _will_ create the route, but will rely on OpenShift to create a default hostname. This means that the newly created route will __not__ be a catch all ("*") route, instead it will have a hostname in the form `<route-name>[-<project>].<suffix>`. Refer to the OpenShift documentation for more information about how default hostnames work and how a cluster administrator can customize it. | |||
Catch-all domains ("\*") are not supported. If one is found in the Gateway definition, {ProductName} _will_ create the route, but will rely on OpenShift to create a default hostname. This means that the newly created route will __not__ be a catch all ("*") route, instead it will have a hostname in the form `<route-name>[-<project>].<suffix>`. Refer to the OpenShift documentation for more information about how default hostnames work and how a `cluster-admin` can customize it. If you are using {product-dedicated}, refer to the {product-dedicated} the `dedicated-admin` role. |
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.
I don't expect you to remove the future tense and markup from the para, but I sure hope someone does.
The "OpenShift" alone in that para is making my other eye twitch. That should probably be an attribute that expands to "OpenShift Container Platform."
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.
I have one sugg to sidestep "using." If you agree with it, seems like it gets applied throughout.
cbc4836
to
0bf4022
Compare
/cherrypick enterprise-4.8 |
@mikemckiernan: new pull request created: #33950 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. |
/cherrypick enterprise-4.7 |
@mikemckiernan: new pull request created: #33951 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. |
/cherrypick enterprise-4.6 |
@mikemckiernan: #30066 failed to apply on top of branch "enterprise-4.6":
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. |