-
Notifications
You must be signed in to change notification settings - Fork 96
crd.yaml
is not attached to Github release for v0.12.0
#247
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
Comments
Also other assets are missing if you compare release v0.12.0 and previous one v0.11.0. Normally they are 21 assets in last previous releases and in v0.12.0 only 7 exists. Also system-upgrade-controller.yaml is missing and all users which requests get a HTTP status 404 currently. So all usages in any CI jobs or automated processes could be broken. |
I ended up at the same problem when using the k3s website link to the manifest. Therefore I switched to v11 |
Sorry to be a bit of a bother but it kind of sucks how painful this project is to deploy... no Helm chart, barely functional kustomize support, no way to install CRDs separately outside using the Github release artifact (which is currently broken). It would be nice to have a standard/cleaner automated way to install and manage updates to this outside of I don't mean to come off rude or anything, just hopefully giving some constructive criticism that may help make things better. |
Checked the scripts subfolder. All the build stuff is located there. I found that the AMD64 build hasn't been run for v.12.0 and that is reason for the missing CRD. |
Added a helm chart in PR #248 |
@brandond any thoughts here? |
Tag CI failed, for reasons that do not appear to be related to anything that was changed in this release. I'll re-run it and see if it completes successfully. |
It looks like something changed in the CI environment, we'll have to fix that and cut a new tag. |
Any update here? |
Looks like this was fixed. Thanks! |
Previous releases of SUC there has been a
crd.yaml
artifact attached to the Github release, it appears missing for v0.12.0.The text was updated successfully, but these errors were encountered: