OBSDOCS-1628: Prepare the concept assembly in Monitoring Overview sec…

[eromanova97]

Version(s): none for CP, monitoring-docs-restructure only

Issue: https://issues.redhat.com/browse/OBSDOCS-1628

QE review:

• QE has approved this change.

$${\color{red}Additional \space information:}$$
The changes in the PR are not yet user-facing

This PR moves content from old to the new assemblies. The content in the original assembly is still there . The reason is to not lose any content while moving it around. There will be a separate issue that will make sure that all the content is transfered as needed.

Therefore, the main thing to check in this PR is to see if the structure in the linked chapters looks good and renders without issues.

I also included some small fixes for the other already transfered sections.


$${\color{red}Links \space to \space docs \space preview \space (with \space an \space explanation \space of \space what \space was \space changed:}$$

• Understanding the monitoring stack - key concepts

  • Added this whole new section based on existing concept modules (no new content, just moved the existing modules to this assembly)

• Maintenance and support for monitoring

  • Added the existing content from the configuring the mon stack section to its standalone assembly.

------------------------The assemblies above are the main changes---------------------

------------------------The following are minor inmprovements---------------------

• Creating cluster ID labels for metrics for core platform monitoring

• Creating cluster ID labels for metrics for monitoring of user-defined projects

  • Removed the introductory concept and moved it to the Key concepts section. Moved this procedural module up one level.

• Controling the placement and distribution of monitoring components

• Controling the placement and distribution of monitoring components-uwm

  • Changed the heading and introductory sentences to include both node selector and toleration procedures (the introduction wrongly included only the introduction to node selectors)

• Choosing a metrics collection profile

• Configuring pod topology spread constraints for core platform monitoring

  • Removed the introductory concept and moved it to the Key concepts section. Moved this procedural module up one level.

• Controlling the impact of unbound metrics attributes in user-defined projects

  • Removed the conceptual content and moved that content to the Key concepts section.

• Modifying the retention time for Thanos Ruler metrics data

  • Moved up one level (was incorrectly nested under the previous module)

[openshift-ci-robot]

@eromanova97: This pull request references OBSDOCS-1628 which is a valid jira issue.

In response to this:

…tion

Version(s): none for CP, monitoring-docs-restructure only

Issue: https://issues.redhat.com/browse/OBSDOCS-1628

Link to docs preview:

QE review:

• QE has approved this change.

Additional information:

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-ci-robot]

@eromanova97: This pull request references OBSDOCS-1628 which is a valid jira issue.

In response to this:

Version(s): none for CP, monitoring-docs-restructure only

Issue: https://issues.redhat.com/browse/OBSDOCS-1628

Link to docs preview:

QE review:

• QE has approved this change.

Additional information:

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.

[ocpdocs-previewbot]

🤖 Fri Jan 24 14:46:27 - Prow CI generated the docs preview:
https://87259--ocpdocs-pr.netlify.app
Complete list of updated preview URLs: artifacts/updated_preview_urls.txt

[openshift-ci-robot]

@eromanova97: This pull request references OBSDOCS-1628 which is a valid jira issue.

In response to this:

Version(s): none for CP, monitoring-docs-restructure only

Issue: https://issues.redhat.com/browse/OBSDOCS-1628

Links to docs preview:

• Understanding the monitoring stack - key concepts
• Creating cluster ID labels for metrics for core platform monitoring
• Controling the placement and distribution of monitoring components
• Controling the placement and distribution of monitoring components-uwm
• Choosing a metrics collection profile
• Configuring pod topology spread constraints for core platform monitoring
• Creating cluster ID labels for metrics for core platform monitoring
• Creating cluster ID labels for metrics for monitoring of user-defined projects
• Controlling the impact of unbound metrics attributes in user-defined projects
• Modifying the retention time for Thanos Ruler metrics data
• Maintenance and support for monitoring

QE review:

• QE has approved this change.

Additional information:

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-ci-robot]

