Skip to content

docs(fluxcd): add Limitations section and update controller version#190

Open
mayank-devtron wants to merge 15 commits into
docv2-sitefrom
docs/fluxcd-setup-and-limitations
Open

docs(fluxcd): add Limitations section and update controller version#190
mayank-devtron wants to merge 15 commits into
docv2-sitefrom
docs/fluxcd-setup-and-limitations

Conversation

@mayank-devtron

Copy link
Copy Markdown
Contributor
  • Add a Limitations section to the FluxCD GitOps page (supported strategies, no rollback, no manual sync, manual controller setup, prerequisites)
  • Update FluxCD controller install command from v0.35.0 to v2.7.5

- Add a Limitations section to the FluxCD GitOps page (supported
  strategies, no rollback, no manual sync, manual controller setup,
  prerequisites)
- Update FluxCD controller install command from v0.35.0 to v2.7.5

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@mayank-devtron mayank-devtron requested review from a team as code owners June 28, 2026 17:24
mayank-devtron and others added 9 commits June 28, 2026 23:07
- Add a Capabilities section (pod restart monitoring, event tracking,
  resource caching)
- Expand the enableResourceList flag description to explain the
  per-cluster resource-caching capability (verified against orchestrator
  getResourceListV2 path)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Document the agentic capabilities of the AI agent (troubleshooting and
remediation, cost insights, application & resource Q&A, documentation
search), derived from the ai-agent (Athena) backend's MCP tool set.
Kept at product level to match the rest of the public page.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Add a 'Caching for Multi-Architecture Builds' subsection to the Docker
Layer Caching docs, covering the orchestrator-cm flags BUILDX_CACHE_MODE_MIN
and ASYNC_BUILDX_CACHE_EXPORT and the per-architecture build cache.
Verified against orchestrator (CiService.go) and ci-runner (DockerHelper.go).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The predefined variables are not shown in the scoped-variable widget,
so users had no example of how to reference them. Add the @{{...}}
usage syntax with a DEVTRON_IMAGE example, incl. the double-quoted form
for deployment templates.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Add a new user-facing API-reference page documenting the GitOps-to-GitOps
migration endpoints (POST /orchestrator/migration/deploy and
/migration/deploy/app-level): request/response schema, gitOpsProviderId
target, dryRun, super-admin auth, and recommended workflow. Wire it into
the Global Configurations sidebar. Verified against orchestrator
deployEntityMigration (apiBean_ent.go, MigrationRestHandler_ent.go).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Document how to enable the SRE debug (Holmes) capability and the Ask
Devtron Expert chatbot: deploy Redis, add Athena backend env vars to the
ai-agent chart (HOLMES_*, CHAT_AGENT_MAX_*, REDIS_URL), and set the
orchestrator-cm (FEATURE_ASK_DEVTRON_EXPERT, PROXY_SERVICE_CONFIG) and
dashboard-cm (FEATURE_ATHENA_DEBUG_MODE_ENABLE) flags. Placeholders used
for environment-specific values.
…t chart

Reframe the AI Debug / Ask Devtron Expert setup to deploy athena-mcp-engine,
athena-api-server, and athena-worker-engine as independent applications
(plus Redis), with per-service env configuration. The public ai-agent chart
is the older single-service (Holmes) agent and does not run these services.
Config verified against the staging deployment; env-specific and secret
values shown as placeholders.
…tecture

Rework the Devtron Intelligence configuration to the current Athena
architecture: deploy athena-mcp-engine, athena-api-server, and
athena-worker-engine as independent services plus Redis, and set the
orchestrator-cm (FEATURE_ASK_DEVTRON_EXPERT, PROXY_SERVICE_CONFIG) and
dashboard-cm (FEATURE_AI_INTEGRATION_ENABLE, FEATURE_ATHENA_DEBUG_MODE_ENABLE)
flags. Removes the superseded standalone ai-agent (Holmes) chart steps and
the CLUSTER_CHAT_CONFIG mechanism. Capabilities and Results sections retained.
Pending DevOps verification of the GA deployment topology.
Replace the placeholder worker-engine note with its verified env vars
(DEVTRON_WORKER_ENGINE_SERVICE_AUTH_TOKEN, DEVTRON_MCP_API_ENDPOINT,
LLM_MODEL_ID/TEMPERATURE, Postgres, and optional MAX_CONCURRENT_RECOMMENDATION_TASKS,
MAX_REACT_AGENT_ITERATIONS, SUPPORTED_UPDATE_WORKLOAD_KINDS), sourced from
the worker_engine component config.

Keep the following limitations in mind when using GitOps deployments via FluxCD:

* **Supported deployment strategies**: Only the `Deployment` and `Rollout` strategies are supported (with the latest chart versions). Other strategies (such as Canary or Blue-Green) are currently not supported.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why so? this information seems incorrect @mayank-devtron

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes it is incorrect. removed


* **Supported deployment strategies**: Only the `Deployment` and `Rollout` strategies are supported (with the latest chart versions). Other strategies (such as Canary or Blue-Green) are currently not supported.

* **No rollback**: Rolling back a FluxCD deployment to a previous version from within Devtron is not currently supported.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

kuch bhi

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

removed the incorrect info


:::caution Who Can Perform This Action?
User must have permissions to:
* Deploy Helm Apps (with environment access)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This complete document needs to be updated based on Athena installation

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

currently the doc assumes we are deploying athena microservices separtely. i have already pinged @akshatsinha007 .will update doc once helm chart is prepared by devops team


* **Event tracking** — Watches events across Kubernetes resources in the cluster, so you can observe and act on what is happening to your workloads.

* **Resource caching** — Caches Kubernetes resources in the target cluster, reducing Kubernetes API fetch times when you browse resources in the **Resource Browser**. This capability is controlled per cluster by the `enableResourceList` flag (see [Update ConfigMap](#4-update-configmap)).

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

resource watcher is dependent on scoop

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added this

@@ -0,0 +1,104 @@
# Migrate GitOps Provider (API) <a href="https://devtron.ai/pricing"><img src="https://devtron-public-asset.s3.us-east-2.amazonaws.com/images/elements/EnterpriseTag.svg" className="enterprise-badge-img" /></a>

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please review this @Ash-exp I'm not sure on this

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

will get it review from asu

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.

2 participants