Skip to content

Latest commit

 

History

History
576 lines (468 loc) · 25.3 KB

README.md

File metadata and controls

576 lines (468 loc) · 25.3 KB

Conjur Open Source Helm Chart

CyberArk Conjur Open Source is a powerful secrets management solution, tailored specifically to the unique infrastructure requirements of native cloud, containers, and DevOps environments. Conjur Open Source is part of the CyberArk Privileged Access Security Solution which is widely used by enterprises across the globe.

GitHub release pipeline status

Github commits (since latest release)

Table of Contents

Prerequisites and Guidelines

  • Installation to an isolated Kubernetes cluster or namespace is highly recommended in order to facilitate limiting of direct access to Conjur Kubernetes resources to security administrators. Here, the term isolated refers to:
    • No workloads besides Conjur and its backend database running in the Kubernetes cluster/namespace.
    • Kubernetes and Helm access to the cluster/namespace is limited to security administrators via Role-Based Access Control (RBAC).
  • Kubernetes 1.7+
  • OCP 4.6
  • Helm v3+. The chart may work with older versions of Helm but that deployment isn't specifically supported.
  • It is recommended that auto-upgrades of Kubernetes version not be used in the Kubernetes platform in which Conjur is deployed. Kubernetes version upgrades should be done in concert with Conjur version upgrades to ensure compatibility between Conjur and Kubernetes.

Installing the Chart

The Chart can be installed from a GitHub release Chart tarball or by cloning this GitHub repository.

All releases: https://github.com/cyberark/conjur-oss-helm-chart/releases

Simple Install

To install Conjur with an integrated Postgres database:

$  CONJUR_NAMESPACE=<conjur-namespace>
$  kubectl create namespace "$CONJUR_NAMESPACE"
$  DATA_KEY="$(docker run --rm cyberark/conjur data-key generate)"
$  HELM_RELEASE=<helm-release>
$  VERSION=<conjur-oss-version>
$  helm install \
   -n "$CONJUR_NAMESPACE" \
   --set dataKey="$DATA_KEY" \
   "$HELM_RELEASE" \
   https://github.com/cyberark/conjur-oss-helm-chart/releases/download/v$VERSION/conjur-oss-$VERSION.tgz

Note: The configured data key will be used to encrypt sensitive information in Conjur's database. This must be archived in a safe place.

Note: These commands require Helm v3+ as-written. If using Helm v2, use arguments --name conjur-oss in place of conjur-oss.

_Note: It is highly recommended that custom, signed SSL certificates be used rather than using auto-generated certificates for external Conjur access and for integrated Postgres database access (see Custom Installation below).

Conjur is running HTTPS on port 443 (9443 within the cluster) with a self-signed certificate. A PostgreSQL deployment is created to store Conjur state.

Note that you can also install from source by cloning this repository and running:

$  CONJUR_NAMESPACE=<conjur-namespace>
$  kubectl create namespace "$CONJUR_NAMESPACE"
$  DATA_KEY="$(docker run --rm cyberark/conjur data-key generate)"
$  HELM_RELEASE=<helm-release>
$  helm install \
   -n "$CONJUR_NAMESPACE" \
   --set dataKey="$DATA_KEY" \
   "$HELM_RELEASE" \
   ./conjur-oss

Installation on OCP

To install Conjur on OCP, use the openshift.enabled=true value, and use images for Conjur, NGINX, and Postgres that are appropriate for an OpenShift platform. The following Helm install example includes the default values for Conjur, NGINX, Postgres images for deploying on OpenShift:

$  CONJUR_NAMESPACE=<conjur-namespace>
$  oc create namespace "$CONJUR_NAMESPACE"
$  DATA_KEY="$(docker run --rm cyberark/conjur data-key generate)"
$  HELM_RELEASE=<helm-release>
$  helm install \
   -n "$CONJUR_NAMESPACE" \
   --set image.repository=registry.connect.redhat.com/cyberark/conjur \
   --set image.tag=latest \
   --set nginx.image.repository=registry.connect.redhat.com/cyberark/conjur-nginx \
   --set nginx.image.tag=latest \
   --set postgres.image.repository=registry.redhat.io/rhel8/postgresql-15 \
   --set postgres.image.tag=latest \
   --set openshift.enabled=true \
   --set dataKey="$DATA_KEY" \
   "$HELM_RELEASE" \
   https://github.com/cyberark/conjur-oss-helm-chart/releases/download/v<VERSION>/conjur-oss-<VERSION>.tgz