@eromanova97: This pull request references OBSDOCS-1628 which is a valid jira issue.

In response to this:

Version(s): none for CP, monitoring-docs-restructure only

Issue: https://issues.redhat.com/browse/OBSDOCS-1628

Links to docs preview (with an explanation of what was changed:

• Understanding the monitoring stack - key concepts
  ** Added this whole new section based on existing concept modules (no new content, just moved the existing modules to this assembly)

• Creating cluster ID labels for metrics for core platform monitoring

• Creating cluster ID labels for metrics for monitoring of user-defined projects
  ** Removed the introductory concept to the Key concepts section. Moved this procedural module up one level.

• Controling the placement and distribution of monitoring components

• Controling the placement and distribution of monitoring components-uwm
  ** Changed the heading and introductory sentences to include both node selector and toleration procedures (the introduction wrongly included only the introduction to node selectors)

• Choosing a metrics collection profile

• Configuring pod topology spread constraints for core platform monitoring
  ** Removed the introductory concept to the Key concepts section. Moved this procedural module up one level.

• Controlling the impact of unbound metrics attributes in user-defined projects
  ** Removed the conceptual content and moved that content to the Key concepts section.

• Modifying the retention time for Thanos Ruler metrics data
  ** Moved up one level (was incorrectly nested under the previous module)

• Maintenance and support for monitoring
  ** Addad the existing content from the configuring the mon stack section to its standalone assembly.

QE review:

• QE has approved this change.

Additional information:

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-ci-robot]

@eromanova97: This pull request references OBSDOCS-1628 which is a valid jira issue.

In response to this:

Version(s): none for CP, monitoring-docs-restructure only

Issue: https://issues.redhat.com/browse/OBSDOCS-1628

Links to docs preview (with an explanation of what was changed:

• Understanding the monitoring stack - key concepts
  ** Added this whole new section based on existing concept modules (no new content, just moved the existing modules to this assembly)

• Creating cluster ID labels for metrics for core platform monitoring

• Creating cluster ID labels for metrics for monitoring of user-defined projects
  ** Removed the introductory concept to the Key concepts section. Moved this procedural module up one level.

• Controling the placement and distribution of monitoring components

• Controling the placement and distribution of monitoring components-uwm
  ** Changed the heading and introductory sentences to include both node selector and toleration procedures (the introduction wrongly included only the introduction to node selectors)

• Choosing a metrics collection profile

• Configuring pod topology spread constraints for core platform monitoring
  ** Removed the introductory concept to the Key concepts section. Moved this procedural module up one level.

• Controlling the impact of unbound metrics attributes in user-defined projects
  ** Removed the conceptual content and moved that content to the Key concepts section.

• Modifying the retention time for Thanos Ruler metrics data
  ** Moved up one level (was incorrectly nested under the previous module)

• Maintenance and support for monitoring
  ** Added the existing content from the configuring the mon stack section to its standalone assembly.

QE review:

• QE has approved this change.

Additional information:

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-ci-robot]

@eromanova97: This pull request references OBSDOCS-1628 which is a valid jira issue.

In response to this:

Version(s): none for CP, monitoring-docs-restructure only

Issue: https://issues.redhat.com/browse/OBSDOCS-1628

Links to docs preview (with an explanation of what was changed:

• Understanding the monitoring stack - key concepts

  • Added this whole new section based on existing concept modules (no new content, just moved the existing modules to this assembly)

• Creating cluster ID labels for metrics for core platform monitoring

• Creating cluster ID labels for metrics for monitoring of user-defined projects

  • Removed the introductory concept to the Key concepts section. Moved this procedural module up one level.

• Controling the placement and distribution of monitoring components

• Controling the placement and distribution of monitoring components-uwm

  • Changed the heading and introductory sentences to include both node selector and toleration procedures (the introduction wrongly included only the introduction to node selectors)

• Choosing a metrics collection profile

• Configuring pod topology spread constraints for core platform monitoring

  • Removed the introductory concept to the Key concepts section. Moved this procedural module up one level.

• Controlling the impact of unbound metrics attributes in user-defined projects

  • Removed the conceptual content and moved that content to the Key concepts section.

• Modifying the retention time for Thanos Ruler metrics data

  • Moved up one level (was incorrectly nested under the previous module)

• Maintenance and support for monitoring

  • Added the existing content from the configuring the mon stack section to its standalone assembly.

QE review:

• QE has approved this change.

Additional information:

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-ci-robot]

