-
Notifications
You must be signed in to change notification settings - Fork 27
feat: add new registration-service config param for ui canary deployement #476
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
// - if the user has a number within the weight returned from the backend than user get's redirect to to new UI | ||
// - if the user has a number above the weight they keep using the current UI | ||
// | ||
// +optional |
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 detail, but you can add a validation of the input
// +optional | |
// +optional | |
// +kubebuilder:validation:Minimum=0 | |
// +kubebuilder:validation:Maximum=10 | |
// +kubebuilder:default=10 |
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
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.
Yeah, tbh I'm not sure what range we want to use.
I though about 1 - 100.
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've added the range (0 - 100 ) , but not the default, since that is defined in the registration service helper function.
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.
Yes, 1-100 is preferable IMO.
Co-authored-by: Feny Mehta <fbm3307@gmail.com>
|
Description
This PR adds new UICanaryDeploymentWeight in the toolchainconfig fields.
Jira: https://issues.redhat.com/browse/SANDBOX-1144
Checks
Did you run
make generate
target? yesDid
make generate
change anything in other projects (host-operator)? yesIn case of new CRD, did you the following? N/A
resources/setup/roles/host.yaml
in the sandbox-sre repositoryPROJECT
file: https://github.com/codeready-toolchain/host-operator/blob/master/PROJECTCSV
file: https://github.com/codeready-toolchain/host-operator/blob/master/config/manifests/bases/host-operator.clusterserviceversion.yamlIn case other projects are changed, please provides PR links.