oracle / oracle/oci-cloud-controller-manager
Backend sets SSL issue
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 158
- Forks
- 108
- PR merge metrics
- No merged PRs in 30d
Description
BUG REPORT
Versions
Environment:
- Kubernetes version (use
kubectl version): client : v1.25.1 | server : v1.25.4 - OS (e.g. from /etc/os-release): Oracle-Linux-8.6-2022.12.15-0-OKE-1.25.4-543
What happened?
Installing the ingress-nginx helm chart did not create SSL Backend sets
What you expected to happen?
Backend sets to have SSL enabled with plaintext health checks
How to reproduce it (as minimally and precisely as possible)?
Install with the following annotations :
service.beta.kubernetes.io/oci-load-balancer-ssl-ports: "443"
service.beta.kubernetes.io/oci-load-balancer-tls-secret: tls-cloud
service.beta.kubernetes.io/oci-load-balancer-tls-backendset-secret: tls-cloud
Anything else we need to know?
It seems like the "oci-load-balancer-tls-backendset-secret" does not have any effect anymore.
On top of that, health checks do not function as is in http which I believe is why that was removed.
However, there now is a checkbox "Force plaintext health checks" that gets http health checks working with SSL enabled.
Would this be enough to get the "backendset-secret" annotation back working with the health check changed to have this checkbox checked if it is ?
I found another issue similar to this and was mainly wondering whether the addition of the checkbox was enough to add the support of that annotation and this checkbox again so we can have SSL enabled backend sets out of the box
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue by installing the ingress-nginx Helm chart with the listed OCI load balancer annotations and inspect the resulting backend sets and health checks. Start by tracing how the Kubernetes Service annotations are handled, then verify that the backend-set TLS annotation takes effect and that health checks remain plaintext when configured.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- cloud, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100