OSSMDOC-223 Document resource guidelines for OSSM Components. #29981
Conversation
openshift-ci-robot
added
the
size/L
JStickler
added
branch/enterprise-4.6
branch/enterprise-4.7
branch/enterprise-4.8
service-mesh
openshift-ci-robot
added
the
size/L
|
Deploy preview for osdocs ready! Built with commit 6f87049dafea71006515982724970f491ea0e4e8 |
|
@longmuir FYI |
|
Deploy preview for osdocs ready! Built with commit a87438c |
There was a problem hiding this comment.
I'm not sure that these two items fit in the custom resources assembly. I think they might be better in a new assembly more focused on performance and tuning.
But if they are to stay in this assembly, I think they're backwards. The recommended resources module recommends changes but doesn't provide a lot of context about what those changes are or do, but some of that information is introduced in the performance and scalability module.
There was a problem hiding this comment.
@neal Timpe agree with your comments about the new content for recommended resources should go with a new assembly on performance and tuning. I was thinking it should go with the High Availability content, once we finally write that. But we'd discussed putting this content into this assembly until we write those other topics. Are you working on performance and scalability with OSSMDOC-246? Do you want me to just merge these modules and you can add them to your assembly?
There was a problem hiding this comment.
@JStickler I'm not sure. We may have discussed it, but now that I see the content, I don't think this is the right place for it.
I'm not writing performance and scalability content in 246. The way I see it, it's more production configuration. I think it relates to this work you're doing with performance and scalability, but I think it would be okay to put it in its own assembly and add HA to it.
It also might be a question for @heathjoy about where we should put this content while we build other content.
There was a problem hiding this comment.
I created a new assembly for the two new topics. Let me know what you think.
There was a problem hiding this comment.
I think that makes more sense. I think it needs to be added to topicmap.yml, but aside from that, it seems like the right thing.
There was a problem hiding this comment.
D'oh! Added to topic map.
JStickler
force-pushed
the
OSSMDOC-223
branch
3 times, most recently
from
57b8dad to
ed5bfbd
Compare
JStickler
changed the title
|
/cherry-pick enterprise-4.6 |
|
@neal-timpe: new pull request created: #30607 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. |
|
/cherry-pick enterprise-4.7 |
|
@neal-timpe: new pull request created: #30612 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. |
|
/cherry-pick enterprise-4.8 |
|
@neal-timpe: new pull request created: #30613 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. |
6 participants
This PR -
** Performance and Scalability
** Recommended Resources