Custom Installation

All important chart values can be customized. The table in the Configuration section below describes customizable chart values.

Values can be customized either by:

Note: When using non-default values for Helm install or upgrade, the user is advised:

  • Setting configurable parameters to non-default values may result in a combination of settings that may not have been tested.
  • Using component images other than the defaults may introduce security vulnerabilities.

Note: It is recommended that any custom chart values that are sensitive in nature should be set on the Helm command line rather than in a custom values file (to avoid the risk of the custom values file not getting deleted after use). An example of how to do this for database.url is shown below.

Example: Installation Using Command Line Arguments

The following shows how to install a Conjur deployment with:

  • A specific version of Conjur
  • A custom domain name to use for accessing Conjur from outside of the cluster
$  CONJUR_NAMESPACE=my-conjur-namespace
$  kubectl create namespace "$CONJUR_NAMESPACE"
$  DATA_KEY="$(docker run --rm cyberark/conjur data-key generate)"
$  HELM_ARGS="--set dataKey=$DATA_KEY \
              --set image.tag=1.11.0 \
              --set image.pullPolicy=IfNotPresent \
              --set ssl.hostname=custom.domainname.com
$  helm install \
   -n "$CONJUR_NAMESPACE" \
   $HELM_ARGS \
   conjur-oss \
   https://github.com/cyberark/conjur-oss-helm-chart/releases/download/v<VERSION>/conjur-oss-<VERSION>.tgz

Example: Installation Using Custom YAML File

The following shows how to install a Conjur deployment with:

  • A specific version of Conjur
  • Additional Kubernetes-API authenticators enabled
  • A custom domain name to use for accessing Conjur from outside of the cluster

First, create a custom values file:

$  DATA_KEY="$(docker run --rm cyberark/conjur data-key generate)"
$  cat >custom-values.yaml <<EOT
authenticators: "authn-k8s/minikube,authn"
dataKey: $DATA_KEY

image:
  tag: "1.11.0"
  pullPolicy: IfNotPresent

ssl:
  hostname: custom.domainname.com
EOT

Next, deploy Conjur using the custom-values.yaml file as follows:

$  CONJUR_NAMESPACE=my-conjur-namespace
$  kubectl create namespace "$CONJUR_NAMESPACE"
$  helm install \
   -n "$CONJUR_NAMESPACE" \
   -f custom-values.yaml \
   conjur-oss \
   https://github.com/cyberark/conjur-oss-helm-chart/releases/download/v<VERSION>/conjur-oss-<VERSION>.tgz

NOTE: If using the Kubernetes authenticator for Conjur, the account.name value (see Configuration) must match the initial Conjur account created.

Configuring Conjur Accounts

By setting account.create to true, you can direct your Conjur container to create an account during startup. To retrieve the credentials for this account, perform the following commands:

CONJUR_ACCOUNT=<conjur-account-name>
CONJUR_NAMESPACE=<conjur-namespace>
HELM_RELEASE=<helm-release>
POD_NAME=$(kubectl get pods --namespace "$CONJUR_NAMESPACE" \
            -l "app=conjur-oss,release=$HELM_RELEASE" \
            -o jsonpath="{.items[0].metadata.name}")
kubectl exec --namespace "$CONJUR_NAMESPACE" \
            "$POD_NAME" \
            --container=conjur-oss \
            -- conjurctl role retrieve-key "$CONJUR_ACCOUNT":user:admin | tail -1

Note: If you have logLevel set to debug, the tail -1 command will truncate the output. To see all output, remove this additional command from the end.

If you set account.create to false, or did not provide a value, an admin account will need to be created. To create an account, use the following commands:

