-
Notifications
You must be signed in to change notification settings - Fork 2
feat(KonnectGatewayControlPlane)!: add v1alpha2 version of KonnectGatewayControlPlane #502
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(KonnectGatewayControlPlane)!: add v1alpha2 version of KonnectGatewayControlPlane #502
Conversation
These test failures for === Failed
=== FAIL: test/crdsvalidation/konnect.konghq.com TestKonnectGatewayControlPlane/updates_not_allowed_for_status_conditions/konnect.authRef_change_is_allowed_when_cp_is_not_Programmed=True_nor_APIAuthValid=True (1.10s)
testcase.go:165:
Error Trace: /home/aldo/repos/kubernetes-configuration/test/crdsvalidation/common/testcase.go:178
/home/aldo/sdk/go1.24.4/src/runtime/asm_amd64.s:1700
Error: Received unexpected error:
KonnectGatewayControlPlane.konnect.konghq.com "test-jjtm2" is invalid: spec: Invalid value: "object": Name must be set for type Origin
testcase.go:165:
Error Trace: /home/aldo/repos/kubernetes-configuration/test/crdsvalidation/common/testcase.go:165
Error: Condition never satisfied
Test: TestKonnectGatewayControlPlane/updates_not_allowed_for_status_conditions/konnect.authRef_change_is_allowed_when_cp_is_not_Programmed=True_nor_APIAuthValid=True
=== FAIL: test/crdsvalidation/konnect.konghq.com TestKonnectGatewayControlPlane/updates_not_allowed_for_status_conditions (0.01s)
=== FAIL: test/crdsvalidation/konnect.konghq.com TestKonnectGatewayControlPlane/restriction_on_cluster_types/cluster_type_is_immutable_when_having_it_set_and_then_trying_to_unset_it (1.09s)
testcase.go:165:
Error Trace: /home/aldo/repos/kubernetes-configuration/test/crdsvalidation/common/testcase.go:175
/home/aldo/sdk/go1.24.4/src/runtime/asm_amd64.s:1700
Error: "KonnectGatewayControlPlane.konnect.konghq.com \"test-9rqb8\" is invalid: [<nil>: Invalid value: \"object\": no such key: status evaluating rule: spec.konnect.authRef is immutable when an entity is already Programmed, <nil>: Invalid value: \"object\": no such key: status evaluating rule: spec.konnect.authRef is immutable when an entity refers to a Valid API Auth Configuration]" does not contain "spec.cluster_type is immutable"
testcase.go:165:
Error Trace: /home/aldo/repos/kubernetes-configuration/test/crdsvalidation/common/testcase.go:165
Error: Condition never satisfied
Test: TestKonnectGatewayControlPlane/restriction_on_cluster_types/cluster_type_is_immutable_when_having_it_set_and_then_trying_to_unset_it
=== FAIL: test/crdsvalidation/konnect.konghq.com TestKonnectGatewayControlPlane/restriction_on_cluster_types (0.01s)
=== FAIL: test/crdsvalidation/konnect.konghq.com TestKonnectGatewayControlPlane (2.49s) |
33d0676
to
c004108
Compare
Skipping failing test in: c004108 |
test/crdsvalidation/konnect.konghq.com/konnectgatewaycontrolplane_test.go
Outdated
Show resolved
Hide resolved
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.
Looks good.
2 points I think we need to cover:
- let's update the sample manifests in this repo with a note stating that this (
v1alpha
) API is deprecated and it shouldn't be used - let's make sure that we update the sample manifests in KGO when we change the controller logic to account for the new version
I'm already working on updating the controller logic and use the new API version. I would block this PR until I have the changes in place in the controller logic. WDYT? |
Sounds good. This is a broader problem that I think we should tackle (get an agreed approach on), namely:
|
7a25cce
to
9ffddfb
Compare
9ffddfb
to
c395eca
Compare
4e1b5dc
to
48dbfee
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.
🚢
996da7f
to
1868c10
Compare
…ewayControlPlane `KonnectGatewayControlPlane` `v1alpha2` has been introduced. The `CreateControlPlaneRequest` fields (`name`, `description`, `clusterType`, `authType`, `cloudGateway`, `proxyUrls`, `labels`) have been moved from the top level of `spec` into a new structured field: `spec.createControlPlaneRequest`. **Action required:** - Update any manifests or code that reference these fields to use the new nested structure, e.g.: ```yaml spec: createControlPlaneRequest: name: my-control-plane clusterType: CLUSTER_TYPE_CONTROL_PLANE # ...other fields... ``` - The old flat field layout is no longer supported in `v1alpha2`. Signed-off-by: Aldo Lacuku <[email protected]>
1868c10
to
4dba134
Compare
test/crdsvalidation/konnect.konghq.com/konnectgatewaycontrolplane_test.go
Outdated
Show resolved
Hide resolved
Signed-off-by: Aldo Lacuku <[email protected]>
Signed-off-by: Aldo Lacuku <[email protected]>
What this PR does / why we need it:
KonnectGatewayControlPlane
v1alpha2
has been introduced.The
CreateControlPlaneRequest
fields (name
,description
,clusterType
,authType
,cloudGateway
,proxyUrls
,labels
) have been moved from the top level ofspec
into a new structured field:spec.createControlPlaneRequest
.Action required:
v1alpha2
.Which issue this PR fixes
Fixes:
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