-
Notifications
You must be signed in to change notification settings - Fork 111
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
Upgrade Operator SDK to v0.18.2 #312
Conversation
f9913e0
to
af30793
Compare
4a92074
to
bf688de
Compare
deploy/olm-catalog/splunk/1.0.0/splunk.v1.0.0.clusterserviceversion.yaml
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.
Seems like all the changes on CRD files are due to the yq version. Wondering if you are using the yq version 3.3.x, by any chance? yq 3.3.x output is not uniform across the Linux distributions, so we stuck with 3.2.x.
@gaurav-splunk @sgontla @jryb @akondur just a note, these changes are in flux right now as a result of trying to handle the issues described here #312 (comment) We are seeing issues due to the interaction of OperatorSDK v0.18.2 and the current iteration of the make_bundle.sh script. Working through those, so perhaps reviewing should be put on hold for now. |
Regarding your comment @sgontla the CRD changes occur with yq v3.2.1, they are due to running
with Operator SDK version 0.18.2. |
Upgrade operator sdk to v0.18.2
fe8b7b5
to
7eda1a0
Compare
No description provided.