Skip to content

Latest commit

 

History

History
 
 

gateway

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 
 
 
 
 
 
 

Aqua Security Gateway Helm Chart

Helm chart for installation and maintenance of Aqua Container Security Platform Gateway component to support multi-cluster use-case.

Contents

Prerequisites

Container Registry Credentials

Link

Installing the Chart

Follow the steps in this section for production grade deployments. You can either clone aqua-helm git repo or you can add our helm private repository (https://helm.aquasec.com)

Installing Aqua Gateway from Github Repo

  1. Clone the GitHub repository with the charts
    git clone -b 6.5 https://github.com/aquasecurity/aqua-helm.git
    cd aqua-helm/
Edit values.yaml file in gateway directory with following details as prerequisite
  1. global.db.external.name - External database name
  2. global.db.external.host - External database public IP or endpoint URL
  3. global.db.external.port - External database port
  4. global.db.external.user - External database username
  5. global.db.external.password - External database password
  6. global.db.external.auditName - External audit database name
  7. global.db.external.auditHost - External audit database public IP or endpoint URL
  8. global.db.external.auditPort - External audit database port
  9. global.db.external.auditUser - External audit database username
  10. global.db.external.auditPassword - External audit database password
  11. console.publicIP - Aqua CSP console public IP or endpoint URL
  12. console.publicPort - Aqua CSP console public port
  // To load DB passswords from secrets:
  // change passwordFromSecret.enable to true
  // for loading DB password from secret edit passwordFromSecret.dbPasswordName  passwordFromSecret.dbPasswordName with secret name and secret key
  // for loading Audit-DB password from secret edit passwordFromSecret.dbAuditPasswordName  passwordFromSecret.dbAuditPasswordName with secret name and secret key
  // for loading PubSub DB password from secret edit passwordFromSecret.dbPubsubPasswordName  passwordFromSecret.dbPubsubPasswordName with secret name and secret key
  1. Create aqua namespace if gateway is being deployed to a new cluster.

    kubectl create namespace aqua
  2. Install Aqua

    helm upgrade --install --namespace aqua gateway ./gateway --set imageCredentials.username=<>,imageCredentials.password=<>,platform=<>

Installing Aqua Gateway from Helm Private Repository

  1. Add Aqua Helm Repository

    helm repo add aqua-helm https://helm.aquasec.com
  2. Check for available chart versions either from Changelog or by running the below command

    helm search repo aqua-helm/gateway --versions
  3. Create aqua namespace if gateway is being deployed to a new cluster.

    kubectl create namespace aqua
  4. copy the values.yaml content from Values.yaml to a file and make the respective changes values then run the following command:

    helm upgrade --install --namespace aqua gateway aqua-helm/gateway --values values.yaml --version <>

Configurable Variables

Parameter Description Default Mandatory
imageCredentials.create Set if to create new pull image secret true YES
imageCredentials.name Your Docker pull image secret name aqua-registry-secret YES
imageCredentials.repositoryUriPrefix repository uri prefix for dockerhub set docker.io registry.aquasec.com YES
imageCredentials.registry set the registry url for dockerhub set index.docker.io/v1/ registry.aquasec.com YES
imageCredentials.username Your Docker registry (DockerHub, etc.) username aqua-registry-secret YES
imageCredentials.password Your Docker registry (DockerHub, etc.) password unset YES
rbac.create To create RBAC for gateway component false YES
if gateway alone is deploying in new cluster
clusterRole.roleRef cluster role reference name for cluster rolebinding unset NO
console.publicIP Address of the server aqua-console-svc YES
console.publicPort Server endpoint Port value 443 YES
serviceAccount.name name of the ServiceAccount aqua-sa YES
headlessService create headless service for envoy true YES
global.platform Orchestration platform name (Allowed values are aks, eks, gke, openshift, tkg, tkgi, k8s, rancher, gs, k3s) unset YES
global.db.external.enabled Avoid installing a Postgres container and use an external database instead false YES
global.db.external.name PostgreSQL DB name unset YES
if db.external.enabled is set to true
global.db.external.host PostgreSQL DB hostname unset YES
if db.external.enabled is set to true
global.db.external.port PostgreSQL DB port unset YES
if db.external.enabled is set to true
global.db.external.user PostgreSQL DB username unset YES
if db.external.enabled is set to true
global.db.external.password PostgreSQL DB password unset YES
if db.external.enabled is set to true
global.db.external.auditName PostgreSQL DB audit name unset NO
global.db.external.auditHost PostgreSQL DB audit hostname unset NO
global.db.external.auditPort PostgreSQL DB audit port unset NO
global.db.external.auditUser PostgreSQL DB audit username unset NO
global.db.external.auditPassword PostgreSQL DB audit password unset NO
global.db.external.pubsubName PostgreSQL DB pubsub name unset NO
global.db.external.pubsubHost PostgreSQL DB pubsub hostname unset NO
global.db.external.pubsubPort PostgreSQL DB pubsub port unset NO
global.db.external.pubsubUser PostgreSQL DB pubsub username unset NO
global.db.external.pubsubPassword PostgreSQL DB pubsub password unset NO
global.db.passwordFromSecret.enabled Enable to load DB passwords from Secrets false YES
global.db.passwordFromSecret.dbPasswordName password secret name null NO
global.db.passwordFromSecret.dbPasswordKey password secret key null NO
global.db.passwordFromSecret.dbAuditPasswordName Audit password secret name null NO
global.db.passwordFromSecret.dbAuditPasswordKey Audit password secret key null NO
global.db.passwordFromSecret.dbPubsubPasswordName Pubsub password secret name null NO
global.db.passwordFromSecret.dbPubsubPasswordKey Pubsub password secret key null NO
global.db.ssl If require an SSL-encrypted connection to the Postgres configuration database. false NO
global.db.auditssl If require an SSL-encrypted connection to the Postgres configuration audit database. false NO
global.db.pubsubssl If require an SSL-encrypted connection to the Postgres configuration pubsub database. false NO
image.repository the docker image name to use gateway NO
image.tag The image tag to use. 6.5 NO
image.pullPolicy The kubernetes image pull policy. IfNotPresent NO
service.type k8s service type ClusterIP NO
service.loadbalancerIP can specify loadBalancerIP address for aqua-gateway in AKS platform null NO
service.annotations service annotations {} NO
service.ports array of ports settings array NO
publicIP gateway public ip aqua-gateway NO
replicaCount replica count 1 NO
resources Resource requests and limits {} NO
nodeSelector Kubernetes node selector {} NO
tolerations Kubernetes node tolerations [] NO
affinity Kubernetes node affinity {} NO
podLabels Configure pod labels {} NO
podAnnotations Kubernetes pod annotations {} NO
securityContext Set of security context for the container nil NO
pdb.minAvailable Set minimum available value for gate pod PDB 1 NO
TLS.enabled If require secure channel communication false NO
TLS.secretName certificates secret name nil YES
if gate.TLS.enabled is set to true
TLS.publicKey_fileName filename of the public key eg: aqua_gateway.crt nil YES
if gate.TLS.enabled is set to true
TLS.privateKey_fileName filename of the private key eg: aqua_gateway.key nil YES
if gate.TLS.enabled is set to true
TLS.rootCA_fileName filename of the rootCA, if using self-signed certificates eg: rootCA.crt nil NO
if gate.TLS.enabled is set to true and using self-signed certificates for TLS/mTLS
TLS.aqua_verify_enforcer change it to "1" or "0" for enabling/disabling mTLS between enforcer and gateway/envoy 0 YES
if gate.TLS.enabled is set to true
extraEnvironmentVars is a list of extra environment variables to set in the gateway deployments. {} NO
extraSecretEnvironmentVars is a list of extra environment variables to set in the gateway deployments, these variables take value from existing Secret objects. [] NO