-
Notifications
You must be signed in to change notification settings - Fork 239
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
OCIStorage: bundles still created as k8s-resources ? #3359
Comments
Hi, thanks for reporting this. Resources are still listed as a reference for the UI, but should not include the real content. That |
The
|
Oh sorry, the
Under status:
...
- apiVersion: v1
kind: ServiceAccount
name: blackbox-exporter-prometheus-blackbox-exporter
namespace: blackbox-exporter I wasn't sure if this is due to it being EXPERIMENTAL (and writing both just in case) or actually a bug. |
If it's in the spec then sounds like a bug :) We will triage and schedule for being fixed. Thanks!! |
Hi,
i started testing the OCIStorage experimental feature. I added this to the gitRepo:
And on deleting all bundles in the gitRepo i can see blobs popping up in the registry. So far so good, but parallel i still see the bundles being generated inside the
fleet-default
-namespace (using rancher-2.10.2 with fleet-0.11.3 ). Eg the rancher-monitoring bundle still takes ~1,2MB in etcd and the resources are listed:It was my understanding that this is either OCIStorage OR k8s-resource? Am i wrong or is this just not implemented yet?
The text was updated successfully, but these errors were encountered: