bitnami/wordpress: 8443 apache configuration fails with post-quantum clients of k8s
- Dominant language
- Go Template
- Stars
- 10.4k
- Forks
- 10.3k
- Avg merge
- 5d 12h
- Merged PRs (30d)
- 14
Description
### Name and Version
bitnami/wordpres 33.0.10
### What steps will reproduce the bug?
```yaml
# FIXME: all the probes configured to http since 33.0.10 since they never come up
# this is since the check runs against 8443 and the apache server does yet not support post-quantum algos
# while k8s enforces it. Locally only curl running `curl --curves X25519:P-256:P-384 -k https://localhost:8443/wp-login.php -v`
# works, so tls 1.3 but without pq, while `curl -curves X25519:P-256:P-384 -k https://localhost:8443/wp-login.php -v` fails
# if that gets fixed, just remove the entire httpGet override for readinessProbe and startupProbe
readinessProbe:
enabled: true
httpGet:
port: http
scheme: HTTP
httpHeaders:
- name: X-Forwarded-Proto
value: https
failureThreshold: 6
startupProbe:
enabled: true
httpGet:
port: http
scheme: HTTP
httpHeaders:
- name: X-Forwarded-Proto
value: https
```
### What do you see instead?
pod never comes up since readyness/startup fails
all checks by k8s fail with
```
sl/tls alert illegal parameter
```
as culr fails with
```
TLS connect error: error:0A000417:SSL routines::ssl/tls alert illegal parameter
```
Contributor guide
Assessment
This issue has not been assessed yet.