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
@@ -230,7 +230,7 @@ must have the `tls.crt` and `tls.key` fields and may only contain a single key a
230
230
## Versioning
231
231
232
232
The version number of a the Kubernetes Orchestrator Extension can be verified by right clicking on the
233
-
`Kube.dll` file in the `<path>/<to>/<orchstrator install>/Extensions/Kubernetes` installation folder,
233
+
`Kyefactor.Orchestrators.K8S.dll` file in the `<path>/<to>/<orchstrator install>/Extensions/Kubernetes` installation folder,
234
234
selecting Properties, and then clicking on the Details tab.
235
235
236
236
## Security Considerations
@@ -305,12 +305,6 @@ subjects:
305
305
certificates. See the [Certificate Store Discovery](#certificate-store-discovery) section later in this README for more
306
306
information.
307
307
308
-
## Certificate Store Discovery
309
-
**NOTE:** To use disovery jobs, you must have the story type created in Keyfactor Command and the `needs_server` checkbox MUST be checked.
310
-
Otherwise you will not be able to provide credentials to the discovery job.
311
-
312
-
The Kubernetes Orchestrator Extension supports certificate discovery jobs. This allows you to populate the certificate stores with existing certificates. To run a discovery job, follow these steps:
313
-
314
308
## Certificate Store Types
315
309
316
310
When setting up the certificate store types you wish the Kubernetes Orchestrator Extension to
@@ -324,6 +318,16 @@ the creation of the desired store types.
324
318
### Configuration Information
325
319
Below is a table of the common values that should be used for all certificate store types.
326
320
321
+
#### Note about StorePath
322
+
A Keyfactor Command certificate store `StorePath` for the K8S orchestrator extension can follow the following formats:
| `secretName` | The name of the secret to use. This assumes `KubeNamespace` is defined or `default` and will be the `secret` or `cert` name on k8s. |
327
+
| `namespace/secretName` | If `KubeNamespace` or `KubeSecretName` are not set, then the path will be split by `/` and the values will be parsed according to the pattern. |
328
+
| `clusterName/namespace/secretName` | Same as above, clusterName is purely informational |
329
+
| `clusterName/namespace/secretType/secretName` | Considered a `full` path, this is what discovery will return as `StorePath` |
330
+
327
331
#### Common Values
328
332
##### UI Basic Tab
329
333
| Field Name | Required | Description | Value |
@@ -347,11 +351,11 @@ Below is a table of the common values that should be used for all certificate st
347
351
| PFX Password Style | | The password style used by the certificate store type. | Default |
348
352
349
353
##### Custom Fields Tab
350
-
| Name | Display Name | Type | Required | Default Value | Description |
| KubeNamespace | Kube Namespace | String | | `default` | The Kubernetes namespace the store will reside. |
353
-
| KubeSecretName | Kube Secret Name | String | | none | This field overrides `storepath` value. The Kubernetes secret or certificate resource name. |
354
-
| KubeSecretType | Kube Secret Type | String | ✓ | none | Must be one of the following `secret`, `secret_tls` or `cert`. See [kube-secret-types](#kube-secret-types). |
354
+
| Name | Display Name | Type | Required | Default Value | Description |
| KubeNamespace | Kube Namespace | String | | `default` | The Kubernetes namespace the store will reside. This will override the value parsed from `storepath`. |
357
+
| KubeSecretName | Kube Secret Name | String | | none | This field overrides `storepath` value. The Kubernetes secret or certificate resource name. |
358
+
| KubeSecretType | Kube Secret Type | String | ✓ | none | Must be one of the following `secret`, `secret_tls` or `cert`. See [kube-secret-types](#kube-secret-types). |
355
359
356
360
##### Kube Secret Types
357
361
- `secret` - A generic secret of type `Opaque`. Must contain a key of one of the following values: [ `cert`, `certficate`, `certs`,`certificates` ] to be inventoried.
@@ -517,6 +521,10 @@ Please refer to the Keyfactor Command Reference Guide for information on creatin
517
521
certificate stores and scheduling Discovery jobs in Keyfactor Command.
518
522
519
523
## Certificate Discovery
524
+
**NOTE:** To use disovery jobs, you must have the story type created in Keyfactor Command and the `needs_server` checkbox MUST be checked.
525
+
Otherwise you will not be able to provide credentials to the discovery job.
526
+
527
+
The Kubernetes Orchestrator Extension supports certificate discovery jobs. This allows you to populate the certificate stores with existing certificates. To run a discovery job, follow these steps:
520
528
1. Click on the "Locations > Certificate Stores" menu item.
0 commit comments