CONJUR_ACCOUNT=<Name for Conjur account to be created>
POD_NAME=$(kubectl get pods --namespace "$CONJUR_NAMESPACE" \
            -l "app=conjur-oss,release=$HELM_RELEASE" \
            -o jsonpath="{.items[0].metadata.name}")
kubectl exec --namespace $CONJUR_NAMESPACE \
              $POD_NAME \
              --container=conjur-oss \
              -- conjurctl account create $CONJUR_ACCOUNT | tail -1

The credentials for this account will be provided after the account has been created. Store these in a safe location.

Installing Conjur with an External Postgres Database

You can configure Conjur to use an external (non-integrated) Postgres database by running helm install with the following command line argument (or setting the equivalent field in a custom values.yaml file):

      --set database.url=<your-database-connection-string>

The format of a Postgres database connection string is documented here.

If this chart value is not explicitly set, then an integrated Postgres database will be deployed along with Conjur.

Auto-Generated Configuration

By default, a helm install of the Conjur Open Source helm chart will include automatic generation of the following configuration:

  • Postgres database password (for integrated Postgres database only).

    Note: The database password configuration is not used when an external Postgres database is configured.

    The database password for an integrated Postgres database is automatically generated if it is not set explicitly. Alternatively, the database password can be set explicitly by including the following helm install command line argument (or by setting the equivalent field in a custom values.yaml file):

        --set database.password=<your-database-password>

  • Postgres database SSL certificate and key (for integrated Postgres database only).

    Alternatively, these values can be set explicitly with the following helm install arguments (or by setting the equivalent field in a custom values.yaml file):

        --set database.ssl.cert=<your-database-ssl-cert>
    --set database.ssl.key=<your-database-ssl-key>

  • Conjur SSL CA signing certificate and SSL self-signed certificate.

    Alternatively, these values can be set explicitly with the following helm install arguments:

        --set ssl.caCert=<your-ssl-CA-cert>
    --set ssl.caKey=<your-ssl-CA-key>
    --set ssl.cert=<your-ssl-cert>
    --set ssl.key=<your-ssl-key>

Upgrading, Modifying, or Migrating a Conjur Open Source Helm Deployment

This Helm chart supports modifications or upgrades of a Conjur deployment via the helm upgrade command. This includes tasks such as rotating SSL certificates.

For details on how to upgrade or modify an existing Conjur Open Source Helm deployment, or migrate Conjur configuration from on Conjur Open Source Helm deployment to a new, separate Conjur Open Source Helm deployment, please see the UPGRADING.md markdown file.

Modifying environment variables for an existing Conjur Open Source Helm Deployment

After deploying the Conjur Open Source using the helm chart, you may need to add or modify an environment variable within the Conjur container. This task can be performed without needing to tear down your existing deployment by using the helm upgrade command.

Example: Changing Log Level

For example, to change the log-level of the Conjur container in your deployment, run the following:

$  CONJUR_NAMESPACE="<conjur-namespace>"
$  HELM_RELEASE="conjur-oss"
$  LOG_LEVEL="<info, debug, etc.>
$  helm upgrade \
   -n "$CONJUR_NAMESPACE" \
   --reuse-values \
   --set logLevel="$LOG_LEVEL" \
   "$HELM_RELEASE" \
   ./conjur-oss

Configuration

The following table lists the configurable parameters of the Conjur Open Source chart and their default values.

Parameter Description Default
account.name Name of the Conjur account to be used by the Kubernetes authenticator "default"
account.create If true, a Conjur account is created automatically after installation false
authenticators List of authenticators that Conjur will whitelist and load. "authn"
conjurLabels Extra Kubernetes labels to apply to Conjur resources {}
database.url PostgreSQL connection string. The format is documented here. If left blank, an integrated PostgreSQL deployment is created. ""
database.password PostgreSQL database password string. Unused if an external Postgres database is configured. See PostgreSQL Database Password Restrictions below. ""
database.ssl.Cert PostgreSQL TLS x509 certificate, base64 encoded. ""
database.ssl.key PostgreSQL TLS private key, base64 encoded. ""
dataKey Conjur data key, 32 byte base-64 encoded string for data encryption. ""
deployment.annotations Annotations for Conjur deployment {}
image.repository Conjur Docker image repository "cyberark/conjur"
image.tag Conjur Docker image tag "1.11.5"
image.pullPolicy Pull policy for Conjur Docker image "Always"
logLevel Conjur log level. Set to 'debug' to enable detailed debug logs in the Conjur container "info"
nginx.image.repository NGINX Docker image repository "nginx"
nginx.image.tag NGINX Docker image tag "1.15"
nginx.image.pullPolicy Pull policy for NGINX Docker image "IfNotPresent"
openshift.enabled Indicates that Conjur is to be installed on an OpenShift platform false
postgres.image.pullPolicy Pull policy for postgres Docker image "IfNotPresent"
postgres.image.repository postgres Docker image repository "postgres"
postgres.image.tag postgres Docker image tag "10.16"
postgres.persistentVolume.create Create a peristent volume to back the PostgreSQL data true
postgres.persistentVolume.size Size of persistent volume to be created for PostgreSQL "8Gi"
postgres.persistentVolume.storageClass Storage class to be used for PostgreSQL persistent volume claim nil
rbac.create Controls whether or not RBAC resources are created. This setting is deprecated and will be replaced in the next major release with two separate settings: rbac.createClusterRole (defaulting to true) and rbac.createClusterRoleBinding (defaulting to false), and the creation of RoleBindings will be recommended over relying on this ClusterRoleBinding. true
replicaCount Number of desired Conjur pods 1
service.external.annotations Annotations for the external LoadBalancer [service.beta.kubernetes.io/aws-load-balancer-backend-protocol: tcp]
service.external.enabled Expose service to the Internet true
service.external.port Conjur external service port 443
service.internal.annotations Annotations for Conjur service {}
service.internal.port Conjur internal service port 443
service.internal.type Conjur internal service type (ClusterIP and NodePort supported) "NodePort"
serviceAccount.create Controls whether or not a service account is created true
serviceAccount.name Name of the ServiceAccount to be used by access-controlled resources created by the chart nil
ssl.altNames Subject Alt Names for generated Conjur certificate and ingress []
ssl.expiration Expiration limit for generated certificates 365
ssl.hostname Hostname and Common Name for generated certificate and ingress "conjur.myorg.com"
postgresLabels Extra Kubernetes labels to apply to Conjur PostgreSQL resources {}

Deploying Without Persistent Volume Support (e.g. for MiniKube, KataCoda)

Some Kubernetes platforms (e.g. MiniKube and KataCoda) do not have out-of-the-box support for StorageClasses or PersistentVolumes. If you are Helm installing a Conjur cluster on such a platform, then it is possible to install the cluster without persistent storage of Conjur secrets configuration and data by using the following chart setting:

--set postgres.persistentVolume.create=false

Using this flag means that your Conjur policies and secrets will not be stored persistently across pod resets, so this is intended to be used for experimentation, exploration, or automated testing, and is not intended to be used in production environments.

Deploying Without LoadBalancer Support (e.g. for KinD, MiniKube, KataCoda)

Some Kubernetes platforms (e.g. Kubernetes-in-Docker [KinD], MiniKube and KataCoda) do not have out-of-the-box support for LoadBalancers.

For such platforms, one workaround for this is to install a software load balancer add-on, such as MetalLB, and assign a pool of routed IPs for the software load balancer to use as external IPs. Configuring such a software load balancer is considered out-of-scope here. Please refer to the MetalLB documentation for details.

An alternative to using a software load balancer would be to install the Conjur cluster without LoadBalancer support by using the following chart setting:

--set service.external.enabled=false

Using this flag will result in a Conjur deployment that uses services of type NodePort rather then LoadBalancer.

Debugging

To display additional debugging information for the Conjur container, you can set the logLevel value to debug.

To change this value without needing to re-deploy or modify your configuration, perform the following steps:

  1. Run helm upgrade to change the current debug value