@eromanova97: This pull request references OBSDOCS-1628 which is a valid jira issue.

In response to this:

Version(s): none for CP, monitoring-docs-restructure only

Issue: https://issues.redhat.com/browse/OBSDOCS-1628

Links to docs preview (with an explanation of what was changed:

• Understanding the monitoring stack - key concepts

  • Added this whole new section based on existing concept modules (no new content, just moved the existing modules to this assembly)

• Creating cluster ID labels for metrics for core platform monitoring

• Creating cluster ID labels for metrics for monitoring of user-defined projects

  • Removed the introductory concept and moved it to the Key concepts section. Moved this procedural module up one level.

• Controling the placement and distribution of monitoring components

• Controling the placement and distribution of monitoring components-uwm

  • Changed the heading and introductory sentences to include both node selector and toleration procedures (the introduction wrongly included only the introduction to node selectors)

• Choosing a metrics collection profile

• Configuring pod topology spread constraints for core platform monitoring

  • Removed the introductory concept and moved it to the Key concepts section. Moved this procedural module up one level.

• Controlling the impact of unbound metrics attributes in user-defined projects

  • Removed the conceptual content and moved that content to the Key concepts section.

• Modifying the retention time for Thanos Ruler metrics data

  • Moved up one level (was incorrectly nested under the previous module)

• Maintenance and support for monitoring

  • Added the existing content from the configuring the mon stack section to its standalone assembly.

QE review:

• QE has approved this change.

Additional information:

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-ci-robot]

@eromanova97: This pull request references OBSDOCS-1628 which is a valid jira issue.

In response to this:

Version(s): none for CP, monitoring-docs-restructure only

Issue: https://issues.redhat.com/browse/OBSDOCS-1628

Links to docs preview (with an explanation of what was changed:

• Understanding the monitoring stack - key concepts

  • Added this whole new section based on existing concept modules (no new content, just moved the existing modules to this assembly)

• Maintenance and support for monitoring

  • Added the existing content from the configuring the mon stack section to its standalone assembly.

------------------------The assemblies above are the main changes---------------------

------------------------The following are minor inmprovements---------------------

• Creating cluster ID labels for metrics for core platform monitoring

• Creating cluster ID labels for metrics for monitoring of user-defined projects

  • Removed the introductory concept and moved it to the Key concepts section. Moved this procedural module up one level.

• Controling the placement and distribution of monitoring components

• Controling the placement and distribution of monitoring components-uwm

  • Changed the heading and introductory sentences to include both node selector and toleration procedures (the introduction wrongly included only the introduction to node selectors)

• Choosing a metrics collection profile

• Configuring pod topology spread constraints for core platform monitoring

  • Removed the introductory concept and moved it to the Key concepts section. Moved this procedural module up one level.

• Controlling the impact of unbound metrics attributes in user-defined projects

  • Removed the conceptual content and moved that content to the Key concepts section.

• Modifying the retention time for Thanos Ruler metrics data

  • Moved up one level (was incorrectly nested under the previous module)

QE review:

• QE has approved this change.

Additional information:

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-ci-robot]

@eromanova97: This pull request references OBSDOCS-1628 which is a valid jira issue.

In response to this:

Version(s): none for CP, monitoring-docs-restructure only

Issue: https://issues.redhat.com/browse/OBSDOCS-1628

