Skip to end of banner Go to start of banner

ONAP deployment dependencies

Skip to end of metadata

Created by Andreas Geißler , last modified on Jul 27, 2023

Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

Current Helm deployment

RBAC setup:

Problems, when component is deployed individually (without "onap" master chart):

ClusterRoleBinding "onap-binding" is missing and need to be added before deployment
"onap-roles-wrapper" is required, as onap-* roles are used by the "ServiceAccount" chart (https://gitlab.devops.telekom.de/tnap/operations/playground/guido_rosenbaum/oom/-/tree/master/kubernetes/common/serviceAccount)
ServiceAccount chart uses a naming schema for the default "role" binding -> $name := printf "%s-%s" (include "common.release" $dot) $role_typ

Solution for individual component deployment

In the common chart "ServiceAccount" the feature exists to create local Roles based on the values.yaml settings (needs to be tested:

No labels