Code owners
Assign users and groups as approvers for specific file changes. Learn more.
exposing_kubernetes_resources.md 6.54 KiB
Expose and manage Kubernetes Custom Resource Definitions (Operators) in a Kubernetes Cluster
Intended Audience: OpenSlice Service Designers
OpenSlice is capable of exposing Kubernetes Resources and Definitions as Service Specifications.
Use OpenSlice to expose NFV resources in service catalogs and deploy them in complex scenarios (service bundles) involving also other systems:
- Include external resources, e.g. RAN controllers
- Manage multiple NSDs in linked NFVOs (OSM installations)
- Combine designed services
- Control the lifecycle of services and pass values from one service to another
Awareness for CRDs and CRs in cluster
CRDs and CRs can appear (disappear) or change status at any time in a cluster. OpenSlice Resource Inventory need to be aware of these events.
When installing OpenSlice you can configure at least one management cluster. OpenSlice connects via a provided kubeconf
- On start-up, OSL tries to register this cluster and context to OSL catalogs.
- After the registration of this cluster as a Resource in OSL OSL is always aware of all CRDs and their CRs in the cluster, even if a CRD or CR is added/updated/deleted in the K8S cluster outside of OSL
- Resources created by OpenSlice have labels, e.g. (org.etsi.osl.*)