Tigera Secure EE
- By Canonical Kubernetes
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| latest/stable | 55 | 27 Feb 2023 | |
| latest/candidate | 55 | 25 Feb 2023 | |
| latest/beta | 47 | 09 Dec 2022 | |
| latest/edge | 57 | 09 Mar 2023 | |
| 1.27/edge | 57 | 09 Mar 2023 | |
| 1.26/stable | 55 | 27 Feb 2023 | |
| 1.26/candidate | 55 | 25 Feb 2023 | |
| 1.26/beta | 47 | 09 Dec 2022 | |
| 1.26/edge | 44 | 23 Nov 2022 | |
| 1.25/stable | 45 | 01 Dec 2022 | |
| 1.25/candidate | 45 | 30 Nov 2022 | |
| 1.25/beta | 46 | 01 Dec 2022 | |
| 1.25/edge | 34 | 09 Sep 2022 | |
| 1.24/stable | 26 | 04 Aug 2022 | |
| 1.24/candidate | 26 | 02 Aug 2022 | |
| 1.24/beta | 15 | 03 May 2022 | |
| 1.24/edge | 24 | 27 Jul 2022 | |
| 1.23/beta | 5 | 22 Mar 2022 | |
| 1.23/edge | 3 | 24 Feb 2022 |
juju deploy tigera-secure-ee
You will need Juju 2.9 to be able to run this command. Learn how to upgrade to Juju 2.9.
Deploy universal operators easily with Juju, the Universal Operator Lifecycle Manager.
Platform:
22.04
20.04
Tigera Secure EE Charm
This charm will deploy Tigera Secure Enterprise Edition (EE) as a background service, and configure CNI for use with Tigera Secure EE, on any principal charm that implements the kubernetes-cni interface.
Usage
The tigera-secure-ee charm is a subordinate. This charm will require a
principal charm that implements the kubernetes-cni interface in order to
properly deploy.
Documentation for how to use this with the Charmed Distribution of Kubernetes can be found here: Using Tigera Secure EE with CDK