9.0.0-0.1.0 • Published 5 years ago

@helm-charts/appscode-voyager v9.0.0-0.1.0

Weekly downloads
1
License
MIT
Repository
-
Last release
5 years ago

@helm-charts/appscode-voyager

Voyager by AppsCode - Secure HAProxy Ingress Controller for Kubernetes

FieldValue
Repository Nameappscode
Chart Namevoyager
Chart Version9.0.0
NPM Package Version0.1.0
##
## Voyager chart configuration
##
replicaCount: 1
# Docker registry containing Voyager & HAProxy images
voyager:
  registry: appscode
  repository: voyager
  tag: 9.0.0
haproxy:
  registry: appscode
  repository: haproxy
  tag: 1.9.2-9.0.0-alpine
cleaner:
  registry: appscode
  repository: kubectl
  tag: v1.11
## Optionally specify an array of imagePullSecrets.
## Secrets must be manually created in the namespace.
## ref: https://kubernetes.io/docs/concepts/containers/images/#specifying-imagepullsecrets-on-a-pod
##
# imagePullSecrets:
#   - name: myRegistryKeySecretName
## Specify a imagePullPolicy
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
##
imagePullPolicy: IfNotPresent
## Use cloud provider here.
cloudProvider:
## The path to the cloud provider configuration file. Empty string for no configuration file.
## ie. for azure use /etc/kubernetes/azure.json
cloudConfig: ''
## Installs voyager operator as critical addon
## https://kubernetes.io/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods/
criticalAddon: false
## Log level for voyager
logLevel: 3
persistence:
  enabled: false
  hostPath: /etc/kubernetes

## Annotations passed to operator pod(s).
##
annotations: {}

## Node labels for pod assignment
## Ref: https://kubernetes.io/docs/user-guide/node-selection/
##
nodeSelector:
  beta.kubernetes.io/os: linux
  beta.kubernetes.io/arch: amd64

## Tolerations for pod assignment
## Ref: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/
##
tolerations: {}

## Affinity for pod assignment
## Ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity
##
affinity: {}

## Install Default RBAC roles and bindings
rbac:
  # Specifies whether RBAC resources should be created
  create: true

serviceAccount:
  # Specifies whether a ServiceAccount should be created
  create: true
  # The name of the ServiceAccount to use.
  # If not set and create is true, a name is generated using the fullname template
  name:

# this flag can be set to 'voyager' to handle only ingress
# with annotation kubernetes.io/ingress.class=voyager.
ingressClass:

apiserver:
  # groupPriorityMinimum is the minimum priority the group should have. Please see
  # https://github.com/kubernetes/kube-aggregator/blob/release-1.9/pkg/apis/apiregistration/v1beta1/types.go#L58-L64
  # for more information on proper values of this field.
  groupPriorityMinimum: 10000
  # versionPriority is the ordering of this API inside of the group. Please see
  # https://github.com/kubernetes/kube-aggregator/blob/release-1.9/pkg/apis/apiregistration/v1beta1/types.go#L66-L70
  # for more information on proper values of this field
  versionPriority: 15
  # enableValidatingWebhook is used to configure apiserver as ValidationWebhook for Voyager CRDs
  enableValidatingWebhook: true
  # CA certificate used by main Kubernetes api server
  ca: not-ca-cert
  # If true, disables status sub resource for crds.
  # Otherwise, enables status sub resource for Kubernetes version >= 1.11 and disables for other versions.
  disableStatusSubresource: false
  # If true, bypasses validating webhook xray checks
  bypassValidatingWebhookXray: false
  # If true, uses kube-apiserver FQDN for AKS cluster to workaround https://github.com/Azure/AKS/issues/522 (default true)
  useKubeapiserverFqdnForAks: true
  # healthcheck configures the readiness and liveliness probes for the operator pod.
  healthcheck:
    enabled: true

# Send usage events to Google Analytics
enableAnalytics: true

# Customization of templates
templates:
  # name of configmap with custom templates
  cfgmap:

Voyager

Voyager by AppsCode - Secure HAProxy Ingress Controller for Kubernetes

TL;DR;

$ helm repo add appscode https://charts.appscode.com/stable/
$ helm repo update
$ helm install appscode/voyager

Introduction

This chart bootstraps an ingress controller deployment on a Kubernetes cluster using the Helm package manager.

Prerequisites

  • Kubernetes 1.8+

Installing the Chart

To install the chart with the release name my-release:

$ helm install --name my-release appscode/voyager

The command deploys Voyager Controller on the Kubernetes cluster in the default configuration. The configuration section lists the parameters that can be configured during installation.

Tip: List all releases using helm list

Uninstalling the Chart

To uninstall/delete the my-release:

