OCI registries for helm

Proposers

• Gabriel Cuba (Whitestack)
• Luis Vega (Whitestack)

Description

OCI-based registries are supported by default since helm v3.8.0. OSM should enable the addition of OCI-based helm repos to be used by KNFs.

Demo or definition of done

• OCI-based helm registries could be added to OSM with osmclient
• Helm based KNFs can point to OCI-based registries.

Robot test k8s_04 should be adapted/extended to use OCI-based registries.

added LCM N2VC labels

added to epic &16

assigned to @cubag

added TO BE PRESENTED label

changed the description

changed the description

removed TO BE PRESENTED label

added PRESENTED IN TECH CALL label

The support of OCI registries from OSM makes all the sense, and the fact that we will have to call helm registry from OSM make also sense. It is suggested to remove any mention to potential implementations in the description. For instance, the use of repo-add in osmclient could be only an example.

As part of the Nephele project, ATOS is already developing this feature and would like to take part in the design and development part to contribute with our input and code. If we only support public OCI registries, the feature becomes much easier to develop since it only has to deal with registry version detection (no osm repo-add needed) in order to use the appropiate helm command (which has a slightly different syntax)

changed the description

removed PRESENTED IN TECH CALL label

changed milestone to %Approved

changed milestone to %Design

removed milestone %Design

added PRESENTED IN TECH CALL label

removed PRESENTED IN TECH CALL label

changed milestone to %Approved

changed milestone to %Design

Checklist for feature owners:

• Add the link to the design (Etherpad)
• Add the links to the Gerrit changes (commits) related to the feature and update the list when needed.
• Contribute documentation in osm-user-guide and add link to the merge request.
• Contribute release notes for the feature and add link to the merge request.
• Relate IM changes to SOL006 v2.6.1
• Relate NBI changes to SOL005 v3.3.1
• Add E2E Robot Test. If no Robot Test is required, it should be explicitly explained.

changed milestone to %Development

Design: https://osm.etsi.org/pad/p/feature10997

added NBI SOL005 osmclient labels and removed LCM label

Gerrit changes:

• SOL005: https://osm.etsi.org/gerrit/#/c/osm/SOL005/+/13975/
• NBI:
  • https://osm.etsi.org/gerrit/#/c/osm/NBI/+/13977/
  • Fix in NBI to support URLs: https://osm.etsi.org/gerrit/#/c/osm/NBI/+/14044/
• osmclient: https://osm.etsi.org/gerrit/#/c/osm/osmclient/+/13976/
• N2VC: https://osm.etsi.org/gerrit/#/c/osm/N2VC/+/14043/
• Tests:
  • https://osm.etsi.org/gerrit/#/c/osm/tests/+/14062/
  • https://osm.etsi.org/gerrit/#/c/osm/tests/+/14059/
• Devops: https://osm.etsi.org/gerrit/#/c/osm/devops/+/14069/

Checklist:

• Please contribute documentation in osm-user-guide and paste here the link to the merge request: osm-doc/osm-user-guide!148 (merged)
• Please contribute release notes in osm-release-notes, under rel15/srcand paste here the link to the merge request: https://osm.etsi.org/gitlab/osm-doc/osm-release-notes

No changes in the IM.

There are changes in NBI spec (SOL005). K8s repositories for Helm have changed to allow oci flag. The spec in SOL005 v3.3.1 doesn't include any modelling of the repositories. Therefore, all the changes in OSM are unique, not finding a similar element in SOL005 v3.3.1.

• Merge request for VNF-onboarding guidelines: vnf-onboarding/vnf-onboarding-guidelines!27
• osm-user-guide: osm-doc/osm-user-guide!148 (merged)
• osm-release-notes: https://osm.etsi.org/gitlab/osm-doc/osm-release-notes/-/merge_requests/24

changed milestone to %Testing and Review