04f9d37a7f
The in-cluster RGW only listens on plain HTTP via a ClusterIP, so S3 clients outside the cluster cannot reach it. TLS terminates in beast to avoid proxy body-size and timeout limits on large uploads. - add a vault-issuer Certificate covering the existing radosgw SANs, rgw.k8s.syd1.au.unkin.net and 198.18.200.11 - mount the cert and enable beast ssl_port 7443, keeping 7480 for probes - add rgw-external LoadBalancer on 198.18.200.11:443 with externalTrafficPolicy Local Part of #582 Reviewed-on: #584 Co-authored-by: unkin-agent <unkin-agent@unkin.net> Co-committed-by: unkin-agent <unkin-agent@unkin.net>
27 lines
539 B
YAML
27 lines
539 B
YAML
---
|
|
apiVersion: cert-manager.io/v1
|
|
kind: Certificate
|
|
metadata:
|
|
name: rgw-tls
|
|
namespace: ceph-system
|
|
labels:
|
|
app.kubernetes.io/name: rgw
|
|
spec:
|
|
secretName: rgw-tls
|
|
issuerRef:
|
|
kind: ClusterIssuer
|
|
name: vault-issuer
|
|
commonName: s3.ceph.unkin.net
|
|
dnsNames:
|
|
- s3.ceph.unkin.net
|
|
- rgw.k8s.syd1.au.unkin.net
|
|
- radosgw.service.consul
|
|
- radosgw.query.consul
|
|
- radosgw.service.au-syd1.consul
|
|
- radosgw.main.unkin.net
|
|
ipAddresses:
|
|
- 198.18.200.11
|
|
privateKey:
|
|
algorithm: RSA
|
|
size: 4096
|