Automatically configure Ollama integration when LLM is enabled

[wgalanciak]

Description

If as a part of the intel deployment, the ai service is enabled:

..
ai:
  enabled: true
..

We should pass required information to the codetogether-intel container to provide default plugin configuration. To do it, we need to set the following env variables:

- CT_HQ_OLLAMA_AI_API_KEY
- CT_HQ_OLLAMA_AI_URL
- CT_HQ_OLLAMA_AI_MODEL_NAME

[danc094codetogether]

To configure the AI integration, follow these steps for each mode:

Bundled mode:

In the values.yaml, set:

ai:
  enabled: true
  mode: "bundled"
  image:
    repository: <bundled-ai-image>
    tag: <tag>

No extra resources are required. The deployment will automatically run the AI as a sidecar container within the same Pod.

External mode:

In the values.yaml, we have two options to configure external AI integration:

Option 1: Let Helm create the Secret (default, recommended for most cases)

ai:
  enabled: true
  mode: "external"
  provider: "<AI Provider>"
  url: "https://<AI URL>"
  externalSecret:
    create: true
    name: ""                 # Leave empty for default name
    apiKey: "<API Key>"      # API key goes here

• What happens: The Helm chart will automatically create a Secret containing the API key.
• How it works: The deployment will use this Secret to provide credentials.

Option 2: Use an existing Secret (advanced, for stricter security or external management)

1. First, manually create the Secret:

kubectl create secret generic my-custom-ai-secret \
  --namespace=portal \
  --from-literal=api-key="your-external-api-key"

2. Then, reference it in the values.yaml:

ai:
  enabled: true
  mode: "external"
  provider: "<AI Provider>"
  url: "https://<AI URL>"
  externalSecret:
    create: false
    name: "my-custom-ai-secret"
    apiKey: ""        # Ignored when using an existing Secret

• What happens: The chart will NOT create a new Secret; it will use the one specified by name.

Notes:

• For bundled, everything is managed by the chart just set the mode and image.
• For external mode, can either let Helm create the Secret for the API key, or reference the Secret created manually for better security or centralized secret management.

[danc094codetogether]

Both bundled and external modes were tested and are working as expected. The integration, pod startup, and /api/generate endpoint were verified for both setups.

[DavidRS13]

@danc094codetogether could you provide the configuration for docker compose.yaml?

[danc094codetogether]

@DavidRS13 this task is related to helm charts.

[wgalanciak]

@danc094codetogether this is not really fixed as the PR that it is linked does not fix this issue.