-
Notifications
You must be signed in to change notification settings - Fork 28
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
Remove binding name #567
Remove binding name #567
Conversation
🙏 looking forward to not getting my logs spammed with
|
// +kubebuilder:validation:Required | ||
// +kubebuilder:validation:Pattern=`^k8s[/][a-zA-Z0-9-]{1,63}$` | ||
Name string `json:"name,omitempty"` | ||
|
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.
I wonder if we shouldn't leave this field in here but mark it as deprecated and change the validation to optional. The only thing I'm worried about if we remove it right now is if someone deploys this change and then rolls back to a previous version, what happens?
If there aren't a lot of users using bindings right now, I think its a lower risk change.
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.
Since we're breaking the API on the hosted side bindings won't work with this field anyway so I don't think it matters too much. Whenever we cut a release with these and a couple other upcoming changes that'll be the first release that works with bindings going forward
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #567 +/- ##
=======================================
Coverage ? 24.11%
=======================================
Files ? 88
Lines ? 12571
Branches ? 0
=======================================
Hits ? 3031
Misses ? 9350
Partials ? 190 ☔ View full report in Codecov by Sentry. |
What
The API for kubernetes bindings is being updated and no longer includes the
binding_name
field. Instead, kubernetes endpoints will be scoped to the account instead of a specific operator.How
Removes references to
binding_name
.Breaking Changes
The ngrok API for kubernetes bindings itself is breaking with this change so this is just following that.
As far as the operator itself:
KubernetesOperatorBinding
resource had itsName
field removed.values.yaml
has been updated to no longer includebindings.name