Skip to content

OBSDOCS-1253: Improve OTEL installation procedure on console and CLI by unifying namespace #87756

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
max-cx wants to merge 1 commit into from
Closed

OBSDOCS-1253: Improve OTEL installation procedure on console and CLI by unifying namespace #87756

max-cx wants to merge 1 commit into from

Conversation

@max-cx
Copy link
Contributor

@max-cx max-cx commented Jan 29, 2025 •
edited
Loading

Signed-off-by: Pavol Loffay [email protected]

Version(s): 4.12, 4.13, 4.14, 4.15, 4.16, 4.17, 4.18

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

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 29, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 29, 2025 •
edited by openshift-ci bot
Loading

@max-cx: This pull request references OBSDOCS-1253 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.19.0" version, but no target version was set.

Details

In response to this:

Signed-off-by: Pavol Loffay [email protected]

Version(s):

Issue:

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 openshift-ci bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jan 29, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 29, 2025 •
edited by openshift-ci bot
Loading

@max-cx: This pull request references OBSDOCS-1253 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.19.0" version, but no target version was set.

Details

In response to this:

Signed-off-by: Pavol Loffay [email protected]

Version(s): 4.12, 4.13, 4.14, 4.15, 4.16, 4.17, 4.18

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

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
Copy link

ocpdocs-previewbot commented Jan 29, 2025

🤖 Wed Jan 29 11:43:19 - Prow CI generated the docs preview:

https://87756--ocpdocs-pr.netlify.app/
https://87756--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/distr_tracing/distr_tracing_tempo/distr-tracing-tempo-installing.html
https://87756--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/otel/otel-installing.html

ocpdocs-vale-bot
ocpdocs-vale-bot reviewed Jan 29, 2025
View reviewed changes
snippets/distr-tracing-tempo-tempomonolithic-custom-resource.adoc
<9> Optional.
<1> Do not create the instance in a namespace which starts with `openshift-` prefix.
<2> Type of storage for storing traces: in-memory storage, a persistent volume, or object storage. The value for a persistent volume is `pv`. The accepted values for object storage are `s3`, `gcs`, or `azure`, depending on the used object store type. The default value is `memory` for the `tmpfs` in-memory storage, which is only appropriate for development, testing, demonstrations, and proof-of-concept environments because the data does not persist when the pod is shut down.
<3> Memory size: For in-memory storage, this means the size of the `tmpfs` volume, where the default is `2Gi`. For a persistent volume, this means the size of the persistent volume claim, where the default is `10Gi`. For object storage, this means the size of the persistent volume claim for the Tempo WAL, where the default is `10Gi`.
Copy link
Collaborator

@ocpdocs-vale-bot ocpdocs-vale-bot Jan 29, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 [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.

ocpdocs-vale-bot
ocpdocs-vale-bot reviewed Jan 29, 2025
View reviewed changes
snippets/distr-tracing-tempo-tempostack-custom-resource.adoc
<6> Optional: Name of a `ConfigMap` object that contains a CA certificate.
<7> Optional.
<1> Do not create the instance in a namespace which starts with `openshift-` prefix.
<2> Size of the persistent volume claim for the Tempo WAL. The default is `10Gi`.
Copy link
Collaborator

@ocpdocs-vale-bot ocpdocs-vale-bot Jan 29, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 [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.

@openshift-ci
Copy link

openshift-ci bot commented Jan 29, 2025

@max-cx: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.

@openshift-bot
Copy link

openshift-bot commented Apr 30, 2025

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 30, 2025
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 30, 2025
@openshift-merge-robot
Copy link

openshift-merge-robot commented Apr 30, 2025

PR needs rebase.

Details

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.

@openshift-bot
Copy link

openshift-bot commented May 2, 2025

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-bot
Copy link

openshift-bot commented Jun 1, 2025

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jun 1, 2025
@max-cx max-cx closed this Jul 1, 2025
@max-cx max-cx deleted the OBSDOCS-1253 branch July 1, 2025 11:39
@max-cx
Copy link
Contributor Author

max-cx commented Jul 2, 2025

The new PR that replaces this one is #95509.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

1 more reviewer

@ocpdocs-vale-bot ocpdocs-vale-bot ocpdocs-vale-bot left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

7 participants

@max-cx @openshift-ci-robot @ocpdocs-previewbot @openshift-bot @openshift-merge-robot @ocpdocs-vale-bot @pavolloffay