Skip to content
New issue

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

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

Already on GitHub? # to your account

ClusterSync: Warn on resource conflicts #2521

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

2uasimojo
Copy link
Member

@2uasimojo 2uasimojo commented Nov 15, 2024

Add a new ClusterSync.Status field, ResourceConflicts, and a corresponding printColumn visible when -o wide is used.

When a single resource (GVK + name [+ namespace if ns-scoped]) is mentioned more than once in the resources sections (not patches or secretMappings) of the [Selector]SyncSets matching a ClusterDeployment, we will add a human-readable message to this status field indicating the resource and the [Selector]SyncSets in which it is mentioned.

Example message:

"Resource {v1 Namespace openshift-logging } is mentioned by 2 [Selector]SyncSets: mygroup, osd-logging1"

HIVE-2634

Add a new ClusterSync.Status field, ResourceConflicts, and a
corresponding printColumn visible when `-o wide` is used.

When a single resource (GVK + name [+ namespace if ns-scoped]) is
mentioned more than once in the `resources` sections (not `patches` or
`secretMappings`) of the [Selector]SyncSets matching a
ClusterDeployment, we will add a human-readable message to this status
field indicating the resource and the [Selector]SyncSets in which it is
mentioned.

Example message:

```
"Resource {v1 Namespace openshift-logging } is mentioned by 2 [Selector]SyncSets: mygroup, osd-logging1"
```

HIVE-2634
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Nov 15, 2024
Copy link
Contributor

openshift-ci bot commented Nov 15, 2024

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

Copy link
Contributor

openshift-ci bot commented Nov 15, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 2uasimojo

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 15, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant