-
Notifications
You must be signed in to change notification settings - Fork 71
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
Changes the yaml for crd creation to remove deprecation warning on v1.22 #250
base: master
Are you sure you want to change the base?
Conversation
It fails to apply the CRDs due to OpenAPI Validation Errors as follows: Spinnaker Accounts:
for SpinnakerService CRD:
How did you get it to work on your local setup ? |
Apologies - I didn't realize i hadn't merged the feature branch with master in my repo. I actually changed my original way of fixing and issue with the depreciation of |
@seanrclayton Thanks for jumping in to help solve this issue! Not sure if this is due to an error on my end or the changes in this branch, but while I was able to get the operator to install with this branch, I can't actually get the operator to deploy anything. See the issue I opened here: #251 |
frequencySeconds: | ||
x-kubernetes-int-or-string: true | ||
description: Number of seconds between each validation |
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 found that you can still use the anyOf
syntax, but the order of the types matters.
In the old version it was
anyOf:
- type: string
- type: integer
but
anyOf:
- type: integer
- type: string
avoids the need to use x-kubernetes-int-or-string
. My interpretation of x-kubernetes-int-or-string
was a workaround, but that may be misguided.
frequencySeconds: | |
x-kubernetes-int-or-string: true | |
description: Number of seconds between each validation | |
frequencySeconds: | |
type: object | |
anyOf: | |
- type: integer | |
- type: string | |
description: Number of seconds between each validation |
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.
The above suggestion can be applied to all int-or-string
lines.
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.
Reading more of the documentation looks like x-kubernetes-int-or-string
is just shorthand, not necessarily a workaround. Carry on!
Hi guys, Many thanks for all your work. |
hmm
looks like the field is not appropriate https://github.com/armory/spinnaker-operator/blob/master/.mergify.yml#L10 |
https://blog.mergify.com/strict-mode-deprecation/ strict was deprecated. @seanrclayton could you, please, check the comment from @abannachZen |
@abannachZen How I can speed up the delivery of this PR? |
I can confirm this fixes the issue I was having as well (with k3d), would be a +1 to merging |
I ran into the same problem described in this issue I updated the yaml to comply with the changes described in the migration document here And Deploying the service seems to work just fine.