Links to docs preview (with an explanation of what was changed:

• Understanding the monitoring stack - key concepts

  • Added this whole new section based on existing concept modules (no new content, just moved the existing modules to this assembly)

• Maintenance and support for monitoring

  • Added the existing content from the configuring the mon stack section to its standalone assembly.

------------------------The assemblies above are the main changes---------------------

------------------------The following are minor inmprovements---------------------

• Creating cluster ID labels for metrics for core platform monitoring

• Creating cluster ID labels for metrics for monitoring of user-defined projects

  • Removed the introductory concept and moved it to the Key concepts section. Moved this procedural module up one level.

• Controling the placement and distribution of monitoring components

• Controling the placement and distribution of monitoring components-uwm

  • Changed the heading and introductory sentences to include both node selector and toleration procedures (the introduction wrongly included only the introduction to node selectors)

• Choosing a metrics collection profile

• Configuring pod topology spread constraints for core platform monitoring

  • Removed the introductory concept and moved it to the Key concepts section. Moved this procedural module up one level.

• Controlling the impact of unbound metrics attributes in user-defined projects

  • Removed the conceptual content and moved that content to the Key concepts section.

• Modifying the retention time for Thanos Ruler metrics data

  • Moved up one level (was incorrectly nested under the previous module)

QE review:

• QE has approved this change.

Additional information:

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-ci-robot]

@eromanova97: This pull request references OBSDOCS-1628 which is a valid jira issue.

In response to this:

Version(s): none for CP, monitoring-docs-restructure only

Issue: https://issues.redhat.com/browse/OBSDOCS-1628

Additional information:
The changes in the PR are not yet user-facing

This PR moves content from old to the new assemblies. The content in the original assembly is still there . The reason is to not lose any content while moving it around. There will be a separate issue that will make sure that all the content is transfered as needed.

Therefore, the main thing to check in this PR is to see if the structure in the linked chapters looks good and renders without issues.

I also included some small fixes for the other already transfered sections.


Links to docs preview (with an explanation of what was changed:

• Understanding the monitoring stack - key concepts

  • Added this whole new section based on existing concept modules (no new content, just moved the existing modules to this assembly)

• Maintenance and support for monitoring

  • Added the existing content from the configuring the mon stack section to its standalone assembly.

------------------------The assemblies above are the main changes---------------------

------------------------The following are minor inmprovements---------------------

• Creating cluster ID labels for metrics for core platform monitoring

• Creating cluster ID labels for metrics for monitoring of user-defined projects

  • Removed the introductory concept and moved it to the Key concepts section. Moved this procedural module up one level.

• Controling the placement and distribution of monitoring components

• Controling the placement and distribution of monitoring components-uwm

  • Changed the heading and introductory sentences to include both node selector and toleration procedures (the introduction wrongly included only the introduction to node selectors)

• Choosing a metrics collection profile

• Configuring pod topology spread constraints for core platform monitoring

  • Removed the introductory concept and moved it to the Key concepts section. Moved this procedural module up one level.

• Controlling the impact of unbound metrics attributes in user-defined projects

  • Removed the conceptual content and moved that content to the Key concepts section.

• Modifying the retention time for Thanos Ruler metrics data

  • Moved up one level (was incorrectly nested under the previous module)

QE review:

• QE has approved this change.

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-ci-robot]

@eromanova97: This pull request references OBSDOCS-1628 which is a valid jira issue.

In response to this:

Version(s): none for CP, monitoring-docs-restructure only

Issue: https://issues.redhat.com/browse/OBSDOCS-1628

$${\color{red}Additional \space information:}$$
The changes in the PR are not yet user-facing

This PR moves content from old to the new assemblies. The content in the original assembly is still there . The reason is to not lose any content while moving it around. There will be a separate issue that will make sure that all the content is transfered as needed.

Therefore, the main thing to check in this PR is to see if the structure in the linked chapters looks good and renders without issues.

I also included some small fixes for the other already transfered sections.


