redhat-cop / redhat-cop/group-sync-operator

Group SyncOperator: PrometheusOperatorRejectedResources

Open
#312 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
132
Forks
71
PR merge metrics
No merged PRs in 30d

Description

Looks like the same problem as https://access.redhat.com/solutions/6992399 or GitOps, Tempo Operator...

Fix:
oc label ns group-sync-operator openshift.io/cluster-monitoring=true

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the issue's namespace label command and inspect how the group-sync-operator namespace is created or configured. Confirm that applying openshift.io/cluster-monitoring=true resolves the PrometheusOperatorRejectedResources condition, then ensure the fix is represented in the project's deployment configuration.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes, prometheus
Domain
infrastructure, observability
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.