$  CONJUR_NAMESPACE="<conjur-namespace>"
$  HELM_RELEASE="conjur-oss"
$  LOG_LEVEL="debug"
$  helm upgrade \
   -n "$CONJUR_NAMESPACE" \
   --reuse-values \
   --set logLevel="$LOG_LEVEL" \
   "$HELM_RELEASE" \
   ./conjur-oss
  1. (Optional) Retrieve the ID of the Conjur container
$ POD_NAME=$(kubectl get pods \
                    --namespace $CONJUR_NAMESPACE \
                    -l "app=conjur-oss,release=conjur-oss" \
                    -o jsonpath="{.items[0].metadata.name}")
  1. Access logs for your Conjur container
$ kubectl logs $POD_NAME conjur-oss
  • (Optional) Use -f to follow logs
$ kubectl logs -f $POD_NAME conjur-oss

PostgreSQL Database Password Restrictions

The following restrictions apply to the PostgreSQL database password:

  • Password must only contain the following:
    • Digits (0-9)
    • Letters (A-Z,a-z)
    • The special characters: ["-", ".", "_", or "~"]
  • Password length must be less than or equal to 64 characters.

What's Next? Deploy an Example Application That Uses Conjur Secrets

If you are new to Conjur, you may be interested in learning more about how Conjur security policy can be configured and an application can be deployed that uses Conjur Open Source to safely manage secrets data.

This repository contains a set of scripts that can:

Please refer to the README.md file in the ../examples/kubernetes-in-docker directory for more details on how to run these demo scripts.

These scripts will also generate some application-specific Conjur policy YAML files and Kubernetes application manifests as concrete examples of how applications can be deployed that use Conjur Kubernetes authentication to safely retrieve secrets.

Deleting the Conjur Deployment

Uninstalling or deleting a Conjur deployment involves two steps:

  • Running helm delete to delete Kubernetes resources that are managed directly by Helm as part of the Conjur Helm release.
  • Using kubectl delete to delete Kubernetes secrets that are associated with the Conjur release, but are not managed directly by Helm.

Uninstalling the Chart via Helm Delete

To uninstall/delete resources that are associated with a Conjur deployment that are directly managed by Helm, use helm delete:

    $  CONJUR_NAMESPACE="<conjur-namespace>"
    $  HELM_RELEASE="conjur-oss"
    $  helm delete -n "$CONJUR_NAMESPACE" "$HELM_RELEASE"

Cleaning Up Kubernetes Secrets Not Managed by Helm

Following a helm delete of a Conjur deployment, there may be some residual Kubernetes secrets that have not been deleted. This will happen whenever secrets are created for "auto-generated" Conjur configuration. Such secrets are decorated with a "pre-install" Helm hook annotation, essentially making these secrets "self-managed" from a Helm perspective. The benefit to having these secrets become "self-managed" is that it prevents loss of that configuration as a result of helm upgrade operations. The downside is that those secrets are no longer cleaned up as part of helm delete.

The Kubernetes secrets that may need to be manually deleted following helm delete are:

Secret Name Description When is Manual Deletion Required?
<helm-release>-conjur-database-password Database Password When created (i.e. database URL not explicitly set)
<helm-release>-conjur-database-ssl Database SSL Certificate When auto-generated (i.e. not explicitly set)
<helm-release>-conjur-database-url Database URL When auto-generated (i.e. not explicitly set)
<helm-release>-conjur-data-key Data encryption key Always
<helm-release>-conjur-ssl-ca-cert Conjur SSL CA Certificate When auto-generated (i.e. not explicitly set)
<helm-release>-conjur-ssl-cert Conjur SSL Access Certificate When auto-generated (i.e. not explicitly set)

To delete the residual "self-managed" Kubernetes secrets associated with the Conjur deployment, run the following:

$  CONJUR_NAMESPACE="<conjur-namespace>"
$  HELM_RELEASE="conjur-oss"
$  kubectl delete secrets -n "$CONJUR_NAMESPACE" --selector="release=$HELM_RELEASE"

Contributing

This chart is maintained at github.com/cyberark/conjur-oss-helm-chart.