Links to docs preview (with an explanation of what was changed:

• Understanding the monitoring stack - key concepts

  • Added this whole new section based on existing concept modules (no new content, just moved the existing modules to this assembly)

• Maintenance and support for monitoring

  • Added the existing content from the configuring the mon stack section to its standalone assembly.

------------------------The assemblies above are the main changes---------------------

------------------------The following are minor inmprovements---------------------

• Creating cluster ID labels for metrics for core platform monitoring

• Creating cluster ID labels for metrics for monitoring of user-defined projects

  • Removed the introductory concept and moved it to the Key concepts section. Moved this procedural module up one level.

• Controling the placement and distribution of monitoring components

• Controling the placement and distribution of monitoring components-uwm

  • Changed the heading and introductory sentences to include both node selector and toleration procedures (the introduction wrongly included only the introduction to node selectors)

• Choosing a metrics collection profile

• Configuring pod topology spread constraints for core platform monitoring

  • Removed the introductory concept and moved it to the Key concepts section. Moved this procedural module up one level.

• Controlling the impact of unbound metrics attributes in user-defined projects

  • Removed the conceptual content and moved that content to the Key concepts section.

• Modifying the retention time for Thanos Ruler metrics data

  • Moved up one level (was incorrectly nested under the previous module)

QE review:

• QE has approved this change.

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-ci-robot]

@eromanova97: This pull request references OBSDOCS-1628 which is a valid jira issue.

In response to this:

Version(s): none for CP, monitoring-docs-restructure only

Issue: https://issues.redhat.com/browse/OBSDOCS-1628

$${\color{red}Additional \space information:}$$
The changes in the PR are not yet user-facing

This PR moves content from old to the new assemblies. The content in the original assembly is still there . The reason is to not lose any content while moving it around. There will be a separate issue that will make sure that all the content is transfered as needed.

Therefore, the main thing to check in this PR is to see if the structure in the linked chapters looks good and renders without issues.

I also included some small fixes for the other already transfered sections.


