Skip to content
This repository was archived by the owner on Dec 13, 2023. It is now read-only.
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
24 changes: 20 additions & 4 deletions 3.10/deployment-kubernetes-deployment-resource.md
Original file line number Diff line number Diff line change
Expand Up @@ -62,30 +62,46 @@ with `<group>` where `<group>` can be any of:
- `syncmasters` for all syncmasters of a `Cluster`.
- `syncworkers` for all syncworkers of a `Cluster`.

### `spec.architectures: []string`
### `spec.architecture: []string`

This setting specifies a list of CPU architectures for the deployment.
This setting specifies a CPU architecture for the deployment.
Possible values are:

- `amd64` (default): Use processors with the x86-64 architecture.
- `arm64`: Use processors with the 64-bit ARM architecture.

The setting expects a list of strings, but you should only specify a single
list item for the architecture, except when you want to migrate from one
architecture to the other. The first list item defines the new default
architecture for the deployment that you want to migrate to.

{% hint 'tip' %}
To use the ARM architecture, you need to enable it in the operator first using
`--set "operator.architectures={amd64,arm64}"`. See
[Installation with Helm](deployment-kubernetes-usage.html#installation-with-helm).
{% endhint 'tip' %}

To let new members as well as recreated members use `arm64` nodes, modify the
To create a new deployment with `arm64` nodes, specify the architecture in the
deployment specification as follows:

```yaml
spec:
architecture:
- arm64
```

To migrate nodes of an existing deployment from `amd64` to `arm64`, modify the
deployment specification so that both architectures are listed:

```diff
spec:
architectures:
architecture:
+ - arm64
- amd64
```

This lets new members as well as recreated members use `arm64` nodes.

Then run the following command:

```bash
Expand Down
2 changes: 1 addition & 1 deletion 3.10/deployment-kubernetes-usage.md
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ helm install $URLPREFIX/kube-arangodb-<version>.tgz --set "operator.architecture
Use at least version 1.2.20 of the operator to use the ARM architecture.
{% endhint %}

Note that you need to set [`spec.architectures`](deployment-kubernetes-deployment-resource.html#specarchitectures-string)
Note that you need to set [`spec.architecture`](deployment-kubernetes-deployment-resource.html#specarchitecture-string)
in the deployment specification, too, in order to create a deployment that runs
on ARM chips.

Expand Down
24 changes: 20 additions & 4 deletions 3.11/deployment-kubernetes-deployment-resource.md
Original file line number Diff line number Diff line change
Expand Up @@ -62,30 +62,46 @@ with `<group>` where `<group>` can be any of:
- `syncmasters` for all syncmasters of a `Cluster`.
- `syncworkers` for all syncworkers of a `Cluster`.

### `spec.architectures: []string`
### `spec.architecture: []string`

This setting specifies a list of CPU architectures for the deployment.
This setting specifies a CPU architecture for the deployment.
Possible values are:

- `amd64` (default): Use processors with the x86-64 architecture.
- `arm64`: Use processors with the 64-bit ARM architecture.

The setting expects a list of strings, but you should only specify a single
list item for the architecture, except when you want to migrate from one
architecture to the other. The first list item defines the new default
architecture for the deployment that you want to migrate to.

{% hint 'tip' %}
To use the ARM architecture, you need to enable it in the operator first using
`--set "operator.architectures={amd64,arm64}"`. See
[Installation with Helm](deployment-kubernetes-usage.html#installation-with-helm).
{% endhint 'tip' %}

To let new members as well as recreated members use `arm64` nodes, modify the
To create a new deployment with `arm64` nodes, specify the architecture in the
deployment specification as follows:

```yaml
spec:
architecture:
- arm64
```

To migrate nodes of an existing deployment from `amd64` to `arm64`, modify the
deployment specification so that both architectures are listed:

```diff
spec:
architectures:
architecture:
+ - arm64
- amd64
```

This lets new members as well as recreated members use `arm64` nodes.

Then run the following command:

```bash
Expand Down
2 changes: 1 addition & 1 deletion 3.11/deployment-kubernetes-usage.md
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ helm install $URLPREFIX/kube-arangodb-<version>.tgz --set "operator.architecture
Use at least version 1.2.20 of the operator to use the ARM architecture.
{% endhint %}

Note that you need to set [`spec.architectures`](deployment-kubernetes-deployment-resource.html#specarchitectures-string)
Note that you need to set [`spec.architecture`](deployment-kubernetes-deployment-resource.html#specarchitecture-string)
in the deployment specification, too, in order to create a deployment that runs
on ARM chips.

Expand Down
24 changes: 20 additions & 4 deletions 3.8/deployment-kubernetes-deployment-resource.md
Original file line number Diff line number Diff line change
Expand Up @@ -62,30 +62,46 @@ with `<group>` where `<group>` can be any of:
- `syncmasters` for all syncmasters of a `Cluster`.
- `syncworkers` for all syncworkers of a `Cluster`.

### `spec.architectures: []string`
### `spec.architecture: []string`

This setting specifies a list of CPU architectures for the deployment.
This setting specifies a CPU architecture for the deployment.
Possible values are:

- `amd64` (default): Use processors with the x86-64 architecture.
- `arm64`: Use processors with the 64-bit ARM architecture.

The setting expects a list of strings, but you should only specify a single
list item for the architecture, except when you want to migrate from one
architecture to the other. The first list item defines the new default
architecture for the deployment that you want to migrate to.

{% hint 'tip' %}
To use the ARM architecture, you need to enable it in the operator first using
`--set "operator.architectures={amd64,arm64}"`. See
[Installation with Helm](deployment-kubernetes-usage.html#installation-with-helm).
{% endhint 'tip' %}

To let new members as well as recreated members use `arm64` nodes, modify the
To create a new deployment with `arm64` nodes, specify the architecture in the
deployment specification as follows:

```yaml
spec:
architecture:
- arm64
```

To migrate nodes of an existing deployment from `amd64` to `arm64`, modify the
deployment specification so that both architectures are listed:

```diff
spec:
architectures:
architecture:
+ - arm64
- amd64
```

This lets new members as well as recreated members use `arm64` nodes.

Then run the following command:

```bash
Expand Down
2 changes: 1 addition & 1 deletion 3.8/deployment-kubernetes-usage.md
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ helm install $URLPREFIX/kube-arangodb-<version>.tgz --set "operator.architecture
Use at least version 1.2.20 of the operator to use the ARM architecture.
{% endhint %}

Note that you need to set [`spec.architectures`](deployment-kubernetes-deployment-resource.html#specarchitectures-string)
Note that you need to set [`spec.architecture`](deployment-kubernetes-deployment-resource.html#specarchitecture-string)
in the deployment specification, too, in order to create a deployment that runs
on ARM chips.

Expand Down
24 changes: 20 additions & 4 deletions 3.9/deployment-kubernetes-deployment-resource.md
Original file line number Diff line number Diff line change
Expand Up @@ -62,30 +62,46 @@ with `<group>` where `<group>` can be any of:
- `syncmasters` for all syncmasters of a `Cluster`.
- `syncworkers` for all syncworkers of a `Cluster`.

### `spec.architectures: []string`
### `spec.architecture: []string`

This setting specifies a list of CPU architectures for the deployment.
This setting specifies a CPU architecture for the deployment.
Possible values are:

- `amd64` (default): Use processors with the x86-64 architecture.
- `arm64`: Use processors with the 64-bit ARM architecture.

The setting expects a list of strings, but you should only specify a single
list item for the architecture, except when you want to migrate from one
architecture to the other. The first list item defines the new default
architecture for the deployment that you want to migrate to.

{% hint 'tip' %}
To use the ARM architecture, you need to enable it in the operator first using
`--set "operator.architectures={amd64,arm64}"`. See
[Installation with Helm](deployment-kubernetes-usage.html#installation-with-helm).
{% endhint 'tip' %}

To let new members as well as recreated members use `arm64` nodes, modify the
To create a new deployment with `arm64` nodes, specify the architecture in the
deployment specification as follows:

```yaml
spec:
architecture:
- arm64
```

To migrate nodes of an existing deployment from `amd64` to `arm64`, modify the
deployment specification so that both architectures are listed:

```diff
spec:
architectures:
architecture:
+ - arm64
- amd64
```

This lets new members as well as recreated members use `arm64` nodes.

Then run the following command:

```bash
Expand Down
2 changes: 1 addition & 1 deletion 3.9/deployment-kubernetes-usage.md
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ helm install $URLPREFIX/kube-arangodb-<version>.tgz --set "operator.architecture
Use at least version 1.2.20 of the operator to use the ARM architecture.
{% endhint %}

Note that you need to set [`spec.architectures`](deployment-kubernetes-deployment-resource.html#specarchitectures-string)
Note that you need to set [`spec.architecture`](deployment-kubernetes-deployment-resource.html#specarchitecture-string)
in the deployment specification, too, in order to create a deployment that runs
on ARM chips.

Expand Down