You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If an extension (cert-manager, kfserving...) is already installed in the cluster and fuseml-installer is told to install it, it should be able to detect existing ones and just calmly skip the installation without raising an error.
This could be done by simply checking for existence of a namespace, in a simplest case. If we want to be more sure, we could check for some specific resource in given namespace, and the name of such resource needs to be provided via description.yaml file.
Related to #272 : such 3rd party extensions would not be deleted when uninstalling FuseML because their namespace would not be labeled by FuseML.
The text was updated successfully, but these errors were encountered:
By labeling the namespaces created for extensions,
make sure to
- detect existing extensions and not overwrite them (closesfuseml#273)
- only delete the extensions that were installed by fuseml (closesfuseml#272)
By labeling the namespaces created for extensions,
make sure to
- detect existing extensions and not overwrite them (closesfuseml#273)
- only delete the extensions that were installed by fuseml (closesfuseml#272)
jsuchome
added a commit
to jsuchome/fuseml
that referenced
this issue
Oct 14, 2021
By labeling the namespaces created for extensions,
make sure to
- detect existing extensions and not overwrite them (closesfuseml#273)
- only delete the extensions that were installed by fuseml (closesfuseml#272)
By labeling the namespaces created for extensions,
make sure to
- detect existing extensions and not overwrite them (closesfuseml#273)
- only delete the extensions that were installed by fuseml (closesfuseml#272)
(cherry picked from commit 6a1bb0d)
If an extension (cert-manager, kfserving...) is already installed in the cluster and fuseml-installer is told to install it, it should be able to detect existing ones and just calmly skip the installation without raising an error.
This could be done by simply checking for existence of a namespace, in a simplest case. If we want to be more sure, we could check for some specific resource in given namespace, and the name of such resource needs to be provided via description.yaml file.
Related to #272 : such 3rd party extensions would not be deleted when uninstalling FuseML because their namespace would not be labeled by FuseML.
The text was updated successfully, but these errors were encountered: