Skip to content
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

[Module Catalog] Prepare testing playground for Otters and Hasselhoffs #2007

Closed
3 tasks done
janmedrek opened this issue Nov 4, 2024 · 1 comment
Closed
3 tasks done
Assignees

Comments

@janmedrek
Copy link
Contributor

janmedrek commented Nov 4, 2024

Description

In order to implement UI/CLI changes it would be great to have some sort of testing ground for all ModuleCatalog-related changes.

Acceptance Criteria

  • Basic CRs set up and present on the DEV landscape + can be checked/interacted with
  • Template Operator can be a lab rat for this case
    • prepare some dummy fields (fill them with anything) OR improve what is in the Template Operator artifacts
    • one module, two different versions (for different channels)
    • make sure the dummy module is not propagated to stage/prod
  • Modulectl released

Attachements
Contact people:

@janmedrek janmedrek changed the title [Module Catalog] Prepare testing playground for Otters and Baywatch guys [Module Catalog] Prepare testing playground for Otters and Hasselhoffs Nov 4, 2024
@lindnerby lindnerby self-assigned this Nov 13, 2024
@lindnerby
Copy link
Member

lindnerby commented Nov 14, 2024

We have created two versions of template-operator on the DEV landscape. with a corresponding ModuleReleaseMeta for mapping the version of 0.0.1-catalog-meta to channel regular and the the version of 0.0.2-catalog-meta to channel fast.

To inspect the modules' versions, run in the context of kyma-mps-dev:

kubectl get moduletemplate -n kcp-system -l operator.kyma-project.io/module-name=template-operator

To have a look at channel mappings, run:

kubectl get mrm -n kcp-system template-operator -o yaml

To install a version of these modules in the context of SKRs, proceed as usual and add the template-operator module to the spec.modules list with the corresponding channel you want to use it from. For example:

spec:
  modules:
  - channel: regular
    name: template-operator

The templates and artifacts where created with the latest release of modulectl and these input config files:

name: kyma-project.io/module/template-operator
version: 0.0.1-catalog-meta
manifest: https://github.com/kyma-project/template-operator/releases/download/1.0.1/template-operator.yaml
security: sec-scanners-config.yaml
repository: https://github.com/kyma-project/template-operator
documentation: https://github.com/kyma-project/template-operator/blob/main/README.md
defaultCR: https://github.com/kyma-project/template-operator/releases/download/1.0.1/default-sample-cr.yaml
icons:
  - name: module-icon
    link: https://github.com/kyma-project/template-operator/blob/main/docs/assets/logo.png
associatedResources:
  - group: operator.kyma-project.io
    version: v1alpha1
    kind: Managed
manager:
  name: template-operator-controller-manager
  namespace: template-operator-system
  group: apps
  version: v1
  kind: Deployment
name: kyma-project.io/module/template-operator
version: 0.0.2-catalog-meta
manifest: https://github.com/kyma-project/template-operator/releases/download/1.0.1/template-operator-statefulset.yaml
security: sec-scanners-config.yaml
repository: https://github.com/kyma-project/template-operator
documentation: https://github.com/kyma-project/template-operator/blob/main/README.md
icons:
  - name: module-icon
    link: https://github.com/kyma-project/template-operator/blob/main/docs/assets/logo.png
associatedResources:
  - group: operator.kyma-project.io
    version: v1alpha1
    kind: Managed
manager:
  name: template-operator-controller-manager
  namespace: template-operator-system
  group: apps
  version: v1
  kind: StatefulSet

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

3 participants