$${\color{red}Links \space to \space docs \space preview \space (with \space an \space explanation \space of \space what \space was \space changed:}$$

• Understanding the monitoring stack - key concepts

  • Added this whole new section based on existing concept modules (no new content, just moved the existing modules to this assembly)

• Maintenance and support for monitoring

  • Added the existing content from the configuring the mon stack section to its standalone assembly.

------------------------The assemblies above are the main changes---------------------

------------------------The following are minor inmprovements---------------------

• Creating cluster ID labels for metrics for core platform monitoring

• Creating cluster ID labels for metrics for monitoring of user-defined projects

  • Removed the introductory concept and moved it to the Key concepts section. Moved this procedural module up one level.

• Controling the placement and distribution of monitoring components

• Controling the placement and distribution of monitoring components-uwm

  • Changed the heading and introductory sentences to include both node selector and toleration procedures (the introduction wrongly included only the introduction to node selectors)

• Choosing a metrics collection profile

• Configuring pod topology spread constraints for core platform monitoring

  • Removed the introductory concept and moved it to the Key concepts section. Moved this procedural module up one level.

• Controlling the impact of unbound metrics attributes in user-defined projects

  • Removed the conceptual content and moved that content to the Key concepts section.

• Modifying the retention time for Thanos Ruler metrics data

  • Moved up one level (was incorrectly nested under the previous module)

QE review:

• QE has approved this change.

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.

[juzhao]

/lgtm

[openshift-ci-robot]

@eromanova97: This pull request references OBSDOCS-1628 which is a valid jira issue.

In response to this:

Version(s): none for CP, monitoring-docs-restructure only

Issue: https://issues.redhat.com/browse/OBSDOCS-1628

$${\color{red}Additional \space information:}$$
The changes in the PR are not yet user-facing

This PR moves content from old to the new assemblies. The content in the original assembly is still there . The reason is to not lose any content while moving it around. There will be a separate issue that will make sure that all the content is transfered as needed.

Therefore, the main thing to check in this PR is to see if the structure in the linked chapters looks good and renders without issues.

I also included some small fixes for the other already transfered sections.


$${\color{red}Links \space to \space docs \space preview \space (with \space an \space explanation \space of \space what \space was \space changed:}$$

• Understanding the monitoring stack - key concepts

  • Added this whole new section based on existing concept modules (no new content, just moved the existing modules to this assembly)

• Maintenance and support for monitoring

  • Added the existing content from the configuring the mon stack section to its standalone assembly.

------------------------The assemblies above are the main changes---------------------

------------------------The following are minor inmprovements---------------------

• Creating cluster ID labels for metrics for core platform monitoring

• Creating cluster ID labels for metrics for monitoring of user-defined projects

  • Removed the introductory concept and moved it to the Key concepts section. Moved this procedural module up one level.

• Controling the placement and distribution of monitoring components

• Controling the placement and distribution of monitoring components-uwm

  • Changed the heading and introductory sentences to include both node selector and toleration procedures (the introduction wrongly included only the introduction to node selectors)

• Choosing a metrics collection profile

• Configuring pod topology spread constraints for core platform monitoring

  • Removed the introductory concept and moved it to the Key concepts section. Moved this procedural module up one level.

• Controlling the impact of unbound metrics attributes in user-defined projects

  • Removed the conceptual content and moved that content to the Key concepts section.

• Modifying the retention time for Thanos Ruler metrics data

  • Moved up one level (was incorrectly nested under the previous module)

QE review:

• QE has approved this change.

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-ci-robot]

@eromanova97: This pull request references OBSDOCS-1628 which is a valid jira issue.

In response to this:

Version(s): none for CP, monitoring-docs-restructure only

Issue: https://issues.redhat.com/browse/OBSDOCS-1628

QE review:

• QE has approved this change.

$${\color{red}Additional \space information:}$$
The changes in the PR are not yet user-facing

This PR moves content from old to the new assemblies. The content in the original assembly is still there . The reason is to not lose any content while moving it around. There will be a separate issue that will make sure that all the content is transfered as needed.

Therefore, the main thing to check in this PR is to see if the structure in the linked chapters looks good and renders without issues.

I also included some small fixes for the other already transfered sections.


$${\color{red}Links \space to \space docs \space preview \space (with \space an \space explanation \space of \space what \space was \space changed:}$$

• Understanding the monitoring stack - key concepts

  • Added this whole new section based on existing concept modules (no new content, just moved the existing modules to this assembly)

• Maintenance and support for monitoring

  • Added the existing content from the configuring the mon stack section to its standalone assembly.

------------------------The assemblies above are the main changes---------------------

------------------------The following are minor inmprovements---------------------

• Creating cluster ID labels for metrics for core platform monitoring

• Creating cluster ID labels for metrics for monitoring of user-defined projects

  • Removed the introductory concept and moved it to the Key concepts section. Moved this procedural module up one level.

• Controling the placement and distribution of monitoring components

• Controling the placement and distribution of monitoring components-uwm

  • Changed the heading and introductory sentences to include both node selector and toleration procedures (the introduction wrongly included only the introduction to node selectors)

• Choosing a metrics collection profile

• Configuring pod topology spread constraints for core platform monitoring

  • Removed the introductory concept and moved it to the Key concepts section. Moved this procedural module up one level.

• Controlling the impact of unbound metrics attributes in user-defined projects

  • Removed the conceptual content and moved that content to the Key concepts section.

• Modifying the retention time for Thanos Ruler metrics data

  • Moved up one level (was incorrectly nested under the previous module)

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.

[eromanova97]

/label peer-review-needed

[openshift-ci]

New changes are detected. LGTM label has been removed.

[openshift-ci]

@eromanova97: all tests passed!

Full PR test history. Your PR dashboard.

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-sigs/prow repository. I understand the commands that are listed here.

[eromanova97]

/label merge-review-needed