OCPBUGS-60303, NETOBSERV-2023: Implement a quickstart for netobserv operator #955
Conversation
|
Skipping CI for Draft Pull Request. |
openshift-ci
bot
added
the
do-not-merge/work-in-progress
| 2.2 If you are not using Loki, click Loki client settings and change **Enable** to **False**. The setting is True by default. | ||
|
|
||
| 2.3 If you are using Loki, set the following specifications: | ||
|
|
||
| i. **spec.loki.mode**: Set this to the **LokiStack** mode, which automatically sets URLs, TLS, cluster roles and a cluster role binding, as well as the authToken value. Alternatively, the Manual mode allows more control over configuration of these settings. | ||
|
|
||
| ii. **spec.loki.lokistack.name**: Set this to the name of your LokiStack resource. In this documentation, loki is used. |
There was a problem hiding this comment.
@stleerh you mentionned you would like to point out Loki Operator doc. How do you want to handle it here ?
Thank you @skrthomas ! Merged your suggestions 😉 |
| 1. In the OpenShift Container Platform web console, click **OperatorHub** from the [Operators]{{highlight qs-nav-operators}} → OperatorHub. | ||
| 2. Choose **Network Observability Operator** from the list of available Operators in the OperatorHub, and click **Install**. |
There was a problem hiding this comment.
Is it possible to provide a direct link to that?
There was a problem hiding this comment.
I don't think so as you usually need to search for it first 🤔
Also, it may vary depending of your catalogs
There was a problem hiding this comment.
But isn't it what lightspeed is doing?
It seems that this link would work: /operatorhub/ns/default?details-item=netobserv-operator-redhat-operators-openshift-marketplace&channel=stable (assuming using the main official catalog)
There was a problem hiding this comment.
Does it works if you remove the channel ?
Else I feel it's not worth. None of the existing quickstarts are doing such.
openshift-ci
bot
removed
the
do-not-merge/work-in-progress
Co-authored-by: Sara Thomas <sarthoma@redhat.com>
Co-authored-by: Sara Thomas <sarthoma@redhat.com>
Co-authored-by: Sara Thomas <sarthoma@redhat.com>
Co-authored-by: Sara Thomas <sarthoma@redhat.com>
Co-authored-by: Joel Takvorian <joel.takvorian@homeblocks.net>
jpinsonneau
force-pushed
the
netobserv_quickstart
branch
from
646d0f7 to
4706403
Compare
|
@jotak could you please review the PR if its good to go? |
openshift-ci-robot
added
the
jira/valid-reference
|
@jpinsonneau: This pull request references NETOBSERV-2023 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.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. |
1 similar comment
|
/retest |
|
@jpinsonneau: 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. |
|
[ART PR BUILD NOTIFIER] Distgit: openshift-enterprise-console-operator |
|
/cherry-pick release-4.18 |
|
@jpinsonneau: new pull request created: #997 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 kubernetes-sigs/prow repository. |
|
/cherry-pick release-4.17 |
|
@jpinsonneau: new pull request created: #998 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 kubernetes-sigs/prow repository. |
|
/cherry-pick release-4.16 |
|
/cherry-pick release-4.15 |
|
/cherry-pick release-4.14 |
|
/cherry-pick release-4.12 |
|
@jpinsonneau: new pull request created: #999 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 kubernetes-sigs/prow repository. |
|
@jpinsonneau: new pull request created: #1000 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 kubernetes-sigs/prow repository. |
|
@jpinsonneau: new pull request created: #1001 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 kubernetes-sigs/prow repository. |
|
@jpinsonneau: new pull request created: #1002 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 kubernetes-sigs/prow repository. |
jhadvig
changed the title
|
@jpinsonneau: Jira Issue OCPBUGS-60303 is in an unrecognized state (Closed) and will not be moved to the MODIFIED state. 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. |
8 participants
Initial quickstart for Network Observability Operator