...
Code Block |
---|
# we can set pull policy for every image under the global key global: pullPolicy: IfNotPresent cps: # enable certain services under their respective keys (here we enable CPS etc.) enabled: true cps-temporal: enabled: false cps-core: config: # under the additional section we can affect certain configurations of the Spring Boot application (new prefix for the REST endpoints) additional: rest: api: cps-base-path: /kiscica postgres: config: pgUserExternalSecret: '{{ .Release.Name }}-postgres-{{ include "common.postgres.secret.userCredentialsUID" . }}' postgres-init: config: # add external secrets to the deployments pgUserExternalSecret: '{{ .Release.Name }}-postgres-{{ include "common.postgres.secret.userCredentialsUID" . }}' sdnc: enabled: false strimzi: enabled: true # set the running number of replicas replicaCount: 1 |
Compile onap chart
When you modify the deployment yaml you need to recompile the onap chart (it is not necessary for installation or when you just modify the values.yaml)
Pnf-simulator
Open pnf-simulator's directory in your terminal. Compile and upload must be run once for each cluster.
...
Code Block | ||
---|---|---|
| ||
chartmuseum --storage local --storage-local-rootdir /root/helm3-storage -port 8879 & |
EOF Exception
sometimes when you start an install you can see an error message
Code Block | ||
---|---|---|
| ||
install.go:192: [debug] Original chart version: ""
Error: INSTALLATION FAILED: unexpected EOF
helm.go:84: [debug] unexpected EOF
INSTALLATION FAILED
main.newInstallCmd.func2
helm.sh/helm/v3/cmd/helm/install.go:141
github.com/spf13/cobra.(*Command).execute
github.com/spf13/cobra@v1.5.0/command.go:872
github.com/spf13/cobra.(*Command).ExecuteC
github.com/spf13/cobra@v1.5.0/command.go:990
github.com/spf13/cobra.(*Command).Execute
github.com/spf13/cobra@v1.5.0/command.go:918
main.main
helm.sh/helm/v3/cmd/helm/helm.go:83
runtime.main
runtime/proc.go:250
runtime.goexit
runtime/asm_386.s:1326 |
It is a bug in helm, not necessary to do anything, just rerun the installation
Strimzi-kafka can not start
You can run only one strimzi-kafka per cluster. When your strimzi-kafka can not start, maybe there is another one on the cluster in a different namespace. Uninstall the other and then restart your strimzi-kafka