-
Notifications
You must be signed in to change notification settings - Fork 8k
update autoscaling version to v2beta2 #37872
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
Conversation
😊 Welcome @richardwxn! This is either your first contribution to the Istio istio repo, or it's been You can learn more about the Istio working groups, code of conduct, and contributing guidelines Thanks for contributing! Courtesy of your friendly welcome wagon. |
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.
Nice! what happens if someone has an overlay?
@richardwxn the failures look like they are real |
Yep I think we need to check in the istio/api changes first, otherwise it cannot recognize the updated schema, which is the reason why the tests are failing |
for helm it should just work since the original values. settings just mapped to a different k8s field. A bit trickier for k8s overlay cases, since some fields are just removed in the v2beta2/v2 schema, two ideas:
@howardjohn @ostromart lmk if that makes sense to you |
2 seems slightly better since (1) would still be a breaking change to IOP when a user upgrades their underlying K8s cluster. With 2 they just need to move before they upgrade to 1.25 which removes the old API |
2dc8119
to
d17fa1a
Compare
@howardjohn PTAL? |
manifests/charts/gateways/istio-egress/templates/autoscale.yaml
Outdated
Show resolved
Hide resolved
@@ -279,6 +279,9 @@ global: | |||
# Setting this port to a non-zero value enables STS server. | |||
servicePort: 0 | |||
|
|||
# whether to use autoscaling/v2 template for HPA settings | |||
autoscalingv2API: true |
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.
Is a user expected to configure this? It would be nice to auto-detect based on their Kubernetes version.
See manifests/charts/gateway/templates/deployment.yaml ip_unprivileged_port_start
for an example doing this
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.
it is for internal usage, i.e. we check the existence of deprecated fields usages from user's IOP and set this autoscalingv2API to false, then render the v2beta1 template instead
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 comment to the Helm description saying it's for internal usage? Users look to our Helm values as an API
@@ -279,6 +279,9 @@ global: | |||
# Setting this port to a non-zero value enables STS server. | |||
servicePort: 0 | |||
|
|||
# whether to use autoscaling/v2 template for HPA settings | |||
autoscalingv2API: true |
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 comment to the Helm description saying it's for internal usage? Users look to our Helm values as an API
operator/pkg/helmreconciler/prune.go
Outdated
@@ -193,6 +209,7 @@ func (h *HelmReconciler) GetPrunedResources(revision string, includeClusterResou | |||
labels[IstioComponentLabelStr] = componentName | |||
} | |||
selector := klabels.Set(labels).AsSelectorPreValidated() | |||
h.modifyPruneResourcesBasedOnK8SVersion() |
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.
+1, think we'd have to change this in a few places though?
In response to a cherrypick label: #37872 failed to apply on top of branch "release-1.14":
|
In response to a cherrypick label: new issue created for failed cherrypick: #38779 |
* update autoscaling version to v2beta2 * integrate with api repo changes * address comments * update helm gateway * address comments, fix boolean condition * modify pruning based on k8s version * fix comments
* update autoscaling version to v2beta2 * integrate with api repo changes * address comments * update helm gateway * address comments, fix boolean condition * modify pruning based on k8s version * fix comments
* operator: update golden files (#38714) Currently operator tests use a snapshot of the manifests for tests to avoid churn. Update these to meet current state of the world. All changes are autogenerated * update autoscaling version to v2beta2 (#37872) * update autoscaling version to v2beta2 * integrate with api repo changes * address comments * update helm gateway * address comments, fix boolean condition * modify pruning based on k8s version * fix comments * bump pdb version to policy/v1 (#38814) * add v1 pdb * release note * Remove common-protos (#38546) * Remove common-protos * Make gen Co-authored-by: John Howard <howardjohn@google.com> Co-authored-by: Xinnan Wen <iamwen@google.com> Co-authored-by: Zhonghu Xu <xuzhonghu@huawei.com>
need to wait for #istio/api#2273 to get in first
address #32005