[BUG] K8S Hardcoded cluster dns suffix

[schmittse]

What happened?

In IngressController.py the suffix cluster.local is hardcoded (line 115).
This value can be customized in a k8s cluster install so it should be editable using configuration.

How to reproduce?

Install a cluster with a custom domain suffix, any Ingress will leads to a backend not found error.

Configuration file(s) (yaml or .env)

N/A

Relevant log output

N/A

BunkerWeb version

1.5.10

What integration are you using?

Kubernetes

Linux distribution (if applicable)

Ubuntu Server 20.04

Removed private data

• I have removed all private data from the configuration file and the logs

Code of Conduct

• I agree to follow this project's Code of Conduct

[fl0ppy-d1sk]

Hello @schmittse,

Thanks for your feedback. It will be implemented in the upcoming 1.6.0 release.

Will keep you updated once it's available in 1.6.0-beta if you have time to test it.

[schmittse]

Hi,

Thanks for the feedback, I'll give 1.6.0-beta a try.
I've also started o work on some fixes of my own, i'll try to contribute.

Already noted on the 1.6.0 code, you are missing watching on ingressclass changes as multiple classes can be added after bunkerWeb install. And the "default" class has to be handled as well.

And trying to fix issue #585 on this beta branch will be a huge bonus for k8s admins.
With this, bunkerweb could be a drop-in replacement for nginxIngressController :)