Skip to content

Conversation

@bimakw
Copy link
Contributor

@bimakw bimakw commented Dec 18, 2025

Description

This PR adds comprehensive documentation for all environment variables used by Camel K, as requested in #6414.

Changes

  • Added new documentation page docs/modules/ROOT/pages/configuration/env-vars.adoc
  • Updated navigation to include the new page

Environment Variables Documented

Operator

  • WATCH_NAMESPACE, NAMESPACE, POD_NAME
  • KAMEL_OPERATOR_ID / OPERATOR_ID
  • KAMEL_BASE_IMAGE / RELATED_IMAGE_BASE
  • CAMEL_K_SYNTHETIC_INTEGRATIONS
  • LOG_LEVEL
  • KAMELET_CATALOG_DIR

Proxy

  • HTTP_PROXY, HTTPS_PROXY, NO_PROXY

Maven

  • MAVEN_CMD, MAVEN_WRAPPER, MAVEN_OPTS

CLI

  • KUBECONFIG, KAMEL_CONFIG_NAME, KAMEL_CONFIG_PATH
  • GITHUB_TOKEN

Build

  • DOCKER_CONFIG, JAVA_HOME

Runtime

  • CAMEL_K_OPERATOR_ID, CAMEL_K_VERSION, CAMEL_K_INTEGRATION
  • CAMEL_K_RUNTIME_VERSION, CAMEL_K_MOUNT_PATH_*
  • CAMEL_K_CONF, CAMEL_K_CONF_D, CAMEL_K_DIGEST

How to Test

  1. Build documentation locally
  2. Navigate to Configuration > Environment Variables
  3. Verify all sections render correctly

Fixes #6414

Document all environment variables used by the Camel K operator, CLI,
and runtime. This includes operator settings, proxy configuration,
Maven options, and runtime environment variables.

Fixes apache#6414
Copy link
Contributor

@squakez squakez left a comment

Choose a reason for hiding this comment

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

Nice work, thanks! We need to remove certain parts, but the operator section is good!

** xref:configuration/runtime-config.adoc[Runtime configuration]
** xref:configuration/runtime-resources.adoc[Runtime resources]
** xref:configuration/runtime-version.adoc[Camel version]
** xref:configuration/env-vars.adoc[Environment Variables]
Copy link
Contributor

Choose a reason for hiding this comment

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

I think this one belongs more to installation>advanced and we can name it Operator Tuning

Copy link
Contributor

Choose a reason for hiding this comment

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

Even better. Don't add a new page. Put this content instead as a paragraph in the operator tuning page: https://camel.apache.org/camel-k/next/installation/advanced/advanced.html

[[env-vars]]
= Environment Variables

The Camel K operator and CLI can be configured using environment variables. This page documents all the environment variables that can be used to customize the behavior of Camel K components.
Copy link
Contributor

Choose a reason for hiding this comment

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

This is operator only, we should remove the CLI.


|`WATCH_NAMESPACE`
|_required_
|The namespace(s) the operator watches for Integration resources. Required for operator startup.
Copy link
Contributor

Choose a reason for hiding this comment

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

Add a note telling that when missing, the operator is watching all namespaces.

|===
|Variable |Default |Description

|`MAVEN_CMD`
Copy link
Contributor

Choose a reason for hiding this comment

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

This one should be omitted. The existence of the command is exclusively for unit test.

|Additional JVM options passed to Maven during builds.
|===

[[cli-env-vars]]
Copy link
Contributor

Choose a reason for hiding this comment

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

Let's remove these one and focus only on the operator.

|===

[[build-env-vars]]
== Build Environment Variables
Copy link
Contributor

Choose a reason for hiding this comment

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

These one should not be configured by the user. Please, remove.

|Path to the Java installation. Used for keystore operations during builds.
|===

[[runtime-env-vars]]
Copy link
Contributor

Choose a reason for hiding this comment

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

Please, remove this section. Those env vars are controlled typically by traits instead.

value: "true"
----

=== For Integrations
Copy link
Contributor

Choose a reason for hiding this comment

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

Remove this section. The goal is the operator tuning.

- Rename page to 'Operator Tuning' and move to installation/advanced
- Remove CLI, Proxy, Maven, Build, Runtime sections per reviewer feedback
- Focus documentation on operator-specific environment variables only
- Add note that WATCH_NAMESPACE defaults to watching all namespaces
@bimakw
Copy link
Contributor Author

bimakw commented Dec 18, 2025

Thanks @squakez for the detailed review! I've addressed all the feedback:

  • Renamed to 'Operator Tuning' and moved to installation/advanced
  • Removed CLI, Proxy, Maven, Build, and Runtime sections - now focused only on operator-specific environment variables
  • Added note that WATCH_NAMESPACE defaults to watching all namespaces when not set

Please let me know if there's anything else that needs adjustment!

Per reviewer feedback, instead of creating a new page, add the operator
environment variables documentation as a section in the existing
fine-tuning page (advanced.adoc).
@bimakw
Copy link
Contributor Author

bimakw commented Dec 18, 2025

Updated! Instead of creating a new page, I've added the environment variables section directly to the existing advanced.adoc page as suggested.

@squakez
Copy link
Contributor

squakez commented Dec 19, 2025

Good work! That page will serve in the future to include any new env var introduced in the operator. Thanks!

@squakez squakez merged commit 18239ed into apache:main Dec 19, 2025
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.

Document env var configurations

2 participants