OBSDOCS-1147: Bugfix - update storage secret table #79341
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@max-cx: This pull request references OBSDOCS-1147 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 task to target the "4.17.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
openshift-ci
bot
added
the
size/M
|
🤖 Mon Jan 06 11:35:32 - Prow CI generated the docs preview: |
|
@max-cx: This pull request references OBSDOCS-1147 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 task to target the "4.17.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
|
@max-cx: This pull request references OBSDOCS-1147 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 task to target the "4.17.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
max-cx
force-pushed
the
OBSDOCS-1147
branch
2 times, most recently
from
e96b0d4 to
ba914ae
Compare
|
/label peer-review-needed |
openshift-ci
bot
added
the
peer-review-needed
stevsmit
added
peer-review-in-progress
openshift-merge-robot
added
the
needs-rebase
|
@max-cx: This pull request references OBSDOCS-1147 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 task to target the "4.18.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
openshift-merge-robot
removed
the
needs-rebase
openshift-ci
bot
added
size/L
@stevsmit, I'm assuming you completed your peer review, for which I'm grateful, I'm doing housekeeping on the labels on this PR: /remove-label peer-review-in-progress |
openshift-ci
bot
added
the
peer-review-done
openshift-ci
bot
removed
the
peer-review-in-progress
|
/label merge-review-needed |
openshift-ci
bot
added
the
merge-review-needed
mburke5678
added
the
merge-review-in-progress
|
@max-cx I'm not seeing the |
max-cx
force-pushed
the
OBSDOCS-1147
branch
2 times, most recently
from
616b114 to
2b866e2
Compare
|
/remove-label merge-review-in-progress |
openshift-ci
bot
removed
the
merge-review-in-progress
|
/remove-label merge-review-needed |
openshift-ci
bot
removed
the
merge-review-needed
|
The This is because your PR targets the If the update in your PR does NOT apply to version 4.18 onward, please re-target this PR to go directly into the appropriate version branch or branches (enterprise-4.x) instead of main. |
|
@max-cx: This pull request references OBSDOCS-1147 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 bug to target the "4.19.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
|
/retest |
Signed-off-by: Andreas Gerstmayr <agerstmayr@redhat.com>
| @@ -59,3 +59,122 @@ managementState: managed # <21> | |||
| <19> Configures operands to handle telemetry data. | |||
| <20> Configures search capabilities. | |||
| <21> Defines whether or not this CR is managed by the Operator. The default value is `managed`. | |||
|
|
|||
| .Tempo parameters | |||
There was a problem hiding this comment.
🤖 [error] OpenShiftAsciiDoc.SuggestAttribute: Use the AsciiDoc attribute '{TempoName}' or '{TempoShortName}' rather than the plain text product term 'Tempo', unless your use case is an exception.
|
|
||
| |`spec:` | ||
| |Specification for the object to be created. | ||
| |Contains all of the configuration parameters for your TempoStack instance. When a common definition for all Tempo components is required, it is defined under the `spec` node. When the definition relates to an individual component, it is placed under the `spec/template/<component>` node. |
There was a problem hiding this comment.
🤖 [error] OpenShiftAsciiDoc.SuggestAttribute: Use the AsciiDoc attribute '{TempoName}' or '{TempoShortName}' rather than the plain text product term 'Tempo', unless your use case is an exception.
| | | ||
|
|
||
| |`template.querier:` | ||
| |Configuration options for the Tempo `querier`. |
There was a problem hiding this comment.
🤖 [error] OpenShiftAsciiDoc.SuggestAttribute: Use the AsciiDoc attribute '{TempoName}' or '{TempoShortName}' rather than the plain text product term 'Tempo', unless your use case is an exception.
|
@max-cx: 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. |
Signed-off-by: Andreas Gerstmayr agerstmayr@redhat.com
Version(s):
4.12, 4.13, 4.14, 4.15, 4.16, 4.17, 4.18
Issue:
https://issues.redhat.com/browse/OBSDOCS-1147
Link to docs preview:
Two sections updated:
QE review:
Additional information: