-
Notifications
You must be signed in to change notification settings - Fork 14
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
feat: DataplaneKonnectExtension
CRD
#453
Conversation
89e8ac6
to
b09db39
Compare
dataplane_konnect_extension
CRDDataplaneKonnectExtension
CRD
fa3c962
to
56279cb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we add a sample manifest showing how this can be used?
I believe also that further comment in the PR description about this CRD would be beneficial to clue in potential reviewers.
8baa7e9
to
0cc163f
Compare
Yep, I added an example under |
ede4d5c
to
6e5a01f
Compare
6e5a01f
to
078d6d3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally LGTM, only some minor comments.
Signed-off-by: Mattia Lavacca <[email protected]>
Signed-off-by: Mattia Lavacca <[email protected]>
69cde85
to
cc2851d
Compare
cc2851d
to
78a8135
Compare
Signed-off-by: Mattia Lavacca <[email protected]>
78a8135
to
6f9c392
Compare
type DataPlaneKonnectExtensionSpec struct { | ||
// ControlPlaneRef is a reference to a ControlPlane this DataPlaneKonnectExtension is associated with. | ||
// +kubebuilder:validation:Required | ||
ControlPlaneRef configurationv1alpha1.ControlPlaneRef `json:"controlPlaneRef"` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a note based on a sync with @mlavacca: when we get to implement the konnectNamespacedRef we should make the CP ref immutable to prevent going from 1 type of CP ref to another (unless that gets implemented)
What this PR does / why we need it:
Which issue this PR fixes
Part of #203.
The original issue is about adding a new konnect-related set of fields directly in the
DataPlane
API. I think we should be very cautious about this approach because KGO is an open-source project that aims to be used by Kong and Konnect customers AND community users. Including SaaS-related fields directly in the API would negatively affect the API itself form the community point of view. Hence this new extension CRD that with an approach very similar to theControlPlaneMetricsExtension
is intended to be used by the DataPlane controller to customize the DataPlane deployment with konnect-related configuration.Special notes for your reviewer:
PR Readiness Checklist:
Complete these before marking the PR as
ready to review
:CHANGELOG.md
release notes have been updated to reflect significant changes