Skip to content

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

Closed
onedr0p opened this issue Jun 28, 2023 · 10 comments
Closed

crd.yaml is not attached to Github release for v0.12.0 #247

onedr0p opened this issue Jun 28, 2023 · 10 comments

Comments

@onedr0p
Copy link

onedr0p commented Jun 28, 2023

Previous releases of SUC there has been a crd.yaml artifact attached to the Github release, it appears missing for v0.12.0.

@IT-Cru
Copy link

IT-Cru commented Jun 29, 2023

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

https://github.com/rancher/system-upgrade-controller/releases/latest/download/system-upgrade-controller.yaml

get a HTTP status 404 currently. So all usages in any CI jobs or automated processes could be broken.

@hurzelpurzel
Copy link

I ended up at the same problem when using the k3s website link to the manifest. Therefore I switched to v11

@onedr0p
Copy link
Author

onedr0p commented Jun 30, 2023

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 kubectl apply -f https://... but it doesn't look like it will get the love it needs to make that happen.

I don't mean to come off rude or anything, just hopefully giving some constructive criticism that may help make things better.

@hurzelpurzel
Copy link

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.

@hurzelpurzel
Copy link

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 kubectl apply -f https://... but it doesn't look like it will get the love it needs to make that happen.

I don't mean to come off rude or anything, just hopefully giving some constructive criticism that may help make things better.

Added a helm chart in PR #248

@onedr0p
Copy link
Author

onedr0p commented Jul 7, 2023

@brandond any thoughts here?

@brandond
Copy link
Member

brandond commented Jul 7, 2023

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.

@brandond
Copy link
Member

brandond commented Jul 7, 2023

It looks like something changed in the CI environment, we'll have to fix that and cut a new tag.

@onedr0p
Copy link
Author

onedr0p commented Jul 20, 2023

Any update here?

@onedr0p
Copy link
Author

onedr0p commented Jul 21, 2023

Looks like this was fixed. Thanks!

@onedr0p onedr0p closed this as completed Jul 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants