OSDOCS-17114: microshift networking CQA pt1#107224
OSDOCS-17114: microshift networking CQA pt1#107224jldohmann wants to merge 1 commit intoopenshift:mainfrom
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@jldohmann: This pull request references OSDOCS-17114 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
jldohmann
force-pushed
the
OSDOCS-17114
branch
from
bd2d694 to
1367476
Compare
openshift-ci
Bot
added
size/M
|
@jldohmann: This pull request references OSDOCS-17114 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
|
🤖 Tue Mar 24 19:07:18 - Prow CI generated the docs preview: https://107224--ocpdocs-pr.netlify.app/microshift/latest/microshift_configuring/microshift-default-config-yaml.html |
|
@jldohmann: This pull request references OSDOCS-17114 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
openshift-merge-robot
added
the
needs-rebase
jldohmann
force-pushed
the
OSDOCS-17114
branch
2 times, most recently
from
6d6036a to
2cac19a
Compare
openshift-merge-robot
removed
the
needs-rebase
|
@jldohmann: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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-sigs/prow repository. I understand the commands that are listed here. |
| include::snippets/technology-preview.adoc[] | ||
|
|
||
| [role="_abstract"] | ||
| To properly plan your single-node edge deployment, review the comprehensive default settings in {product-title}. Understanding these built-in parameters, ranging from OVN-Kubernetes Container Network Interface (CNI) settings to API and storage configurations, helps you determine if you need to customize your overall configuration to match your existing infrastructure. |
There was a problem hiding this comment.
| To properly plan your single-node edge deployment, review the comprehensive default settings in {product-title}. Understanding these built-in parameters, ranging from OVN-Kubernetes Container Network Interface (CNI) settings to API and storage configurations, helps you determine if you need to customize your overall configuration to match your existing infrastructure. | |
| To properly plan your single-node edge deployment, review the comprehensive default settings in {microshift-short}. Understanding these built-in parameters, ranging from OVN-Kubernetes Container Network Interface (CNI) settings to API and storage configurations, helps you determine if you need to customize your overall configuration to match your existing infrastructure. |
the product title attribute is only used in the release notes and general intro
this short desc is actually conceptually incorrect; microshift does not need to match infrastructure as this is not the way it is deployed (really cannot seem to say this enough); this sounds like single-openshift, which it is not
| To properly plan your single-node edge deployment, review the comprehensive default settings in {product-title}. Understanding these built-in parameters, ranging from OVN-Kubernetes Container Network Interface (CNI) settings to API and storage configurations, helps you determine if you need to customize your overall configuration to match your existing infrastructure. | |
| To plan your edge deployment, you can review the comprehensive default settings in {microshift-short}. Understanding default parameters helps you determine how you need to customize your configuration to match your edge destination. |
the edge deployment is going to be a single device (ok, many times over) that runs on an image-based rhel system with microshift as the k app platform; config generally has to do with storage and security versus performance and that is based on both location and the device itself
| `storage.driver`:: Specifies the storage driver to use. Default null value deploys Logical Volume Managed Storage (LVMS). | ||
| `storage.optionalCsiComponents`:: Specifies the CSI components to deploy. Default null value deploys `snapshot-controller`. | ||
| -- No newline at end of file | ||
| `storage.driver`:: Specifies the default storage to use. The default null value deploys Logical Volume Managed Storage (LVMS). |
There was a problem hiding this comment.
| `storage.driver`:: Specifies the default storage to use. The default null value deploys Logical Volume Managed Storage (LVMS). | |
| `storage.driver`:: Specifies the storage driver to use. The default null value deploys Logical Volume Managed Storage (LVMS). |
other types of drivers were intended to be used here as well; i would leave this--i don't know what the support status is at this point; you can ask @copejon
|
|
||
| .{product-title} network topology | ||
| The following diagram shows an overview of the {product-title} network topology: | ||
|
|
There was a problem hiding this comment.
the title should still be included, not deleted (did we hit a DITA rule on that one?)
There was a problem hiding this comment.
yes, this kept flagging one of the AsciiDocDITA rules. if that shouldn't happen, the vale rule in the package will need to be updated to handle these cases
5 participants
Version(s): 4.16+
Issue: https://issues.redhat.com/browse/OSDOCS-17114
Link to docs preview:
Additional information: MS networking CQA pt.1