You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pigsty scales from [**laptop**](https://pigsty.io/docs/setup) to [**datacenter**](https://pigsty.io/docs/deploy). Enterprise-grade. Developer-friendly. [**Get Started**](https://pigsty.io/docs/setup/install) with the latest [**v4.5.0**](https://github.com/pgsty/pigsty/releases/tag/v4.5.0):
19
+
Pigsty scales from [**laptop**](https://pigsty.io/docs/setup) to [**datacenter**](https://pigsty.io/docs/deploy). Enterprise-grade. Developer-friendly. [**Get Started**](https://pigsty.io/docs/setup/install) with the latest [**v4.4.0**](https://github.com/pgsty/pigsty/releases/tag/v4.4.0):
[**Prepare**](https://pigsty.io/docs/deploy/prepare) a fresh `x86_64` / `aarch64` node runs any [**compatible**](https://pigsty.io/docs/ref/linux)**Linux** OS Distros, then [**Install**](https://pigsty.io/docs/setup/install#install)**Pigsty** with:
87
87
@@ -121,24 +121,24 @@ pig sty deploy # run the deploy.yml playbook
121
121
<details><summary>Install with get script</summary><br>
> **Security Note**: The `files/pki/ca/` directory contains sensitive CA private key. Ensure proper backup and access control. The CA key should never be exposed or committed to version control.
@@ -152,24 +159,28 @@ files/pki/
152
159
CA key exists? CA cert exists? Action
153
160
───────────────────────────────────────
154
161
No No Create new CA key and cert
162
+
No Yes Create a new key; keep the existing cert*
155
163
Yes No Create cert using existing key
156
164
Yes Yes Reuse existing CA (no changes)
157
165
```
158
166
167
+
`*` This state produces a mismatched pair. Always provide the CA key and
168
+
certificate together.
169
+
159
170
### ca_create = false
160
171
161
172
```
162
173
CA key exists? CA cert exists? Action
163
174
───────────────────────────────────────
164
175
Yes Yes Reuse existing CA
176
+
Yes No Create cert using existing key
165
177
No * ABORT (fail the playbook)
166
-
* No ABORT (fail the playbook)
167
178
```
168
179
169
180
170
-
## Using External CA
181
+
## Using an Existing CA
171
182
172
-
To use your own enterprise or public CA:
183
+
To provide an existing CA key pair:
173
184
174
185
1. Set `ca_create: false` in your configuration:
175
186
@@ -198,7 +209,7 @@ To use your own enterprise or public CA:
198
209
199
210
## Issuing Additional Certificates
200
211
201
-
Use [`cert.yml`](../../cert.yml) to issue additional certificates with the CA:
212
+
Use `cert.yml` to issue additional certificates with the CA:
0 commit comments