cluster-logging-operator
cluster-logging-operator copied to clipboard
Update api_observability_v1.adoc
Description
Have fixed the content presentation int the Cloudwatch section. The table was broken due to the "||" characters. Inserted the backslash to prevent it.
/cc /assign
Links
None
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: faldanarh Once this PR has been reviewed and has the lgtm label, please assign alanconway for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
@faldanarh: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
| Test name | Commit | Details | Required | Rerun command |
|---|---|---|---|---|
| ci/prow/unit | 64689b612d971ddbcc133da6b9daaabacab801b2 | link | true | /test unit |
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.
@faldanarh we are more then happy to accept improvements to any bits of this code base. Note this document is autogenerated and any changes need to be sourced in the api go code. You must:
- edit the code
- run
make generate bundle docs/reference/operator/api_observability_v1.adoc
This should result in three files being changed
/hold
Have fixed the content presentation int the Cloudwatch section. The table was broken due to the "||" characters. Inserted the backslash to prevent it.
@jcantrill I have done what you requested and created a new PR #2851
Closing this in favour of #2851
/close
@alanconway: Closed this PR.
In response to this:
/close
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.