@@ -159,10 +159,10 @@ to the `spec` like shown above, and then the user-secret will gain these additio
159
159
160
160
# # Using Selfmanager
161
161
162
- If you choose to disable cert manager during helm installation - or also if you cannot deploy cert manager on your
163
- cluster - you can use the `NiFi operator` as a self signed CA with ther `Selfmanager` feature.
162
+ If you choose to disable cert manager during helm installation - or simply if you cannot deploy cert manager on your
163
+ cluster - you can use the `NiFi operator` as a self signed CA with the `Selfmanager` feature.
164
164
165
- To do so, set the `pkiBackend` option to `selfmanager` under the `sslSecrets` attribute of `Nificluster` yaml
165
+ To do so, simply set the `pkiBackend` option to `selfmanager` under the `sslSecrets` attribute of `Nificluster` yaml
166
166
definition.
167
167
168
168
` ` ` yaml
@@ -177,15 +177,13 @@ spec:
177
177
pkiBackend: "selfmanager"
178
178
` ` `
179
179
180
- :::tip You can use the sample `Nificluster` YAML definition provided
181
- in `config/samples/tls_secured_nificluster_with_selfmanager.yaml`
180
+ :::tip
181
+ You can use the sample `Nificluster` YAML definition provided in `config/samples/tls_secured_nificluster_with_selfmanager.yaml`
182
182
:: :
183
183
184
- This will make the operator handle all certs generation, creation and deletion process without having to manually deploy
184
+ This will make the operator handle all required certs generation, creation and deletion process without having to manually deploy
185
185
anything.
186
186
187
187
:::warning
188
- ` create` and `issuerRef` will - logically - no longer have an impact on the behavior of the operator. Also, please be
189
- aware the current version of the operator do not handle the certs renewal and so all certs emitted will have a 10 years
190
- expiration delay avoiding expired certs issues.
191
- :::
188
+ ` create` and `issuerRef` will - logically - no longer have an impact on the behavior of the operator.
189
+ :: :
0 commit comments