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
The recent changes required by the Community Modules story enable us to start working on the module related commands in kyma CLI. Multiple changes were introduced to the API of Kyma Lifecycle Manager, and thus, the new planned commands for module management should go along with them.
We want to have a set of convenient kyma CLI commands to interact with Kyma Module Catalog.
Changes in Licecycle management API
ModuleTemplate CRD:
.spec.channel field was deprecated
.spec.info introduced, it includes basic information on the Module that can be displayed in Busola, such as repo/docu links, icons
.spec.resources introduced, it contains a reference to all the resources that need to be installed in order for the Module to be operational (used for manual installation)
spec.associatedResources introduced, it contains a list of all module-related CRDs
.spec.manager introduced, contains a reference to the Module manager, which can be used to determine whether manually installed module is operational or not
ModuleReleaseMeta CRD introduced
It contains ties between module versions and channels used
Acceptance criteria
User of managed cluster should be able to discover modules w/o enabling them, for example:
discover available modules from catalog
read details about the module (what API does it offer)
User of managed cluster should be able to manage modules on his managed cluster, for example:
enable managed module (with default module CR)
enable managed module (with custom module CR)
disable managed module
unmanage module (keep module resources and API, but do not keep them managed by LFM )
Having the new Kyma CLI ready, we have to remember to update tutorials, including these in the Discovery Center missions. Please add it to the Definitions of Done for the epic.
Having the new Kyma CLI ready, we have to remember to update tutorials, including these in the Discovery Center missions. Please add it to the Definitions of Done for the epic.
Description
The recent changes required by the Community Modules story enable us to start working on the module related commands in kyma CLI. Multiple changes were introduced to the API of Kyma Lifecycle Manager, and thus, the new planned commands for module management should go along with them.
Reasons
We want to have a set of convenient kyma CLI commands to interact with Kyma Module Catalog.
Changes in Licecycle management API
.spec.channel
field was deprecated.spec.info
introduced, it includes basic information on the Module that can be displayed in Busola, such as repo/docu links, icons.spec.resources
introduced, it contains a reference to all the resources that need to be installed in order for the Module to be operational (used for manual installation)spec.associatedResources
introduced, it contains a list of all module-related CRDs.spec.manager
introduced, contains a reference to the Module manager, which can be used to determine whether manually installed module is operational or notAcceptance criteria
User of managed cluster should be able to discover modules w/o enabling them, for example:
User of managed cluster should be able to manage modules on his managed cluster, for example:
Attachments
We have been provided with sample
moduletemplates
andModuleReleaseMeta
objects on development environmentkyma-project/lifecycle-manager#2007 (comment)
The text was updated successfully, but these errors were encountered: