Skip to content

Bump Intel version to 1.3.5#209

Merged
danc094codetogether merged 87 commits intomainfrom
dev
Apr 28, 2026
Merged

Bump Intel version to 1.3.5#209
danc094codetogether merged 87 commits intomainfrom
dev

Conversation

@danc094codetogether
Copy link
Copy Markdown
Contributor

No description provided.

wgalanciak and others added 30 commits May 7, 2025 19:53
* Set environment variables via .env file.

* Missing change

* Change how hostnames and secret are set.

* changes for env template

* add env variable resolver on sso redirect value
* tweak name of dhparam.pem env var

* fix env var name in nginx template

* fix pam to pem
* fix(intel-chart): handle nil ai.openai.api_key to prevent template errors

Adjusted the Helm chart template for ai-secrets to avoid referencing ai.openai.api_key and
ai.external.api_key when undefined.
This fixes a fatal error during `helm template` when AI mode is set to `bundled`
and no OpenAI config is present. Ensures compatibility with bundled-only deployments.

* Changes to fix workflow issues
Previously, the Helm chart required either 'bundled' or 'external' AI mode to be configured, making it
mandatory to include AI integration. This commit introduces a new flag `ai.enabled` to allow disabling
AI features entirely, enabling Intel to be deployed without any AI-related containers or resources.
- Removed the section referring to metrics(prometeus), etc from the README

Co-authored-by: engineering <engineering@codetogether.com>
)

* Make sidecar AI container resource block optional in deployment

- Updated deployment.yaml to include the `resources` block for the `codetogether-llm` sidecar only if values are defined in values.yaml.
- Ensures the bundled AI container can run without specifying resource limits/requests by default.
- Improved overall Helm template flexibility for embedded AI mode.
- Validated that runs with AI Container embeeded.

* Enable support for external AI provider

- Updated deployment.yaml to support both bundled and external AI modes, allowing selection via .Values.ai.mode.
- Added manifests for external AI integration:
  - ai-config ConfigMap: defines external provider and URL.
  - ai-external-secret Secret: stores the external API key.
- Verified that external AI mode works by routing requests through the configured external service.

* feat: automate creation of external AI ConfigMap and Secret from values.yaml

- Added Helm templates to generate ai-config ConfigMap and ai-external-secret Secret automatically when AI external mode is enabled.
- ConfigMap values (ai_provider, ai_url) and Secret value (api-key) are now configurable via values.yaml.
- Ensured resources are only created when ai.enabled=true and ai.mode=external.

* feat: allow use of existing or Helm-managed ai-external-secret in deployment

- Updated deployment.yaml to support referencing a user-provided Secret for AI external API key, with fallback to Helm-managed creation.
- Added ai-external-secret.yaml template to optionally create the secret from values if not provided.

* Fixing helm template validations

* Adding values configuration

---------

Co-authored-by: engineering <engineering@codetogether.com>
* Change resources of ai

* Include gen ai on docker compose.

* undo changes
* Fixes after Testing
- Refactored deployment.yaml to reference ai.externalSecret.name when create: false
- Corrected CT_HQ_OLLAMA_AI_API_KEY key to apiKey to match Secret’s stringData
- Updated ai-external-secret.yaml to generate a Secret only when create: true

* Bump intel chart version to 1.2.5

* Fix to user http://codetogether-llm:8000/ always

---------

Co-authored-by: engineering <engineering@codetogether.com>
Co-authored-by: engineering <engineering@codetogether.com>
* initial config

* Docker compose example to run keycloak

---------

Co-authored-by: Ignacio Moreno <nmorenor@gmail.com>
* initial config

* Docker compose example to run keycloak

* Undo properties file change

* fixes on properties file

---------

Co-authored-by: Wojciech Galanciak <wojtek@codetogether.com>
* initial config

* Docker compose example to run keycloak

* Undo properties file change

* fixes on properties file

---------

Co-authored-by: Wojciech Galanciak <wojtek@codetogether.com>
danc094codetogether and others added 24 commits November 18, 2025 16:15
Removed run-nginx volume mount from deployment.
Updated volume mounts and volumes to use memory medium for tmp and run-volatile.
* feat(helm): add warning log when deprecated AV settings are detected

Fixes: #192

- Added a startup warning when any Audio/Video related values
  (av.enabled, av.serverIP, av.stunServers, av.jitsiUrl) are present
  in Helm chart configurations.
- Ensures deployments are notified that built in A/V support is no
  longer available.
- No functional behavior changed, only logs a warning at container start.

* chore: add AV deprecation warning and clean up env vars

- Add Helm NOTES warning when AV related values are configured
- Remove unused CT_AV_DEPRECATED_WARNING environment variable from Deployment
- Keep AV env configuration minimal while clearly signaling that A/V is no longer supported
…199)

Fixes: #198

- add service.annotations to values.yaml with default {}
- render metadata.annotations in templates/service.yaml via .Values.service.annotations
- keep backward compatibility when annotations are not set
…ntel deployment (#202)

Fixes: #201

- This PR adds support for configurable “startup containers” by allowing users to define Kubernetes initContainers in the Intel Helm chart.
#205)

* Add dedicated Keycloak readiness gate to prevent Intel starting too early

This PR adds an optional Docker Compose overlay that supports customers running a dedicated/external Keycloak (Keycloak not started by our compose stack).

Some customers still use an external Keycloak. In this mode, the previously recommended depends_on: codetogether-keycloak: condition: service_healthy cannot apply, because there is no codetogether-keycloak service in the final stack. As a result, docker compose up --wait can fail because codetogether-intel starts before Keycloak is reachable.

Add a new compose overlay: compose/compose.dedicated-keycloak.yaml

Introduces a lightweight keycloak-ready service with a healthcheck that polls:
https://${KEYCLOAK_FQDN}/realms/${KEYCLOAK_REALM}/.well-known/openid-configuration

Makes codetogether-intel depend on:

- cassandra: service_healthy (keep existing dependency)
- keycloak-ready: service_healthy (new gate)

- Add a short compose/README.md describing:
- required .env variables (KEYCLOAK_FQDN, KEYCLOAK_REALM)
- exact docker compose command using the overlay

docker compose \
  -f compose/compose.yaml \
  -f compose/compose.dedicated-keycloak.yaml \
  --env-file ./.env \
  up --pull always --wait -d

* Fix
- The chart currently supports extraVolumes, extraVolumeMounts, and
extraEnvVars but has no way to inject additional containers into
the pod spec.
- This adds an extraContainers parameter (empty by
default) following the same convention, enabling sidecar use cases
like Fluent Bit for CloudWatch log shipping.
Template the hardcoded path (/) and port (http) in liveness and
readiness probes so they can be overridden via values. Defaults
preserve existing behavior for all current deployments.

CTPD-4358

Made-with: Cursor
@danc094codetogether danc094codetogether merged commit 248dffb into main Apr 28, 2026
1 check passed
@TimWebb
Copy link
Copy Markdown
Contributor

TimWebb commented Apr 28, 2026

🔎 Product Specs PR Tracker

Spec page updated: SaaS Frontend, Admin Portal & Staging Infrastructure (2026-04-10 → 2026-04-24 rollup)
The following spec section(s) appear to have drifted:

  • The "Intel (cthq) Staging Deploy Workflow" section did not document health probe configurability. PR Bump Intel version to 1.3.5 #209 introduces configurable livenessProbe.path, livenessProbe.port, readinessProbe.path, and readinessProbe.port in the Intel Helm chart values.yaml with backward-compatible defaults (/ and http).
  • Chart version bumped from 1.3.4 → 1.3.5; spec did not previously track the Intel chart version.

Linked Jira: CTPD-4358 (parent: CTPD-4277 — SaaS 4.7 Staging Hardening)


Automated by Product Specs PR Tracker. If this is a false positive or the spec should be updated differently, ping in #dev-product.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants