WIP: feat(update default ingress class): score to update default ingress class to use trusted CA cert #158

wjro · 2025-09-12T20:06:14Z

wjro commented

2025-09-12 20:06:14 +00:00

built basic structure for the score to update the default ingress class in an okd cluster. Updating the default ingress to use a ca cert allows dynamically provisioning tls certificates for ingresses.
Also added quality of life function to check if a deployment exists using the k8sclient.

built basic structure for the score to update the default ingress class in an okd cluster. Updating the default ingress to use a ca cert allows dynamically provisioning tls certificates for ingresses. Also added quality of life function to check if a deployment exists using the k8sclient.

wjro added 1 commit 2025-09-12 20:06:14 +00:00

wip(update-ingress): built basic structure for the okd commands to update the default ingress to allow dynamically provisioning tls certificates for ingresses added quality of life function to check if a deployement exists using the k8sclient

Run Check Script / check (pull_request) Successful in 57s

Details

41f1bca69c

johnride commented

2025-10-21 13:51:03 +00:00

Context : private cloud

Private cloud operators will like exposing automatically ingress ressources in the internal network with the default router. This router is generally also exposed publicly, which means that all ingresses will be reachable publicly if the HOST header is correct.

I think this behavior has serious enough implications to validate with customers what behavior they like.

Context : private cloud Private cloud operators will like exposing automatically ingress ressources in the internal network with the default router. This router is generally also exposed publicly, which means that all ingresses will be reachable publicly if the HOST header is correct. I think this behavior has serious enough implications to validate with customers what behavior they like.

wjro closed this pull request

2025-10-22 15:36:47 +00:00