Skip to main content

How to configure Grain

Grain is deployed through the data Helm chart. In Argo CD, select this chart and enter your configuration in Helm > Values.

The chart values are grouped by application:

  • kokos configures the Grain runtime and its dispatcher.
  • webup configures the Webup interface.
  • restapi installs the separate legacy RestAPI component. The current Grain APIs are provided by Kokos.

Each section has its own configuration and has to be indented under the relative top level object.

For example, the configuration

webup:
  cfg:
    context: WebUP

which configures the URL context for webup, has to be placed under the top level object webup to be passed to Grain, in this fashion:

webup:
  webup:
    cfg:
      context: WebUP

Each top level object has a boolean field called enabled, which enables (or disables when set to false) the installation of that application.

With the data chart, all three applications are enabled by default. Using the enabled field you can disable the installation of one or more applications.

The current Grain APIs are provided by Kokos, so you do not need restapi to use them. In this example, only Kokos is installed, since webup and restapi are both disabled:

kokos:
  enabled: true

webup:
  enabled: false

restapi:
  enabled: false
info

The data-smeup chart used for Grain with AS400 has different defaults: Kokos is enabled, while Webup and the legacy RestAPI component are disabled. See How to configure Grain with AS400.

See the Grain installation guide for the Argo CD deployment steps.

Do not store passwords, API keys, or other credentials in a values file committed to a repository. Supply secrets through your deployment's approved secret-management mechanism.