Skip to content

Commit 18c0e30

Browse files
committed
Add the --server-side flag to apply commands in documentation
This commit adds the '--server-side' flag to the installation 'apply' commands in the documentation. This is done to remove the `kubectl.kubernetes.io/last-applied-configuration` from the CRD so as to avoid violating the limit on the size of `metadata.annotations`.
1 parent 1520ab0 commit 18c0e30

File tree

5 files changed

+6
-6
lines changed

5 files changed

+6
-6
lines changed

docs/content/guides/private-registries.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -100,7 +100,7 @@ patchesJson6902:
100100
You can then install PGO from the private registry using the standard installation procedure, e.g.:
101101

102102
```shell
103-
kubectl apply -k kustomize/install
103+
kubectl apply --server-side -k kustomize/install/default
104104
```
105105

106106
## Deploy a Postgres cluster from a Private Registry

docs/content/installation/kustomize.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -118,14 +118,14 @@ are deploying the operator with cluster-wide or namespace-limited permissions).
118118
To install PGO itself in cluster-wide mode, apply the kustomization file in the `default` folder:
119119

120120
```shell
121-
kubectl apply -k kustomize/install/default
121+
kubectl apply --server-side -k kustomize/install/default
122122
```
123123

124124
To install PGO itself in namespace-limited mode, apply the kustomization file in the
125125
`singlenamespace` folder:
126126

127127
```shell
128-
kubectl apply -k kustomize/install/singlenamespace
128+
kubectl apply --server-side -k kustomize/install/singlenamespace
129129
```
130130

131131
The `kustomization.yaml` files in those folders take care of applying the appropriate permissions.

docs/content/installation/upgrade.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ Then, once both the Deployment and ServiceAccount have been deleted, proceed wit
3838
by applying the new version of the Kustomize installer:
3939

4040
```bash
41-
kubectl apply -k kustomize/install/bases
41+
kubectl apply --server-side -k kustomize/install/default
4242
```
4343

4444
## Upgrading from PGO v5.0.2 and Below

docs/content/quickstart/_index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ You can install PGO, the Postgres Operator from Crunchy Data, using the command
3535

3636
```
3737
kubectl apply -k kustomize/install/namespace
38-
kubectl apply -k kustomize/install/default
38+
kubectl apply --server-side -k kustomize/install/default
3939
```
4040

4141
This will create a namespace called `postgres-operator` and create all of the objects required to deploy PGO.

docs/content/tutorial/getting-started.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ If you have not done so, please install PGO by following the [quickstart]({{< re
1010
As part of the installation, please be sure that you have done the following:
1111

1212
1. [Forked the Postgres Operator examples repository](https://github.com/CrunchyData/postgres-operator-examples/fork) and cloned it to your host machine.
13-
1. Installed PGO to the `postgres-operator` namespace. If you are inside your `postgres-operator-examples` directory, you can run the `kubectl apply -k kustomize/install` command.
13+
1. Installed PGO to the `postgres-operator` namespace. If you are inside your `postgres-operator-examples` directory, you can run the `kubectl apply --server-side -k kustomize/install/default` command.
1414

1515
Note if you are using this guide in conjunction with images from the [Crunchy Data Customer Portal](https://access.crunchydata.com), please follow the [private registries]({{< relref "guides/private-registries.md" >}}) guide for additional setup instructions.
1616

0 commit comments

Comments
 (0)