Skip to content
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.

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

fix(groups): Add group namespace field #22

Merged
merged 1 commit into from
Jul 20, 2022
Merged

Conversation

akosveres
Copy link
Collaborator

We'll be able to tell the controller where the group resource is, it
could be in a separate namespace

This was based on an implementation from the cassandra operator seen
here: https://github.com/k8ssandra/cass-operator/blob/master/controllers/control/cassandratask_controller.go#L135-L138

This fixes #21.

@akosveres akosveres requested a review from ianaya89 July 20, 2022 12:14
We'll be able to tell the controller where the group resource is, it
could be in a separate namespace

This was based on an implementation from the cassandra operator seen
here: https://github.com/k8ssandra/cass-operator/blob/master/controllers/control/cassandratask_controller.go#L135-L138

This fixes #21.
Copy link

@ianaya89 ianaya89 left a comment

Choose a reason for hiding this comment

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

:shipit:

@akosveres akosveres merged commit 8a23b56 into main Jul 20, 2022
@akosveres akosveres deleted the BAU_group_cross_namespace branch July 20, 2022 14:44
@github-actions
Copy link

🎉 This PR is included in version 1.3.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

akosveres added a commit that referenced this pull request Jul 21, 2022
akosveres added a commit that referenced this pull request Jul 22, 2022
* Revert "fix(groups): Add group namespace field (#22)"

This reverts commit 8a23b56.

* fix(group): Make groups cluster scoped

We do not actually need to make the groups part of namespaces, they can
be cluster scoped, this way any ApiCheck in any namespace can read it.
It's a much better solution than specifying the namespace for each
group.

Tested locally, tests updated to not use a namespace for the group
resource.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Groups have to be in the same namespace as apiChecks
2 participants