Change Kyma settings
To change your Kyma settings, you simply deploy the same Kyma version that you're currently using, just with different configuration values.
You can use the --values-file
and the --value
flag.
To override the standard Kyma configuration, run:
Click to copykyma deploy --values-file {VALUES_FILE_PATH}In the following example,
{VALUES_FILE_PATH}
is the path to a YAML file containing the desired configuration:- For
global
, the values ofimages.istio_pilot.version
,images.istio_pilot.directory
andcontainerRegistry.path
will be overridden to1.11.4
,istio
anddocker.io
respectively. - For
ory
, the values ofhydra.deployment.resources.limits.cpu
andhydra.deployment.resources.requests.cpu
will be overridden to153m
and53m
respectively. - For
monitoring
, the values ofalertmanager.alertmanagerSpec.resources.limits.memory
andalertmanager.alertmanagerSpec.resources.requests.memory
will be overridden to304Mi
and204Mi
respectively.
Click to copyglobal:containerRegistry:path: docker.ioimages:istio_pilot:version: 1.11.4directory: "istio"ory:hydra:deployment:resources:limits:cpu: 153mrequests:cpu: 53mmonitoring:alertmanager:alertmanagerSpec:resources:limits:memory: 304Mirequests:memory: 204Mi- For
You can also provide multiple values files at the same time:
Click to copykyma deploy --values-file {VALUES_FILE_1_PATH} --values-file {VALUES_FILE_2_PATH}
NOTE: If a value is defined in several files, the value of the last file in the list is used.
Alternatively, you can specify single values instead of a file:
Click to copykyma deploy --value ory.hydra.deployment.resources.limits.cpu=153m \--value ory.hydra.deployment.resources.requests.cpu=53m \--value monitoring.alertmanager.alertmanagerSpec.resources.limits.memory=304Mi \--value monitoring.alertmanager.alertmanagerSpec.resources.requests.memory=204Mi
NOTE: If a value is defined several times, the last value definition in the list is used. The
--value
flag also overrides any conflicting value that is defined with a--value-file
flag.