-
Notifications
You must be signed in to change notification settings - Fork 5
/
gateway-values.yaml
153 lines (139 loc) · 4.83 KB
/
gateway-values.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
## Default values for tyk-hybrid chart
## This is a YAML-formatted file.
## Declare variables to be passed into your templates.
## See Tyk Helm documentation for installation details:
## https://tyk.io/docs/tyk-cloud/environments-deployments/hybrid-gateways/#hybrid-gateways-in-a-kubernetes-cluster
## Registry for all Tyk images - https://hub.docker.com/u/tykio
# Chart name override. Truncates to 63 characters.
# Default value: tyk-hybrid.name
nameOverride: ""
# App name override. Truncates to 63 characters.
# Default value: tyk-hybrid.fullname
fullnameOverride: ""
hybrid: true
# These are your Tyk stack secrets will directly map to the following Tyk stack configuration:
secrets:
# tyk.conf node_secret
# tyk.conf secret
APISecret: CHANGEME
# If you don't want to store plaintext secrets in the Helm value file and would
# rather provide the k8s Secret externally please populate the value below
useSecretName: ""
redis:
# The addrs value will allow you to set your Redis addresses. If you are
# using a redis cluster, you can list the endpoints of the redis instances
# or use the cluster configuration endpoint.
# Default value: redis.{{ .Release.Namespace }}.svc.cluster.local:6379
# addrs:
# - redis.tyk.svc.cluster.local:6379
# This is the the DNS name of the redis as set when using Bitnami
# - tyk-redis-master.tyk.svc.cluster.local:6379
# Redis password
# If you're using Bitnami Redis chart please input your password in the field below
# pass: ""
# Enables SSL for Redis connection. Redis instance will have to support that.
# Default value: false
# useSSL: true
# The enableCluster value will allow you to indicate to Tyk whether you are running
# a Redis cluster or not.
# Default value: false
# enableCluster: true
# By default the database index is 0. Setting the database index is not
# supported with redis cluster. As such, if you have enableCluster: true,
# then this value should be omitted or explicitly set to 0.
storage:
database: 0
gateway:
# The hostname to bind the Gateway to.
hostName: tyk-gw.local
# Sharding gateway allows you to selectively load APIs to specific gateways.
# If enabled make sure you have at least one gateway that is not sharded.
# Also be sure to match API segmentation tags with the tags selected below.
sharding:
enabled: false
tags: ""
# When true, sets the gateway protocol to HTTPS.
tls: false
# For on premise MDCB setups simply change the connection string to point to
# your MDCB instance
rpc:
# On the Tyk Cloud Console find this value in the endpoints for your
# control plane deployment
connString: ""
useSSL: true
sslInsecureSkipVerify: true
# orgID of your dashboard user
rpcKey: ""
# API key of your dashboard user
apiKey: ""
# Group/cluster that this instance belongs.
# Required when running multiple isolated clusters each having their own Redis instance.
# Must be the same across all the gateways of a cluster which share a Redis.
# Must be unique per cluster.
groupId: ""
#
# For a classic cloud hybrid gateway use these settings:
#
# connString: "hybrid.cloud.tyk.io:9091"
# useSSL: true
# bindToSlugs: true
# sslInsecureSkipVerify: false
# rpcKey: ""
# apiKey: ""
kind: Deployment
replicaCount: 1
containerPort: 8080
image:
repository: tykio/tyk-gateway
tag: v4.0.0
pullPolicy: Always
service:
type: NodePort
port: 443
externalTrafficPolicy: Local
annotations: {}
# Creates an ingress object in k8s. Will require an ingress-controller and
# annotation to that ingress controller.
ingress:
enabled: false
# specify your ingress controller class name below
className: ""
annotations: {}
# kubernetes.io/ingress.class: nginx
# kubernetes.io/tls-acme: "true"
hosts:
- host: chart-example.local
paths:
- path: /
pathType: ImplementationSpecific
tls: []
# - secretName: chart-example-tls
# hosts:
# - chart-example.local
resources: {}
# We usually recommend not to specify default resources and to leave this
# as a conscious choice for the user. This also increases chances charts
# run on environments with little resources, such as Minikube. If you do
# want to specify resources, uncomment the following lines, adjust them
# as necessary, and remove the curly braces after 'resources:'.
# limits:
# cpu: 100m
# memory: 128Mi
# requests:
# cpu: 100m
# memory: 128Mi
securityContext:
runAsUser: 1000
fsGroup: 2000
nodeSelector: {}
tolerations:
- key: node-role.kubernetes.io/master
effect: NoSchedule
affinity: {}
extraEnvs: []
mounts: []
rbac: true
# deprecated - please use the rpcKey and apiKey in the gateway section
tyk_k8s:
dash_key: ""
org_id: ""