$ helm delete my-release

The command removes all the Kubernetes components associated with the chart and deletes the release.

Configuration

The following tables lists the configurable parameters of the Voyager chart and their default values.

ParameterDescriptionDefault
replicaCountNumber of operator replicas to create (only 1 is supported)1
voyager.registryDocker registry used to pull Voyager imageappscode
voyager.repositoryVoyager container imagevoyager
voyager.tagVoyager container image tag9.0.0
haproxy.registryDocker registry used to pull HAProxy imageappscode
haproxy.repositoryHAProxy container imagehaproxy
haproxy.tagHAProxy container image tag1.9.2-9.0.0-alpine
cleaner.registryDocker registry used to pull Webhook cleaner imageappscode
cleaner.repositoryWebhook cleaner container imagekubectl
cleaner.tagWebhook cleaner container image tagv1.11
imagePullSecretsSpecify image pull secretsnil (does not add image pull secrets to deployed pods)
imagePullPolicyImage pull policyIfNotPresent
cloudProviderName of cloud providernil
cloudConfigPath to cloud config
criticalAddonIf true, installs Voyager operator as critical addonfalse
logLevelLog level for operator3
persistence.enabledEnable mounting cloud configfalse
persistence.hostPathHost mount path for cloud config/etc/kubernetes
affinityAffinity rules for pod assignment{}
annotationsAnnotations applied to operator pod(s){}
nodeSelectorNode labels for pod assignment{}
tolerationsTolerations used pod assignment{}
rbac.createIf true, create and use RBAC resourcestrue
serviceAccount.createIf true, create a new service accounttrue
serviceAccount.nameService account to be used. If not set and serviceAccount.create is true, a name is generated using the fullname template
ingressClassIngress class to watch for. If empty, it handles all ingress
templates.cfgmapName of configmap with custom templates
apiserver.groupPriorityMinimumThe minimum priority the group should have.10000
apiserver.versionPriorityThe ordering of this API inside of the group.15
apiserver.enableValidatingWebhookConfigure apiserver as adission webhooks for Voyager CRDstrue
apiserver.caCA certificate used by main Kubernetes api servernot-ca-cert
apiserver.disableStatusSubresourceIf true, disables status sub resource for crds. Otherwise enables based on Kubernetes versionfalse
apiserver.bypassValidatingWebhookXrayIf true, bypasses validating webhook xray checksfalse
apiserver.useKubeapiserverFqdnForAksIf true, uses kube-apiserver FQDN for AKS cluster to workaround https://github.com/Azure/AKS/issues/522true
apiserver.healthcheck.enabledEnable readiness and liveliness probestrue
enableAnalyticsSend usage events to Google Analyticstrue

Specify each parameter using the --set key=value[,key=value] argument to helm install. For example:

$ helm install --name my-release --set image.tag=v0.2.1 appscode/voyager

Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example:

$ helm install --name my-release --values values.yaml appscode/voyager

RBAC

By default the chart will not install the recommended RBAC roles and rolebindings.

You need to have the flag --authorization-mode=RBAC on the api server. See the following document for how to enable RBAC.

To determine if your cluster supports RBAC, run the the following command:

$ kubectl api-versions | grep rbac

If the output contains "beta", you may install the chart with RBAC enabled (see below).

Enable RBAC role/rolebinding creation

To enable the creation of RBAC resources (On clusters with RBAC). Do the following:

$ helm install --name my-release appscode/voyager --set rbac.create=true
9.0.0-0.1.0

5 years ago

8.0.1-0.1.0

5 years ago

8.0.0-0.1.0

5 years ago

7.4.0-0.1.0

5 years ago

7.3.0-0.1.0

5 years ago

7.2.0-0.1.0

5 years ago

7.1.1-0.1.0

5 years ago

7.1.0-0.1.0

5 years ago

7.0.0-rc.3-0.1.0

5 years ago

7.0.0-rc.2-0.1.0

5 years ago

7.0.0-rc.1-0.1.0

5 years ago

7.0.0-rc.0-0.1.0

5 years ago

7.0.0-0.1.0

5 years ago

5.0.0-0.1.0

5 years ago

3.2.3-0.1.0

5 years ago

3.2.2-0.1.0

5 years ago

3.2.1-0.1.0

5 years ago

3.2.0-0.1.0

5 years ago

3.1.0-0.1.0

5 years ago

3.0.0-0.1.0

5 years ago

2.2.0-0.1.0

5 years ago

2.1.0-0.1.0

5 years ago

2.0.0-0.1.0

5 years ago

1.2.0-0.1.0

5 years ago

1.1.0-0.1.0

5 years ago

1.0.0-0.1.0

5 years ago

0.1.0-0.1.0

5 years ago