Add CRD scaffolding for cluster observability / signal manager #748
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pavolloffay
requested review from
jan--f and
JoaoBraveCoding
and removed request for
a team
pavolloffay
force-pushed
the
cluster-obser-1
branch
2 times, most recently
from
d4c3e1f to
87efb20
Compare
Signed-off-by: Pavol Loffay <p.loffay@gmail.com>
pavolloffay
force-pushed
the
cluster-obser-1
branch
from
87efb20 to
3b5f246
Compare
alanconway
approved these changes
May 22, 2025
deploy/crds/common/observability.openshift.io_clusterobservabilities.yaml
Show resolved
Hide resolved
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alanconway, pavolloffay The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-merge-bot bot
pushed a commit
that referenced
this pull request
May 28, 2025
* fix: further fix github action olm publish failure (#742) * fix: allow to create a logging plugin without a loki stack (#743) Signed-off-by: Gabriel Bernal <gbernal@redhat.com> * build: check for go installation before setting up a new environment (#745) Signed-off-by: Gabriel Bernal <gbernal@redhat.com> * feat: enable deployment of common accelerator perses dashboard (#744) Common accelerator perses dashboard contains metrics that are common for different accelerators' vendors. The dashboard will be deployed along with UI plugin * fix: Update main.go korrel8r tag to release-coo-1.2 (#746) * feat: add monitoring-plugin stream 0.4 and 0.5 (#747) Signed-off-by: Jenny Zhu <jenny.a.zhu@gmail.com> * feat: add CRD scaffolding for cluster observability / signal manager (#748) Signed-off-by: Pavol Loffay <p.loffay@gmail.com> * chore: update troubleshooting plugin image tag (#749) Signed-off-by: Jenny Zhu <jenny.a.zhu@gmail.com> * fix: add default value to logs schema (#751) * fix: check lokistack value on lokistack discovery (#753) Signed-off-by: Gabriel Bernal <gbernal@redhat.com> * chore: update troubleshooting plugin to new image (#755) * chore: update logging image to v6.1.1 (#756) * chore(release): 1.2.0 (new cut) --------- Signed-off-by: Gabriel Bernal <gbernal@redhat.com> Signed-off-by: Jenny Zhu <jenny.a.zhu@gmail.com> Signed-off-by: Pavol Loffay <p.loffay@gmail.com> Co-authored-by: lihongyan1 <hongyli@redhat.com> Co-authored-by: Gabriel Bernal <gbernal@redhat.com> Co-authored-by: Yevgeny Shnaidman <60741237+yevgeny-shnaidman@users.noreply.github.com> Co-authored-by: Alan Conway <aconway@redhat.com> Co-authored-by: Jenny Zhu <jenny.a.zhu@gmail.com> Co-authored-by: Pavol Loffay <p.loffay@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Replaces #724
This PR just adds scaffolding CRD (without controller) for the ClusterObservability CR.
I would like to rename the original name
SignalManagertoClusterObservability. I think it is less ambiguous and aligns with MCO API that we have agreed on in the pastMultiClusterObservability.The long-term goal for the COO is to become a swiss-army knife for deploying observability stack on a single cluster and be used by MCO. Aligning the APIs will provide straight forward user experience any going from single cluster to multi-cluster deployments.