-
Notifications
You must be signed in to change notification settings - Fork 2
Expand file tree
/
Copy pathnginx_ingress_example.yaml
More file actions
308 lines (289 loc) · 6.57 KB
/
Copy pathnginx_ingress_example.yaml
File metadata and controls
308 lines (289 loc) · 6.57 KB
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
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
# Example: Using ZeroSSL Issuer with NGINX Ingress Controller
# This example demonstrates how to automatically obtain ZeroSSL certificates
# for NGINX ingress resources using cert-manager annotations
---
# Step 1: Create the ZeroSSL API key secret
apiVersion: v1
kind: Secret
metadata:
name: zerossl-api-key
namespace: default
type: Opaque
stringData:
api-key: "your-zerossl-api-key-here"
---
# Step 2: Create Route53 credentials secret (for DNS validation)
apiVersion: v1
kind: Secret
metadata:
name: route53-credentials
namespace: default
type: Opaque
stringData:
secret: "your-aws-secret-access-key-here"
---
# Step 3: Create the ZeroSSL Issuer with DNS solver
apiVersion: zerossl.cert-manager.io/v1alpha1
kind: Issuer
metadata:
name: zerossl-issuer
namespace: default
spec:
apiKeySecretRef:
name: zerossl-api-key
key: api-key
validityDays: 90
strictDomains: true
solvers:
- dns01:
route53:
accessKeyID: AKIAEXAMPLE123456789
hostedZoneID: Z2E9THH2A4HU6P
region: us-east-1
secretAccessKeySecretRef:
key: secret
name: route53-credentials
selector:
dnsZones:
- example.com
---
# Example 1: Basic NGINX Ingress with ZeroSSL certificate
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: app-ingress
namespace: default
annotations:
# Enable cert-manager to automatically create certificates
cert-manager.io/issuer: "zerossl-issuer"
cert-manager.io/issuer-kind: "Issuer"
cert-manager.io/issuer-group: "zerossl.cert-manager.io"
# NGINX Ingress Controller annotations
kubernetes.io/ingress.class: "nginx"
nginx.ingress.kubernetes.io/ssl-redirect: "true"
nginx.ingress.kubernetes.io/force-ssl-redirect: "true"
spec:
tls:
- hosts:
- app.example.com
- api.example.com
secretName: app-tls-certificate
rules:
- host: app.example.com
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: app-service
port:
number: 80
- host: api.example.com
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: api-service
port:
number: 80
---
# Example 2: Wildcard certificate with NGINX Ingress (single domain only)
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: wildcard-ingress
namespace: default
annotations:
# Use ZeroSSL issuer for wildcard certificates (requires DNS validation)
cert-manager.io/issuer: "zerossl-issuer"
cert-manager.io/issuer-kind: "Issuer"
cert-manager.io/issuer-group: "zerossl.cert-manager.io"
# NGINX Ingress Controller annotations
kubernetes.io/ingress.class: "nginx"
nginx.ingress.kubernetes.io/ssl-redirect: "true"
nginx.ingress.kubernetes.io/force-ssl-redirect: "true"
# Optional: Custom certificate duration
cert-manager.io/duration: "2160h" # 90 days
cert-manager.io/renew-before: "720h" # 30 days before expiry
spec:
tls:
- hosts:
- "*.example.com" # ZeroSSL wildcard certificates must be single domain only
secretName: wildcard-tls-certificate
rules:
- host: admin.example.com
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: admin-service
port:
number: 80
- host: blog.example.com
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: blog-service
port:
number: 80
- host: api.example.com
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: api-service
port:
number: 80
---
# Example 3: Multiple domains with custom configuration
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: multi-domain-ingress
namespace: default
annotations:
# ZeroSSL issuer configuration
cert-manager.io/issuer: "zerossl-issuer"
cert-manager.io/issuer-kind: "Issuer"
cert-manager.io/issuer-group: "zerossl.cert-manager.io"
# NGINX Ingress Controller annotations
kubernetes.io/ingress.class: "nginx"
nginx.ingress.kubernetes.io/ssl-redirect: "true"
nginx.ingress.kubernetes.io/force-ssl-redirect: "true"
# Advanced NGINX configurations
nginx.ingress.kubernetes.io/proxy-body-size: "50m"
nginx.ingress.kubernetes.io/proxy-connect-timeout: "30"
nginx.ingress.kubernetes.io/proxy-send-timeout: "30"
nginx.ingress.kubernetes.io/proxy-read-timeout: "30"
# Custom SSL configuration
nginx.ingress.kubernetes.io/ssl-protocols: "TLSv1.2 TLSv1.3"
nginx.ingress.kubernetes.io/ssl-ciphers: "ECDHE-RSA-AES128-GCM-SHA256,ECDHE-RSA-AES256-GCM-SHA384"
spec:
tls:
- hosts:
- shop.example.com
- checkout.example.com
secretName: shop-tls-certificate
rules:
- host: shop.example.com
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: shop-frontend
port:
number: 80
- host: checkout.example.com
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: checkout-service
port:
number: 80
---
# Example services (for demonstration purposes)
apiVersion: v1
kind: Service
metadata:
name: app-service
namespace: default
spec:
selector:
app: my-app
ports:
- port: 80
targetPort: 8080
type: ClusterIP
---
apiVersion: v1
kind: Service
metadata:
name: api-service
namespace: default
spec:
selector:
app: my-api
ports:
- port: 80
targetPort: 8080
type: ClusterIP
---
apiVersion: v1
kind: Service
metadata:
name: website-service
namespace: default
spec:
selector:
app: website
ports:
- port: 80
targetPort: 8080
type: ClusterIP
---
apiVersion: v1
kind: Service
metadata:
name: admin-service
namespace: default
spec:
selector:
app: admin-panel
ports:
- port: 80
targetPort: 8080
type: ClusterIP
---
apiVersion: v1
kind: Service
metadata:
name: blog-service
namespace: default
spec:
selector:
app: blog
ports:
- port: 80
targetPort: 8080
type: ClusterIP
---
apiVersion: v1
kind: Service
metadata:
name: shop-frontend
namespace: default
spec:
selector:
app: shop
ports:
- port: 80
targetPort: 8080
type: ClusterIP
---
apiVersion: v1
kind: Service
metadata:
name: checkout-service
namespace: default
spec:
selector:
app: checkout
ports:
- port: 80
targetPort: 8080
type: ClusterIP