The Kubernetes Orchestrator allows for the remote management of certificate stores defined in a Kubernetes cluster. The following types of Kubernetes resources are supported:
- Secrets - Kubernetes secrets of type
kubernetes.io/tlsorOpaque - Certificates - Kubernetes certificates of type
certificates.k8s.io/v1
This repository contains a Universal Orchestrator Extension which is a plugin to the Keyfactor Universal Orchestrator. Within the Keyfactor Platform, Orchestrators are used to manage “certificate stores” — collections of certificates and roots of trust that are found within and used by various applications.
The Universal Orchestrator is part of the Keyfactor software distribution and is available via the Keyfactor customer portal. For general instructions on installing Extensions, see the “Keyfactor Command Orchestrator Installation and Configuration Guide” section of the Keyfactor documentation. For configuration details of this specific Extension see below in this readme.
The Universal Orchestrator is the successor to the Windows Orchestrator. This Orchestrator Extension plugin only works with the Universal Orchestrator and does not work with the Windows Orchestrator.
Kubernetes Orchestrator Extension is supported by Keyfactor for Keyfactor customers. If you have a support issue, please open a support ticket via the Keyfactor Support Portal at https://support.keyfactor.com
To report a problem or suggest a new feature, use the Issues tab. If you want to contribute actual bug fixes or proposed enhancements, use the Pull requests tab.
The minimum version of the Keyfactor Universal Orchestrator Framework needed to run this version of the extension is 10.x
The Keyfactor Universal Orchestrator may be installed on either Windows or Linux based platforms. The certificate operations supported by a capability may vary based what platform the capability is installed on. The table below indicates what capabilities are supported based on which platform the encompassing Universal Orchestrator is running.
| Operation | Win | Linux |
|---|---|---|
| Supports Management Add | ✓ | ✓ |
| Supports Management Remove | ✓ | ✓ |
| Supports Create Store | ✓ | ✓ |
| Supports Discovery | ✓ | ✓ |
| Supports Reenrollment | ||
| Supports Inventory | ✓ | ✓ |
This orchestrator extension has the ability to connect to a variety of supported PAM providers to allow for the retrieval of various client hosted secrets right from the orchestrator server itself. This eliminates the need to set up the PAM integration on Keyfactor Command which may be in an environment that the client does not want to have access to their PAM provider.
The secrets that this orchestrator extension supports for use with a PAM Provider are:
| Name | Description |
|---|---|
| ServerUsername | Must be set to kubeconfig if used. If you do not set it to kubeconfig the ServerPassword will be ignored. |
| ServerPassword | Must be set if ServerUsername is provided. The service account credentials for the Universal Orchestrator to use. Must be in kubeconfig format. For more information review Kubernetes service account docs and scripts. |
It is not necessary to use a PAM Provider for all of the secrets available above. If a PAM Provider should not be used, simply enter in the actual value to be used, as normal.
If a PAM Provider will be used for one of the fields above, start by referencing the Keyfactor Integration Catalog. The GitHub repo for the PAM Provider to be used contains important information such as the format of the json needed. What follows is an example but does not reflect the json values for all PAM Providers as they have different "instance" and "initialization" parameter names and values.
General PAM Provider Configuration
To use a PAM Provider to resolve a field, in this example the Server Password will be resolved by the Hashicorp-Vault provider, first install the PAM Provider extension from the Keyfactor Integration Catalog on the Universal Orchestrator.
Next, complete configuration of the PAM Provider on the UO by editing the manifest.json of the PAM Provider (e.g. located at extensions/Hashicorp-Vault/manifest.json). The "initialization" parameters need to be entered here:
"Keyfactor:PAMProviders:Hashicorp-Vault:InitializationInfo": {
"Host": "http://127.0.0.1:8200",
"Path": "v1/secret/data",
"Token": "xxxxxx"
}After these values are entered, the Orchestrator needs to be restarted to pick up the configuration. Now the PAM Provider can be used on other Orchestrator Extensions.
With the PAM Provider configured as an extenion on the UO, a json object can be passed instead of an actual value to resolve the field with a PAM Provider. Consult the Keyfactor Integration Catalog for the specific format of the json object.
To have the Server Password field resolved by the Hashicorp-Vault provider, the corresponding json object from the Hashicorp-Vault extension needs to be copied and filed in with the correct information:
{"Secret":"my-kv-secret","Key":"myServerPassword"}This text would be entered in as the value for the Server Password, instead of entering in the actual password. The Orchestrator will attempt to use the PAM Provider to retrieve the Server Password. If PAM should not be used, just directly enter in the value for the field.
- Keyfactor Version Supported
- Platform Specific Notes
- PAM Integration
- Overview
- Versioning
- Security Considerations
- Kubernetes Orchestrator Extension Installation
- Certificate Store Types
- Creating Certificate Stores and Scheduling Discovery Jobs
- Certificate Discovery
- Certificate Inventory
- Certificate Management
- Development
- License
The minimum version of the Keyfactor Universal Orchestrator Framework needed to run this version of the extension is 10.1
| Keyfactor Version | Universal Orchestrator Framework Version | Supported |
|---|---|---|
| 10.2.1 | 10.1, 10.2 | ✓ |
| 10.1.1 | 10.1, 10.2 | ✓ |
| 10.0.0 | 10.1, 10.2 | ✓ |
| 9.10.1 | Not supported on KF 9.X.X | x |
| 9.5.0 | Not supported on KF 9.X.X | x |
The Keyfactor Universal Orchestrator may be installed on either Windows or Linux based platforms. The certificate operations supported by a capability may vary based what platform the capability is installed on. See the store type specific sections below for more details on specific cababilities based on Kubernetes resource type.
This orchestrator extension has the ability to connect to a variety of supported PAM providers to allow for the retrieval of various client hosted secrets right from the orchestrator server itself. This eliminates the need to set up the PAM integration on Keyfactor Command which may be in an environment that the client does not want to have access to their PAM provider.
The secrets that this orchestrator extension supports for use with a PAM Provider are:
| Name | Description |
|---|---|
| ServerPassword | This is a raw JSON file that contains service account credentials to interact with the Kubernetes APIs. See the service account setup guide for permission details. |
| ServerUsername | This is a static value that must be set to kubeconfig. |
It is not necessary to implement all of the secrets available to be managed by a PAM provider.
For each value that you want managed by a PAM provider, simply enter the key value inside your
specific PAM provider that will hold this value into the corresponding field when setting up
the certificate store, discovery job, or API call.
Setting up a PAM provider for use involves adding an additional section to the manifest.json file for this extension as well as setting up the PAM provider you will be using. Each of these steps is specific to the PAM provider you will use and are documented in the specific GitHub repo for that provider. For a list of Keyfactor supported PAM providers, please reference the Keyfactor Integration Catalog.
The Kubernetes Orchestrator Extension is an integration that can remotely manage certificate resources in a Kubernetes cluster. The certificate store types that can be managed in the current version are:
- K8SCert - Kubernetes certificates of type
certificates.k8s.io/v1 - K8SSecret - Kubernetes secrets of type
Opaque - K8STLSSecret - Kubernetes secrets of type
kubernetes.io/tls - K8SCluster - This allows for a single store to manage a k8s cluster's secrets or type
Opaqueandkubernetes.io/tls. This can be thought of as a container ofK8SSecretandK8STLSSecretstores across all k8s namespaces. - K8SNS - This allows for a single store to manage a k8s namespace's secrets or type
Opaqueandkubernetes.io/tls. This can be thought of as a container ofK8SSecretandK8STLSSecretstores for a single k8s namespace. - K8SJKS - Kubernetes secrets of type
Opaquethat contain one or more Java Keystore(s). These cannot be managed at the cluster or namespace level as they should all require unique credentials. - K8SPKCS12 - Kubernetes secrets of type
Opaquethat contain one or more PKCS12(s). These cannot be managed at the cluster or namespace level as they should all require unique credentials.
This orchestrator extension makes use of the Kubernetes API by using a service account to communicate remotely with certificate stores. The service account must have the correct permissions in order to perform the desired operations. For more information on the required permissions, see the service account setup guide.
The K8SCert store type is used to manage Kubernetes certificates of type certificates.k8s.io/v1.
To provision these certs use the k8s-csr-signer
documentation for more information.
The K8SSecret store type is used to manage Kubernetes secrets of type Opaque. These secrets can have any
arbitrary fields, but except for the tls.crt and tls.key fields, these are reserved for the kubernetes.io/tls
secret type.
NOTE: The orchestrator will only manage the fields named certificates and private_keys in the
secret. Any other fields will be ignored.
The K8STLSSecret store type is used to manage Kubernetes secrets of type kubernetes.io/tls. These secrets
must have the tls.crt and tls.key fields and may only contain a single key and single certificate.
The K8SJKS store type is used to manage Kubernetes secrets of type Opaque. These secrets
must have a field that ends in .jks. The orchestrator will inventory and manage using a custom alias of the following
pattern: <k8s_secret_field_name>/<keystore_alias>. For example, if the secret has a field named mykeystore.jks and
the keystore contains a certificate with an alias of mycert, the orchestrator will manage the certificate using the
alias mykeystore.jks/mycert.
The K8SPKCS12 store type is used to manage Kubernetes secrets of type Opaque. These secrets
must have a field that ends in .p12, .pkcs12, .pfx. The orchestrator will inventory and manage using a
custom alias of the following pattern: <k8s_secret_field_name>/<keystore_alias>. For example, if the secret has a
field named mykeystore.p12 and the keystore contains a certificate with an alias of mycert, the orchestrator will
manage the certificate using the alias mykeystore.p12/mycert.
The version number of a the Kubernetes Orchestrator Extension can be verified by right clicking on the
Kyefactor.Orchestrators.K8S.dll file in the <path>/<to>/<orchstrator install>/Extensions/Kubernetes installation folder,
selecting Properties, and then clicking on the Details tab.
For the Kubernetes Orchestrator Extension to be able to communicate with a Kubernetes cluster, it must be able to authenticate with the cluster. This is done by providing the extension with a service account token that has the appropriate permissions to perform the desired operations. The service account token can be provided to the extension in one of two ways:
- As a raw JSON file that contains the service account credentials
- As a base64 encoded string that contains the service account credentials
To set up a service account user on your Kubernetes cluster to be used by the Kubernetes Orchestrator Extension, use the following example as a guide:
apiVersion: v1
kind: ServiceAccount
metadata:
name: keyfactor
namespace: keyfactor
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
name: keyfactor
rules:
- apiGroups: ["certificates.k8s.io"]
resources: ["certificatesigningrequests"]
verbs: ["create", "get", "list", "watch", "update", "patch", "delete"]
- apiGroups: [""]
resources: ["secrets"]
verbs: ["create", "get", "list", "watch", "update", "patch", "delete"]
- apiGroups: [""]
resources: ["namespaces"]
verbs: ["get", "list", "watch"]
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
name: keyfactor
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: keyfactor
subjects:
- kind: ServiceAccount
name: keyfactor
namespace: keyfactor- Create the certificate store types you wish to manage. Please refer to the individual sections devoted to each supported store type under "Certificate Store Types" later in this README.
- Stop the Keyfactor Universal Orchestrator Service for the orchestrator you plan to install this extension to run on.
- In the Keyfactor Orchestrator installation folder (by convention usually C:\Program Files\Keyfactor\Keyfactor Orchestrator), find the "Extensions" folder. Underneath that, create a new folder named "Kubernetes". You may choose to use a different name if you wish.
- Download the latest version of the Kubernetes orchestrator extension from GitHub. Click on the "Latest" release link on the right hand side of the main page and download the first zip file.
- Copy the contents of the download installation zip file to the folder created in Step 3.
- (Optional) If you decide to create one or more certificate store types with short names different than the suggested values (please see the individual certificate store type sections in "Certificate Store Types" later in this README for more information regarding certificate store types), edit the manifest.json file in the folder you created in step 3, and modify each "ShortName" in each "Certstores.{ShortName}.{Operation}" line with the ShortName you used to create the respective certificate store type. If you created it with the suggested values, this step can be skipped.
- Modify the config.json file (See the "Configuration File Setup" section later in this README)
- Start the Keyfactor Universal Orchestrator Service.
- Create the certificate store types you wish to manage. Please refer to the individual sections devoted to each supported store type under Certificate Store Types later in this README.
- (Optional) Run certificate discovery jobs to populate the certificate stores with existing certificates. See the Certificate Store Discovery section later in this README for more information.
When setting up the certificate store types you wish the Kubernetes Orchestrator Extension to
manage, there are some common settings that will be the same for all supported types.
To create a new Certificate Store Type in Keyfactor Command, first click on settings
(the gear icon on the top right) => Certificate Store Types => Add. Alternatively,
there are cURL scripts for all of the currently implemented certificate store types
in the Certificate Store Type cURL Scripts folder in this repo if you wish to automate
the creation of the desired store types.
Below is a table of the common values that should be used for all certificate store types.
A Keyfactor Command certificate store StorePath for the K8S orchestrator extension can follow the following formats:
| Pattern | Description |
|---|---|
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. |
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. |
clusterName/namespace/secretName |
Same as above, clusterName is purely informational |
clusterName/namespace/secretType/secretName |
Considered a full path, this is what discovery will return as StorePath |
| Field Name | Required | Description | Value |
|---|---|---|---|
| Name | ✓ | The display name you wish to use for the new Certificate Store Type. | Depends on store type. |
| ShortName | ✓ | The short name you wish to use for the new Certificate Store Type. | Depends on store type. |
| Custom Capability | ✓ | Whether or not the certificate store type supports custom capabilities. | Checked [x] |
| Supported Job Types | ✓ | The job types supported by the certificate store type. | Depends on store type. |
| Needs Server | ✓ | Must be set to true or checked. NOTE: If using this ServerUsername must be equal to kubeconfig and ServerPassword will be the kubeconfig file in JSON format |
Checked [x] |
| Blueprint Allowed | Checked if you wish to make use of blueprinting. Please refer to the Keyfactor Command Reference Guide for more details on this feature. | Unchecked [ ] | |
| Uses PowerShell | Whether or not the certificate store type uses PowerShell. | Unchecked [ ] | |
| Requires Store Password | Whether or not the certificate store type requires a password. | Unchecked [ ] | |
| Supports Entry Password | Whether or not the certificate store type supports entry passwords. | Unchecked [ ] |
| Field Name | Required | Description | Value |
|---|---|---|---|
| Store Path Type | The type of path the certificate store type uses. | Freeform | |
| Supports Custom Alias | Whether or not the certificate store type supports custom aliases. | Depends on store type. | |
| Private Key Handling | Whether or not the certificate store type supports private key handling. | Depends on store type. | |
| PFX Password Style | The password style used by the certificate store type. | Default |
| Name | Display Name | Type | Required | Default Value | Description |
|---|---|---|---|---|---|
| KubeNamespace | Kube Namespace | String | This field overrides implied Store Path value. The Kubernetes namespace the store will reside. This will override the value parsed from storepath. |
||
| KubeSecretName | Kube Secret Name | String | This field overrides implied Store Path value. The Kubernetes secret or certificate resource name. |
||
| KubeSecretType | Kube Secret Type | String | ✓ | Must be one of the following secret, secret_tls or cert. See kube-secret-types. |
|
| IncludeCertChain | Include Certificate Chain | Bool | true |
Will default to true if not set. Set this to false if you do not want certificate chains deployed. |
|
| SeparateChain | SeparateChain | Bool | false |
Will default to false if not set. Set this to true if you want to deploy certificate chain to the ca.crt field for Opaque and tls secrets. |
secret- A generic secret of typeOpaque. Must contain a key of one of the following values: [cert,certficate,certs,certificates] to be inventoried.tls_secret- A secret of typekubernetes.io/tls. Must contain the following keys: [tls.crt,tls.key] to be inventoried.cert- A certificatecertificates.k8s.io/v1resource. Must contain the following keys: [csr,cert] to be inventoried.
- See specific certificate store type instructions below
The following commands can be used with kfutil. Please refer to the kfutil documentation for more information on how to use the tool to interact w/ Keyfactor Command. kfuti
kfutil login
kfutil store-types create --name K8SSecret| Field Name | Required | Value |
|---|---|---|
| Name | ✓ | K8SSecret |
| ShortName | ✓ | K8SSecret |
| Custom Capability | ✓ | Checked [x] + K8SSecret |
| Supported Job Types | ✓ | Inventory, Add, Remove, Create, Discovery |
| Needs Server | ✓ | Checked [x] |
| Blueprint Allowed | Unchecked [ ] | |
| Uses PowerShell | Unchecked [ ] | |
| Requires Store Password | Unchecked [ ] | |
| Supports Entry Password | Unchecked [ ] |
NOTE: If using PAM, server_username must be equal to kubeconfig and server_password will be the kubeconfig file in JSON format.
| Field Name | Value |
|---|---|
| Store Path Type | Freeform |
| Supports Custom Alias | Forbidden |
| Private Key Handling | Optional |
| PFX Password Style | Default |
| Name | Display Name | Type | Required | Default Value | Description |
|---|---|---|---|---|---|
| KubeNamespace | Kube Namespace | String | default |
The K8S namespace the Opaque secret lives. This will override any value inferred in the Store Path |
|
| KubeSecretName | Kube Secret Name | String | ✓ | The name of the K8S Opaque secret. This will override any value inferred in the Store Path |
|
| KubeSecretType | Kube Secret Type | String | ✓ | secret |
|
| IncludeCertChain | Include Certificate Chain | Bool | true |
Will default to true if not set. If set to false only leaf cert will be deployed. |
|
| SeparateChain | SeparateChain | Bool | false |
Will default to false if not set. true will deploy leaf cert to tls.crt and the rest of the cert chain to ca.crt. If set to false the full chain is deployed to tls.crt |
Empty
The following commands can be used with kfutil. Please refer to the kfutil documentation for more information on how to use the tool to interact w/ Keyfactor Command.
kfutil login
kfutil store-types create --name K8STLSSecr| Field Name | Required | Value |
|---|---|---|
| Name | ✓ | K8STLSSecr |
| ShortName | ✓ | K8STLSSecr |
| Custom Capability | ✓ | Checked [x] + K8STLSSecr |
| Supported Job Types | ✓ | Inventory, Add, Remove, Create, Discovery |
| Needs Server | ✓ | Checked [x] |
| Blueprint Allowed | Unchecked [ ] | |
| Uses PowerShell | Unchecked [ ] | |
| Requires Store Password | Unchecked [ ] | |
| Supports Entry Password | Unchecked [ ] |
| Field Name | Required | Value |
|---|---|---|
| Store Path Type | Freeform | |
| Supports Custom Alias | Forbidden | |
| Private Key Handling | Optional | |
| PFX Password Style | Default |
| Name | Display Name | Type | Required | Default Value | Description |
|---|---|---|---|---|---|
| KubeNamespace | Kube Namespace | String | The K8S namespace the tls secret lives. This will override any value inferred in the Store Path |
||
| KubeSecretName | Kube Secret Name | String | The name of the K8S tls secret. This will override any value inferred in the Store Path |
||
| KubeSecretType | Kube Secret Type | String | ✓ | tls_secret |
|
| IncludeCertChain | Include Certificate Chain | Bool | true |
If set to false only leaf cert will be deployed. |
|
| SeparateChain | SeparateChain | Bool | true |
true will deploy leaf cert to tls.crt and the rest of the cert chain to ca.crt. If set to false the full chain is deployed to tls.crt |
Empty
The following commands can be used with kfutil. Please refer to the kfutil documentation for more information on how to use the tool to interact w/ Keyfactor Command.
kfutil login
kfutil store-types create --name K8SPKCS12| Field Name | Required | Value |
|---|---|---|
| Name | ✓ | K8SPKCS12 |
| ShortName | ✓ | K8SPKCS12 |
| Custom Capability | ✓ | Checked [x] + K8SPKCS12 |
| Supported Job Types | ✓ | Inventory, Add, Remove, Create, Discovery |
| Needs Server | ✓ | Checked [x] |
| Blueprint Allowed | Unchecked [ ] | |
| Uses PowerShell | Unchecked [ ] | |
| Requires Store Password** | Unchecked [ ] | |
| Supports Entry Password | Unchecked [ ] |
NOTE: Requires Store Password is required if pkcs12 password is not being sourced from a separate secret in the
K8S cluster.
| Field Name | Value |
|---|---|
| Store Path Type | Freeform |
| Supports Custom Alias | Required |
| Private Key Handling | Optional |
| PFX Password Style | Default |
| Name | Display Name | Type | Required | Default Value | Description |
|---|---|---|---|---|---|
| KubeNamespace | Kube Namespace | String | K8S namespace the PKCS12 secret lives. This will override any value inferred in the Store Path |
||
| KubeSecretName | Kube Secret Name | String | The K8S secret name that contains PKCS12 data. This will override any value inferred in the Store Path |
||
| KubeSecretType | Kube Secret Type | String | ✓ | pkcs12 |
This must be set to pkcs12. |
| CertificateDataFieldName | Certificate Data Field Name | String | ✓ | .p12 |
The K8S secret field name to source the PKCS12 data from. You can provide an extension .p12 or .pfx for a secret with a key example.p12 |
| PasswordFieldName | Password Field Name | String | password |
If sourcing the PKCS12 password from a K8S secret this is the field it will look for the password in. | |
| PasswordIsK8SSecret | Password Is K8S Secret | Bool | false |
If you want to use the PKCS12 secret or a separate secret specific in KubeSecretPasswordPath set this to true |
|
| StorePasswordPath | Kube Secret Password Path | String | Source PKCS12 password from a separate K8S secret. Pattern: namespace_name/secret_name |
Empty
namespace_name/secret_namenamespace_name/secrets/secret_namecluster_name/namespace_name/secrets/secret_name
k8s_secret_field_name/keystore_alias
The following commands can be used with kfutil. Please refer to the kfutil documentation for more information on how to use the tool to interact w/ Keyfactor Command.
kfutil login
kfutil store-types create --name K8SJKS| Field Name | Required | Value |
|---|---|---|
| Name | ✓ | K8SJKS |
| ShortName | ✓ | K8SJKS |
| Custom Capability | ✓ | Checked [x] + K8SJKS |
| Supported Job Types | ✓ | Inventory, Add, Remove, Create, Discovery |
| Needs Server | ✓ | Checked [x] |
| Blueprint Allowed | Unchecked [ ] | |
| Uses PowerShell | Unchecked [ ] | |
| Requires Store Password** | Unchecked [ ] | |
| Supports Entry Password | Unchecked [ ] |
NOTE: Requires Store Password is required if pkcs12 password is not being sourced from a separate secret in the
K8S cluster.
| Field Name | Value |
|---|---|
| Store Path Type | Freeform |
| Supports Custom Alias | Required |
| Private Key Handling | Optional |
| PFX Password Style | Default |
| Name | Display Name | Type | Required | Default Value | Description |
|---|---|---|---|---|---|
| KubeNamespace | Kube Namespace | String | K8S namespace the JKS secret lives. This will override any value inferred in the Store Path. |
||
| KubeSecretName | Kube Secret Name | String | The K8S secret name that contains JKS data. This will override any value inferred in the Store Path. |
||
| KubeSecretType | Kube Secret Type | String | ✓ | jks |
|
| CertificateDataFieldName | Certificate Data Field Name | String | ✓ | .jks |
The K8S secret field name to source the JKS data from |
| PasswordFieldName | Password Field Name | String | ✓ | password |
If sourcing the JKS password from a K8S secret this is the field it will look for the password in. |
| PasswordIsK8SSecret | Password Is K8S Secret | Bool | false |
If you want to use the JKS secret or a separate secret specific in `` set this to true |
|
| StorePasswordPath | Kube Secret Password Path | String | Source JKS password from a separate K8S secret. Pattern: namespace_name/secret_name |
Empty
cluster_name
namespace_name/secrets/secret_type/secret_name
The following commands can be used with kfutil. Please refer to the kfutil documentation for more information on how to use the tool to interact w/ Keyfactor Command.
kfutil login
kfutil store-types create --name K8SCluster| Field Name | Required | Value |
|---|---|---|
| Name | ✓ | K8SCluster |
| ShortName | ✓ | K8SCluster |
| Custom Capability | ✓ | Checked [x] + K8SCluster |
| Supported Job Types | ✓ | Inventory, Add, Remove, Create |
| Needs Server | ✓ | Checked [x] |
| Blueprint Allowed | Unchecked [ ] | |
| Uses PowerShell | Unchecked [ ] | |
| Requires Store Password | Unchecked [ ] | |
| Supports Entry Password | Unchecked [ ] |
| Field Name | Value |
|---|---|
| Store Path Type | Freeform |
| Supports Custom Alias | Required |
| Private Key Handling | Optional |
| PFX Password Style | Default |
| Name | Display Name | Type | Required | Default Value | Description |
|---|---|---|---|---|---|
| IncludeCertChain | Include Certificate Chain | Bool | true |
Will default to true if not set. If set to false only leaf cert will be deployed. |
|
| SeparateChain | Separate Chain | Bool | false |
Will default to false if not set. Set this to true if you want to deploy certificate chain to the ca.crt field for Opaque and tls secrets. |
Empty
NOTE: This store type will only inventory K8S secrets that contain the keys tls.crt and tls.key.
namespace_namecluster_name/namespace_name
secrets/secret_type/secret_name
The following commands can be used with kfutil. Please refer to the kfutil documentation for more information on how to use the tool to interact w/ Keyfactor Command.
kfutil login
kfutil store-types create --name K8SNS| Field Name | Required | Value |
|---|---|---|
| Name | ✓ | K8SNS |
| ShortName | ✓ | K8SNS |
| Custom Capability | ✓ | Checked [x] + K8SNS |
| Supported Job Types | ✓ | Inventory, Add, Remove, Create |
| Needs Server | ✓ | Checked [x] |
| Blueprint Allowed | Unchecked [ ] | |
| Uses PowerShell | Unchecked [ ] | |
| Requires Store Password | Unchecked [ ] | |
| Supports Entry Password | Unchecked [ ] |
| Field Name | Value |
|---|---|
| Store Path Type | Freeform |
| Supports Custom Alias | Required |
| Private Key Handling | Optional |
| PFX Password Style | Default |
| Name | Display Name | Type | Required | Default Value | Description |
|---|---|---|---|---|---|
| KubeNamespace | Kube Namespace | String | K8S namespace to manage. This will override any value inferred in the Store Path. |
||
| IncludeCertChain | Include Certificate Chain | Bool | true |
Will default to true if not set. If set to false only leaf cert will be deployed. |
|
| SeparateChain | Separate Chain | Bool | false |
Will default to false if not set. Set this to true if you want to deploy certificate chain to the ca.crt field for Opaque and tls secrets. |
Empty
The following commands can be used with kfutil. Please refer to the kfutil documentation for more information on how to use the tool to interact w/ Keyfactor Command.
kfutil login
kfutil store-types create --name K8SCert| Field Name | Required | Value |
|---|---|---|
| Name | ✓ | K8SCert |
| ShortName | ✓ | K8SCert |
| Custom Capability | ✓ | Checked [x] + K8SCert |
| Supported Job Types | ✓ | Inventory, Discovery |
| Needs Server | ✓ | Checked [x] |
| Blueprint Allowed | Unchecked [ ] | |
| Uses PowerShell | Unchecked [ ] | |
| Requires Store Password | Unchecked [ ] | |
| Supports Entry Password | Unchecked [ ] |
| Field Name | Required | Value |
|---|---|---|
| Store Path Type | Freeform | |
| Supports Custom Alias | Forbidden | |
| Private Key Handling | Forbidden | |
| PFX Password Style | Default |
| Name | Display Name | Type | Required | Default Value | Description |
|---|---|---|---|---|---|
| KubeNamespace | Kube Namespace | String | The K8S namespace the cert resource lives. This will override any value inferred in the Store Path |
||
| KubeSecretName | Kube Secret Name | String | The K8S cert name. This will override any value inferred in the Store Path. |
||
| KubeSecretType | Kube Secret Type | String | ✓ | cert |
Empty
Please refer to the Keyfactor Command Reference Guide for information on creating certificate stores and scheduling Discovery jobs in Keyfactor Command.
NOTE: To use disovery jobs, you must have the story type created in Keyfactor Command and the needs_server checkbox MUST be checked.
Otherwise you will not be able to provide credentials to the discovery job.
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:
- Click on the "Locations > Certificate Stores" menu item.
- Click the "Discover" tab.
- Click the "Schedule" button.
- Configure the job based on storetype. Note the "Server Username" field must be set to
kubeconfigand the "Server Password" field is thekubeconfigformatted JSON file containing the service account credentials. See the "Service Account Setup" section earlier in this README for more information on setting up a service account.
- Click the "Save" button and wait for the Orchestrator to run the job. This may take some time depending on the number of certificates in the store and the Orchestrator's check-in schedule.
For discovery of K8SNS stores toy can use the following params to filter the certificates that will be discovered:
Directories to search- comma separated list of namespaces to search for certificates ORallto search all namespaces. This cannot be left blank.
For discovery of K8SPKCS12 and K8SJKS stores toy can use the following params to filter the certificates that will be discovered:
Directories to search- comma separated list of namespaces to search for certificates ORallto search all namespaces. This cannot be left blank.File name patterns to match- comma separated list of K8S secret keys to search for PKCS12 or JKS data. Will use the following keys by default:tls.pfx,tls.pkcs12,pfx,pkcs12,tls.jks,jks.
In order for certificates to be inventoried by the Keyfactor k8s-orchestrator, they must have specific keys and values in the Kubernetes Secret. The following table shows the required keys and values for each type of certificate store.
| Store Type | Valid Secret Keys |
|---|---|
| K8STLSSecr | tls.crt,tls.key, ca.crt |
| K8SSecret | tls.crt,tls.crts, ca.crt |
| K8SCert | cert, csr |
| K8SPKCS12 | *.pfx,*.pkcs12, *.p12 |
| K8SJKS | *.jks |
| K8SNS | tls.crt,tls.crts, ca.crt |
| K8SCluster | tls.crt,tls.crts, ca.crt |
Management add/remove/create operations will attempt to write back to the Kubernetes Secret. The following table shows the keys that the orchestrator will write back to the Kubernetes Secret for each type of certificate store.
| Store Type | Managed Secret Keys |
|---|---|
| K8STLSSecr | tls.crt,tls.key, ca.crt |
| K8SSecret | tls.crt,tls.key, ca.crt |
| K8SPKCS12 | Specified in custom field KubeSecretKey or use defaults |
| K8SJKS | Specified in custom field KubeSecretKey or use defaults |
| K8SCluster | tls.crt,tls.key |
| K8SNS | tls.crt,tls.key |
These store types are virtually the same, they only differ in what K8S secret type they create. Both store types allow
for ONLY a single certificate to be stored in the secret. This means any add job will overwrite the existing
tls.crt, tls.key, and ca.crt values in the secret. If a secret does not exist, the orchestrator will create one
with the fields tls.crt, tls.key. Additionally, if SeparateChain on the store definition is set to
true, then the field ca.crt will be populated with the certificate chain data.
NOTE: If a secret already exists and does not contain the field ca.crt, the orchestrator will NOT add the field
ca.crt to the secret, and instead will deploy a full certificate chain to the tls.crt field.
Here's what an Opaque secret looks like in the UI when it does not contain the ca.crt field NOTE the chain is
included in the tls.crt field:
Here's what an Opaque secret looks like in the UI when it does contain the ca.crt field:
It is possible to deploy a certificate without the private key from Command, and this is how it will look in the UI
NOTE the chain will only be included if Command has inventoried it:
The K8SJKS store type is a Java Key Store (JKS) that is stored in a Kubernetes Secret. The secret can contain multiple
JKS files. The orchestrator will attempt to manage the JKS files found in the secret that match the allowed_keys or
CertificateDataFieldName custom field values.
Alias pattern: <k8s_secret_field_name>/<keystore_alias>.
Example of secret containing 2 JKS stores:
Here's what this looks like in the UI:
When creating cert store type manually, that store property names and entry parameter names are case sensitive