-
Notifications
You must be signed in to change notification settings - Fork 120
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
Feature: Allow ImageCache CR to be created in a different namespace; not restricted to the one to which kube-fledged was deployed #86
Comments
@brainfair : The ImageCache CR has to be created in the same namespace where kube-fledged controller and webhook-servers are installed. Having them in different namespaces is not supported. You can deploy kube-fledged to any namespace you wish. Do you need the capability to have the ImageCache CR created in a different namespace? |
Yes, I think it would be a good idea if one kube-fledged works with CRs from the others namespaces, because if we have many namespaces (over 100 for example) it`s be huge overhead to deploy kube-fledged to each namespace. |
Complete log:-
|
Hello,
I try to create ImageCache not in kube-fledged NS.
After this pulling jobs don`t create and I see many errors in kubefledged-controller like:
E0729 09:25:24.612184 1 image_manager.go:446] error pulling image 'myimage' to node 'mynode': the namespace of the provided object does not match the namespace sent on the request E0729 09:25:24.810254 1 image_manager.go:464] Error creating job in node &Node....
If I deploy ImageCache to kube-fledged NS all fine
Envorinment:
bare-metal k8s version: 1.20.7
The text was updated successfully, but these errors were encountered: