FIG. 2 illustrates an operation 200 of a management service to add a CNF to a deployment environment according to an implementation. The steps of operation 200 are referenced parenthetically in the paragraphs that follow with reference to systems and elements of computing environment 100.

In operation 200, management service 130 will identify (201) a package associated with a CNF in a first repository. In some implementations, the user will provide a path to the CNF, wherein the CNF may comprise a Helm chart in some examples that can include a plurality of configuration files (YAML files) that are packaged as part of a Helm chart. When the path is provided to management service 130 or is registered with management service 130, management service 130 may identify (202) one or more configuration parameters associated with the CNF and update (203) one or more files for the CNF based on the configuration parameters. In some implementations, the configuration parameters will comprise a node selector (referred to as “nodeselector” in Kubernetes) that is used to define requirements for nodes or hosts for deploying the application.