[
https://issues.apache.org/jira/browse/IGNITE-26160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Iurii Gerzhedovich updated IGNITE-26160:
----------------------------------------
Description:
Add support for --bootstrap-config CLI option to provide node configuration as
an inline HOCON string.
Description:
Introduced a new - -bootstrap-config command-line option that allows users to
start an IGNITE 3 node with configuration passed directly as a string, instead
of relying on external config files (- -config-path). This improves
compatibility with containerized environments (e.g., Kubernetes, Docker) and
supports config-as-code and immutable infrastructure practices.
Key Points:
• --bootstrap-config accepts HOCON-formatted configuration string.
• Mutually exclusive with --config-path.
• Configuration is persisted to Vault and becomes read-only after startup.
• No file-based persistence; changes require restart with new config.
• Supports Kubernetes, Docker, and ephemeral/dev environments.
Backward Compatibility:
Existing --config-path option remains fully supported. No breaking changes.
was:
Add support for --bootstrap-config CLI option to provide node configuration as
an inline HOCON string.
Description:
Introduced a new --bootstrap-config command-line option that allows users to
start an IGNITE 3 node with configuration passed directly as a string, instead
of relying on external config files (--config-path). This improves
compatibility with containerized environments (e.g., Kubernetes, Docker) and
supports config-as-code and immutable infrastructure practices.
Key Points:
• --bootstrap-config accepts HOCON-formatted configuration string.
• Mutually exclusive with --config-path.
• Configuration is persisted to Vault and becomes read-only after startup.
• No file-based persistence; changes require restart with new config.
• Supports Kubernetes, Docker, and ephemeral/dev environments.
Backward Compatibility:
Existing --config-path option remains fully supported. No breaking changes.
> Introduce bootstrap configuration providing for containerized env
> -----------------------------------------------------------------
>
> Key: IGNITE-26160
> URL: https://issues.apache.org/jira/browse/IGNITE-26160
> Project: Ignite
> Issue Type: Improvement
> Components: configuration ai3
> Reporter: Mikhail Pochatkin
> Assignee: Mikhail Pochatkin
> Priority: Major
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Add support for --bootstrap-config CLI option to provide node configuration
> as an inline HOCON string.
> Description:
> Introduced a new - -bootstrap-config command-line option that allows users to
> start an IGNITE 3 node with configuration passed directly as a string,
> instead of relying on external config files (- -config-path). This improves
> compatibility with containerized environments (e.g., Kubernetes, Docker) and
> supports config-as-code and immutable infrastructure practices.
> Key Points:
> • --bootstrap-config accepts HOCON-formatted configuration string.
> • Mutually exclusive with --config-path.
> • Configuration is persisted to Vault and becomes read-only after startup.
> • No file-based persistence; changes require restart with new config.
> • Supports Kubernetes, Docker, and ephemeral/dev environments.
> Backward Compatibility:
> Existing --config-path option remains fully supported. No breaking changes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
