Kubernetes, OpenShift, and GKE

Overview

This integration enables you to securely pass secrets stored in Conjur to applications running in RedHat OpenShift, Google Kubernetes Engine (GKE), or other Kubernetes implementations. By configuring your environment to integrate with Conjur, secrets are never exposed to third parties.

The Conjur integration provides the following features for your Kubernetes environment:

  • End-to-end encryption of secrets through mutual TLS.

  • Robust authentication and authorization incorporating Conjur policy, signed certificates, and an internal Kubernetes authenticator.

  • Conjur policy provides separation of duties, letting your security teams control container access while development teams define application requirements.

  • Easy deployment of applications across environments and pods.

  • Secret rotation and centralized auditing.

 
  • This section describes both the Conjur Enterprise and Conjur Open Source integrations.
  • Unless otherwise noted, all references to Kubernetes applies to native Kubernetes as well as the OpenShift and GKE implementations of Kubernetes.
  • All references to Kubernetes namespaces intentionally includes the OpenShift concept of Project.

Requirements

Access to one of the following:

  • OpenShift environment (3.9 or higher) with an internal Docker registry.

  • GKE cluster:

    • Version 1.9 or higher is required for easy installation with Google Cloud Marketplace; version 1.10 is recommended.
    • Version 1.5 and higher are supported with Helm installation.
  • Other Kubernetes environment (1.5 or higher)

For Conjur Enterprise, you also need: 

  • A license for a Conjur cluster with a master and at least two standbys.

  • Conjur licensing for at least two followers.

  • The latest conjur-appliance Docker image from your Conjur support representative

In this section:

 
True 10.5