Skip to content

K8SPXC-1768 Updated the custom installation documentation#302

Open
nastena1606 wants to merge 4 commits intomainfrom
K8SPXC-1768-Doc-name-override-Helm
Open

K8SPXC-1768 Updated the custom installation documentation#302
nastena1606 wants to merge 4 commits intomainfrom
K8SPXC-1768-Doc-name-override-Helm

Conversation

@nastena1606
Copy link
Copy Markdown
Collaborator

Added how to override Helm release names

Added how to override Helm release names
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Updates the “custom installation” documentation to better explain how to customize both the Operator deployment and the Percona XtraDB Cluster, including guidance on overriding Helm-generated resource names.

Changes:

  • Expanded kubectl-based customization steps to reference deploy/bundle.yaml for Operator deployment configuration and deploy/cr.yaml for cluster configuration.
  • Reworked the Helm section with examples for --set vs values.yaml workflows.
  • Added a new section explaining Helm nameOverride / fullnameOverride naming behavior and a small “common values” reference table.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread docs/custom-install.md Outdated
Comment thread docs/custom-install.md Outdated
Comment thread docs/custom-install.md Outdated
Comment thread docs/custom-install.md Outdated
Comment on lines +60 to +87
```bash
helm install my-db percona/pxc-db --version {{ release }} --namespace pxc \
--set pxc.volumeSpec.resources.requests.storage=20Gi \
--set backup.enabled=false
```

**Using a `values.yaml` file**

Create a `values.yaml` file with your custom parameters and pass it to `helm install` with the `-f` or `--values` flag:

```bash
helm install my-db percona/ps-db --version {{ release }} --namespace <namespace> -f values.yaml
```

You can pass any of the Operator’s [Custom Resource options :octicons-link-external-16:](https://github.com/percona/percona-helm-charts/tree/main/charts/pxc-db#installing-the-chart) as a
`--set key=value[,key=value]` argument.
Example `values.yaml`:

The following example deploys a Percona XtraDB Cluster in the
`pxc` namespace, with disabled backups and 20 Gi storage:
``` yaml title="values.yaml"
allowUnsafeConfigurations: true
sharding:
enabled: false
pxc:
size: 3
volumeSpec:
pvc:
resources:
requests:
storage: 2Gi
backup:
Copy link

Copilot AI Apr 27, 2026

Choose a reason for hiding this comment

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

The storage override key path is inconsistent between the --set example (pxc.volumeSpec.resources.requests.storage) and the values.yaml example (pxc.volumeSpec.pvc.resources.requests.storage). Please make these consistent and ensure they match the actual Helm values schema so readers don’t copy an incorrect key.

Copilot uses AI. Check for mistakes.
Comment thread docs/custom-install.md
Comment on lines +37 to +47
3. To customize Percona XtraDB Cluster, edit the required options in the `deploy/cr.yaml` file and apply it as follows:

```bash
kubectl apply -f deploy/cr.yaml -n <namespace>
```


=== "Helm"

To install Percona XtraDB Cluster with custom parameters, use the following command:
You can install the Operator deployment and the Percona XtraDB Cluster with custom parameters using Helm. Find what options you can customize in the [Operator chart documentation :octicons-link-external-16:](https://github.com/percona/percona-helm-charts/tree/main/charts/pxc-operator#installing-the-chart) and the [Percona Server for MySQL chart documentation :octicons-link-external-16:](https://github.com/percona/percona-helm-charts/tree/main/charts/pxc-db#installing-the-chart).

You can provide custom parameters to Helm using either the `--set` flag or a `values.yaml` file. The `--set` flag is convenient for overriding a small number of parameters directly in the command line, while a `values.yaml` file is preferable when you want to manage many custom settings in one place. Both methods are fully supported by Helm and can be used as needed for your deployment.
Copy link

Copilot AI Apr 27, 2026

Choose a reason for hiding this comment

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

There are a couple of double-spaces in the prose (e.g., before deploy/cr.yaml and in “Cluster with”), which can cause awkward rendering in some Markdown processors. Please reduce to single spaces for consistency.

Copilot uses AI. Check for mistakes.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
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.

5 participants