Skip to content

elastic #271

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 24, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
61 changes: 45 additions & 16 deletions apps/docs/content/elasticsearch/overview.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -2,44 +2,73 @@
title: Elasticsearch
---

Deploy [Elasticsearch](https://www.elastic.co/elasticsearch) instances in Zerops with flexible scaling options, from standalone to highly available clusters.
import UnorderedList from '@site/src/components/UnorderedList';
import UnorderedCodeList from '@site/src/components/UnorderedCodeList';
import data from '@site/static/data.json';
import ResourceTable from '/src/components/ResourceTable';

## Connection
Deploy [Elasticsearch](https://www.elastic.co/elasticsearch/) instances in Zerops with flexible scaling options, from standalone nodes to highly available clusters.

## Supported Versions

Currently supported Elasticsearch versions:
<UnorderedList data={data.elasticsearch.readable}/>

Import configuration version:
<UnorderedCodeList data={data.elasticsearch.import}/>


<ResourceTable resources={{
ram: {
min: '0.25 GB',
}
}} />

## Connection Details

- **Port**: 9200
- **Protocol**: HTTP only
- **Internal Access**: `http://hostname:9200`
- **Note**: When accessing from another service within the same project, use the service hostname <!-- fixme (js) add link to generic DNS page -->
- **Internal Access**: `http://{hostname}:9200`

## Configuration
:::note
When accessing from another service within the same project, use the service hostname as the connection address.
:::

### How to install/uninstall plugins
## Configuration Options

Configure Elasticsearch plugins using a comma-separated list:
### Plugin Management

You can configure Elasticsearch plugins using a comma-separated list in your environment secrets:

```yaml
envSecrets:
PLUGINS: "analysis-icu,ingest-attachment"
```

- **Description**: Defines plugins to install at startup
**Plugin Configuration Details:**
- Defines plugins to install at service startup
- **Format**: `plugin1,plugin2,...`
- **Note**: Removing a plugin from this list triggers uninstallation on service restart
- Service automatically installs specified plugins during initialization
- Removing a plugin from this list triggers uninstallation on service restart

### How to adjust JVM heap allocation
### JVM Heap Allocation

Control JVM heap size as a percentage of container memory:
Control the JVM heap size as a percentage of container memory:

```yaml
envSecrets:
HEAP_PERCENT: "75"
```

- **Description**: Percentage of container memory allocated to JVM heap
- **Default**: 50
- **Range**: 1-100
- **Note**: To increase available memory, adjust the service's RAM allocation in scaling configuration <!-- fixme (js) add link to generic scaling page -->
- **Important**: Changes to HEAP_PERCENT require a service restart to take effect
**Heap Configuration Details:**
- Value represents the percentage of container memory allocated to JVM heap
- **Default**: 50% of available container memory
- **Valid range**: 1-100
- To increase available memory, adjust the service's RAM allocation in scaling configuration

:::note Requires Restart
Changes to HEAP_PERCENT require a service restart to take effect.
:::

## Backup

Expand Down
42 changes: 26 additions & 16 deletions apps/docs/static/llms-full.txt
Original file line number Diff line number Diff line change
Expand Up @@ -4451,33 +4451,43 @@ Have you build something that others might find useful? Don't hesitate to share

# Elasticsearch > Overview

Deploy [Elasticsearch](https://www.elastic.co/elasticsearch) instances in Zerops with flexible scaling options, from standalone to highly available clusters.
## Connection
Deploy [Elasticsearch](https://www.elastic.co/elasticsearch/) instances in Zerops with flexible scaling options, from standalone nodes to highly available clusters.
## Supported Versions
Currently supported Elasticsearch versions:
Import configuration version:
## Connection Details
- **Port**: 9200
- **Protocol**: HTTP only
- **Internal Access**: `http://hostname:9200`
- **Note**: When accessing from another service within the same project, use the service hostname
## Configuration
### How to install/uninstall plugins
Configure Elasticsearch plugins using a comma-separated list:
- **Internal Access**: `http://{hostname}:9200`
:::note
When accessing from another service within the same project, use the service hostname as the connection address.
:::
## Configuration Options
### Plugin Management
You can configure Elasticsearch plugins using a comma-separated list in your environment secrets:
```yaml
envSecrets:
PLUGINS: "analysis-icu,ingest-attachment"
```
- **Description**: Defines plugins to install at startup
**Plugin Configuration Details:**
- Defines plugins to install at service startup
- **Format**: `plugin1,plugin2,...`
- **Note**: Removing a plugin from this list triggers uninstallation on service restart
### How to adjust JVM heap allocation
Control JVM heap size as a percentage of container memory:
- Service automatically installs specified plugins during initialization
- Removing a plugin from this list triggers uninstallation on service restart
### JVM Heap Allocation
Control the JVM heap size as a percentage of container memory:
```yaml
envSecrets:
HEAP_PERCENT: "75"
```
- **Description**: Percentage of container memory allocated to JVM heap
- **Default**: 50
- **Range**: 1-100
- **Note**: To increase available memory, adjust the service's RAM allocation in scaling configuration
- **Important**: Changes to HEAP_PERCENT require a service restart to take effect
**Heap Configuration Details:**
- Value represents the percentage of container memory allocated to JVM heap
- **Default**: 50% of available container memory
- **Valid range**: 1-100
- To increase available memory, adjust the service's RAM allocation in scaling configuration
:::note Requires Restart
Changes to HEAP_PERCENT require a service restart to take effect.
:::
## Backup
Elasticsearch backups are created using `elasticdump`:
- **Format**: `.gz` (per index/component dump)
Expand Down
42 changes: 26 additions & 16 deletions apps/docs/static/llms-small.txt
Original file line number Diff line number Diff line change
Expand Up @@ -4259,33 +4259,43 @@ Have you build something that others might find useful? Don't hesitate to share

# Elasticsearch > Overview

Deploy [Elasticsearch](https://www.elastic.co/elasticsearch) instances in Zerops with flexible scaling options, from standalone to highly available clusters.
## Connection
Deploy [Elasticsearch](https://www.elastic.co/elasticsearch/) instances in Zerops with flexible scaling options, from standalone nodes to highly available clusters.
## Supported Versions
Currently supported Elasticsearch versions:
Import configuration version:
## Connection Details
- **Port**: 9200
- **Protocol**: HTTP only
- **Internal Access**: `http://hostname:9200`
- **Note**: When accessing from another service within the same project, use the service hostname
## Configuration
### How to install/uninstall plugins
Configure Elasticsearch plugins using a comma-separated list:
- **Internal Access**: `http://{hostname}:9200`
:::note
When accessing from another service within the same project, use the service hostname as the connection address.
:::
## Configuration Options
### Plugin Management
You can configure Elasticsearch plugins using a comma-separated list in your environment secrets:
```yaml
envSecrets:
PLUGINS: "analysis-icu,ingest-attachment"
```
- **Description**: Defines plugins to install at startup
**Plugin Configuration Details:**
- Defines plugins to install at service startup
- **Format**: `plugin1,plugin2,...`
- **Note**: Removing a plugin from this list triggers uninstallation on service restart
### How to adjust JVM heap allocation
Control JVM heap size as a percentage of container memory:
- Service automatically installs specified plugins during initialization
- Removing a plugin from this list triggers uninstallation on service restart
### JVM Heap Allocation
Control the JVM heap size as a percentage of container memory:
```yaml
envSecrets:
HEAP_PERCENT: "75"
```
- **Description**: Percentage of container memory allocated to JVM heap
- **Default**: 50
- **Range**: 1-100
- **Note**: To increase available memory, adjust the service's RAM allocation in scaling configuration
- **Important**: Changes to HEAP_PERCENT require a service restart to take effect
**Heap Configuration Details:**
- Value represents the percentage of container memory allocated to JVM heap
- **Default**: 50% of available container memory
- **Valid range**: 1-100
- To increase available memory, adjust the service's RAM allocation in scaling configuration
:::note Requires Restart
Changes to HEAP_PERCENT require a service restart to take effect.
:::
## Backup
Elasticsearch backups are created using `elasticdump`:
- **Format**: `.gz` (per index/component dump)
Expand Down