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

cleanup: remove .spec.global field from the KongPluginBinding resource #28

Merged
merged 4 commits into from
Aug 12, 2024

Conversation

mlavacca
Copy link
Member

@mlavacca mlavacca commented Aug 9, 2024

What this PR does / why we need it:

This PR removes the .spec.global field from the KongPluginBinding resource. KPB is a namespaced resource and having a field in its spec that affects all the resources of a cluster breaks the namespace isolation.

Which issue this PR fixes

Fixes #

Special notes for your reviewer:

PR Readiness Checklist:

Complete these before marking the PR as ready to review:

  • the CHANGELOG.md release notes have been updated to reflect significant changes

@mlavacca mlavacca requested a review from a team as a code owner August 9, 2024 10:34
@mlavacca mlavacca changed the title Mlavacca/remove global cleanup: remove .spec.global field from the KongPluginBinding resource Aug 9, 2024
@mlavacca mlavacca force-pushed the mlavacca/remove-global branch from 55e2d27 to 54e6e77 Compare August 12, 2024 08:26
Copy link
Contributor

@czeslavo czeslavo left a comment

Choose a reason for hiding this comment

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

Hm, that makes sense. I guess that means that to model global plugins with bindings, we will need a separate KongPluginClusterBinding CRD?

Signed-off-by: Mattia Lavacca <[email protected]>
Signed-off-by: Mattia Lavacca <[email protected]>
Signed-off-by: Mattia Lavacca <[email protected]>
@mlavacca mlavacca force-pushed the mlavacca/remove-global branch from 54e6e77 to 6da4ebd Compare August 12, 2024 10:29
@mlavacca
Copy link
Member Author

Hm, that makes sense. I guess that means that to model global plugins with bindings, we will need a separate KongPluginClusterBinding CRD?

Yep, I already commented in the original issue about this possibility. I think that's the way to go 👍

@mlavacca mlavacca merged commit c0067c4 into main Aug 12, 2024
6 checks passed
@mlavacca mlavacca deleted the mlavacca/remove-global branch August 12, 2024 10:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants