Skip to content
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.

Sign up for GitHub

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

K8SPSMDB-1152 Update images with multi arch support #197

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

K8SPSMDB-1152 Update images with multi arch support #197

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
03d6aa4
K8SPSMDB-1152 Update images with multi arch support
fiowro Nov 14, 2024
93bf310
fix wrong deletion
fiowro Nov 14, 2024
8f023ce
update installation instructions
fiowro Nov 14, 2024
58c3260
remove taints removal note
fiowro Nov 14, 2024
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
56 changes: 10 additions & 46 deletions docs/aks.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,66 +77,30 @@ az aks get-credentials --resource-group my-resource-group --name my-cluster-name

2. The Operator has been started, and you can deploy your MongoDB cluster:

=== "For x86_64 architecture"


``` {.bash data-prompt="$" }
$ kubectl apply -f https://raw.githubusercontent.com/percona/percona-server-mongodb-operator/v{{ release }}/deploy/cr.yaml
```

??? example "Expected output"

``` {.text .no-copy}
perconaservermongodb.psmdb.percona.com/my-cluster-name created
```

!!! note

This deploys default MongoDB cluster configuration, three mongod, three mongos, and three config server instances. Please see [deploy/cr.yaml :octicons-link-external-16:](https://raw.githubusercontent.com/percona/percona-server-mongodb-operator/v{{ release }}/deploy/cr.yaml) and [Custom Resource Options](operator.md) for the configuration options. You can clone the repository with all manifests and source code by executing the following command:
``` {.bash data-prompt="$" }
$ kubectl apply -f https://raw.githubusercontent.com/percona/percona-server-mongodb-operator/v{{ release }}/deploy/cr.yaml
```

``` {.bash data-prompt="$" }
$ git clone -b v{{ release }} https://github.com/percona/percona-server-mongodb-operator
```
??? example "Expected output"

After editing the needed options, apply your modified `deploy/cr.yaml` file as follows:
``` {.text .no-copy}
perconaservermongodb.psmdb.percona.com/my-cluster-name created
```

``` {.bash data-prompt="$" }
$ kubectl apply -f deploy/cr.yaml
```
!!! note

=== "For ARM64 architecture"

Clone the repository with all manifests and source code by executing the following command:
This deploys default MongoDB cluster configuration, three mongod, three mongos, and three config server instances. Please see [deploy/cr.yaml :octicons-link-external-16:](https://raw.githubusercontent.com/percona/percona-server-mongodb-operator/v{{ release }}/deploy/cr.yaml) and [Custom Resource Options](operator.md) for the configuration options. You can clone the repository with all manifests and source code by executing the following command:

``` {.bash data-prompt="$" }
$ git clone -b v{{ release }} https://github.com/percona/percona-server-mongodb-operator
```

Edit the `deploy/cr.yaml` configuration file: set `image` and `backup.image` Custom Resource options to special multi-architecture image versions by adding a `-multi` suffix to their tags:

```yaml
....
image: percona/percona-server-mongodb:{{ mongodb70recommended }}-multi
...
backup:
...
image: percona/percona-backup-mongodb:{{ pbmrecommended }}-multi
```

Please note, that currently [monitoring with PMM](monitoring.md) is not supported on ARM64 configurations.

After editing, apply your modified `deploy/cr.yaml` file as follows:
After editing the needed options, apply your modified `deploy/cr.yaml` file as follows:

``` {.bash data-prompt="$" }
$ kubectl apply -f deploy/cr.yaml
```

??? example "Expected output"

``` {.text .no-copy}
perconaservermongodb.psmdb.percona.com/my-cluster-name created
```

The creation process may take some time. When the process is over your
cluster will obtain the `ready` status. You can check it with the following
command:
Expand Down
152 changes: 25 additions & 127 deletions docs/eks.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,152 +56,50 @@ Also, you need to configure AWS CLI with your credentials according to the

Deploy the Operator by applying the `deploy/bundle.yaml` manifest from the Operator source tree.

=== "For x86_64 architecture"

You can apply it without downloading, [using :octicons-link-external-16:](https://kubernetes.io/docs/reference/using-api/server-side-apply/) the following command:

``` {.bash data-prompt="$" }
$ kubectl apply --server-side -f https://raw.githubusercontent.com/percona/percona-server-mongodb-operator/v{{ release }}/deploy/bundle.yaml
```

??? example "Expected output"
You can apply it without downloading, [using :octicons-link-external-16:](https://kubernetes.io/docs/reference/using-api/server-side-apply/) the following command:

``` {.text .no-copy}
customresourcedefinition.apiextensions.k8s.io/perconaservermongodbs.psmdb.percona.com serverside-applied
customresourcedefinition.apiextensions.k8s.io/perconaservermongodbbackups.psmdb.percona.com serverside-applied
customresourcedefinition.apiextensions.k8s.io/perconaservermongodbrestores.psmdb.percona.com serverside-applied
role.rbac.authorization.k8s.io/percona-server-mongodb-operator serverside-applied
serviceaccount/percona-server-mongodb-operator serverside-applied
rolebinding.rbac.authorization.k8s.io/service-account-percona-server-mongodb-operator serverside-applied
deployment.apps/percona-server-mongodb-operator serverside-applied
```

=== "For ARM64 architecture"

Clone the repository with all manifests and source code by executing the following command:
``` {.bash data-prompt="$" }
$ kubectl apply --server-side -f https://raw.githubusercontent.com/percona/percona-server-mongodb-operator/v{{ release }}/deploy/bundle.yaml
```

``` {.bash data-prompt="$" }
$ git clone -b v{{ release }} https://github.com/percona/percona-server-mongodb-operator
```
??? example "Expected output"

Edit the `deploy/bundle.yaml` file: add the following [affinity rules](constraints.md#affinity-and-anti-affinity) to the `spec` part of the `percona-server-mongodb-operator` Deployment:

```yaml hl_lines="15-23"
apiVersion: apps/v1
kind: Deployment
metadata:
name: percona-server-mongodb-operator
spec:
replicas: 1
selector:
matchLabels:
name: percona-server-mongodb-operator
template:
metadata:
labels:
name: percona-server-mongodb-operator
spec:
affinity:
nodeAffinity:
requiredDuringSchedulingIgnoredDuringExecution:
nodeSelectorTerms:
- matchExpressions:
- key: kubernetes.io/arch
operator: In
values:
- arm64
``` {.text .no-copy}
customresourcedefinition.apiextensions.k8s.io/perconaservermongodbs.psmdb.percona.com serverside-applied
customresourcedefinition.apiextensions.k8s.io/perconaservermongodbbackups.psmdb.percona.com serverside-applied
customresourcedefinition.apiextensions.k8s.io/perconaservermongodbrestores.psmdb.percona.com serverside-applied
role.rbac.authorization.k8s.io/percona-server-mongodb-operator serverside-applied
serviceaccount/percona-server-mongodb-operator serverside-applied
rolebinding.rbac.authorization.k8s.io/service-account-percona-server-mongodb-operator serverside-applied
deployment.apps/percona-server-mongodb-operator serverside-applied
```

After editing, [apply :octicons-link-external-16:](https://kubernetes.io/docs/reference/using-api/server-side-apply/) your modified `deploy/bundle.yaml` file as follows:

``` {.bash data-prompt="$" }
$ kubectl apply --server-side -f deploy/bundle.yaml
```

??? example "Expected output"

``` {.text .no-copy}
customresourcedefinition.apiextensions.k8s.io/perconaservermongodbs.psmdb.percona.com serverside-applied
customresourcedefinition.apiextensions.k8s.io/perconaservermongodbbackups.psmdb.percona.com serverside-applied
customresourcedefinition.apiextensions.k8s.io/perconaservermongodbrestores.psmdb.percona.com serverside-applied
role.rbac.authorization.k8s.io/percona-server-mongodb-operator serverside-applied
serviceaccount/percona-server-mongodb-operator serverside-applied
rolebinding.rbac.authorization.k8s.io/service-account-percona-server-mongodb-operator serverside-applied
deployment.apps/percona-server-mongodb-operator serverside-applied
```

2. The Operator has been started, and you can deploy your MongoDB cluster:

=== "For x86_64 architecture"


``` {.bash data-prompt="$" }
$ kubectl apply -f https://raw.githubusercontent.com/percona/percona-server-mongodb-operator/v{{ release }}/deploy/cr.yaml
```

??? example "Expected output"

``` {.text .no-copy}
perconaservermongodb.psmdb.percona.com/my-cluster-name created
```

!!! note

This deploys default MongoDB cluster configuration, three mongod, three mongos, and three config server instances. Please see [deploy/cr.yaml :octicons-link-external-16:](https://raw.githubusercontent.com/percona/percona-server-mongodb-operator/v{{ release }}/deploy/cr.yaml) and [Custom Resource Options](operator.md) for the configuration options. You can clone the repository with all manifests and source code by executing the following command:
``` {.bash data-prompt="$" }
$ kubectl apply -f https://raw.githubusercontent.com/percona/percona-server-mongodb-operator/v{{ release }}/deploy/cr.yaml
```

``` {.bash data-prompt="$" }
$ git clone -b v{{ release }} https://github.com/percona/percona-server-mongodb-operator
```
??? example "Expected output"

After editing the needed options, apply your modified `deploy/cr.yaml` file as follows:
``` {.text .no-copy}
perconaservermongodb.psmdb.percona.com/my-cluster-name created
```

``` {.bash data-prompt="$" }
$ kubectl apply -f deploy/cr.yaml
```
!!! note

=== "For ARM64 architecture"

Edit the `deploy/cr.yaml` file: set the following [affinity rules](constraints.md#affinity-and-anti-affinity) in **all `affinity` subsections**:

```yaml hl_lines="2-11"
....
affinity:
advanced:
nodeAffinity:
requiredDuringSchedulingIgnoredDuringExecution:
nodeSelectorTerms:
- matchExpressions:
- key: kubernetes.io/arch
operator: In
values:
- arm64
```
This deploys default MongoDB cluster configuration, three mongod, three mongos, and three config server instances. Please see [deploy/cr.yaml :octicons-link-external-16:](https://raw.githubusercontent.com/percona/percona-server-mongodb-operator/v{{ release }}/deploy/cr.yaml) and [Custom Resource Options](operator.md) for the configuration options. You can clone the repository with all manifests and source code by executing the following command:

Also, set `image` and `backup.image` Custom Resource options to special multi-architecture image versions by adding a `-multi` suffix to their tags:

```yaml
...
image: percona/percona-server-mongodb:{{ mongodb70recommended }}-multi
...
backup:
...
image: percona/percona-backup-mongodb:{{ pbmrecommended }}-multi
``` {.bash data-prompt="$" }
$ git clone -b v{{ release }} https://github.com/percona/percona-server-mongodb-operator
```

Please note, that currently [monitoring with PMM](monitoring.md) is not supported on ARM64 configurations.

After editing, apply your modified `deploy/cr.yaml` file as follows:
After editing the needed options, apply your modified `deploy/cr.yaml` file as follows:

``` {.bash data-prompt="$" }
$ kubectl apply -f deploy/cr.yaml
```

??? example "Expected output"

``` {.text .no-copy}
perconaservermongodb.psmdb.percona.com/my-cluster-name created
```

The creation process may take some time. When the process is over your
cluster will obtain the `ready` status. You can check it with the following
command:
Expand Down
Loading