pragaonj / ingress-rule-updater Goto Github PK

Is your feature request related to a problem? Please describe.
Currently, when an ingress rule already exists, instead of skipping, the CLI exits (returns an error). The behavior sounds appropriate, but when it comes to deployment pipelines (like using azure pipeline), and having a task where you want to add an ingress rule, when the task throws an error because the ingress rule already exists, it fails the whole pipeline, which is not ideal.

Describe the solution you'd like
Either not return an error when the rule exists or have a flag where you can continue if path exists.

If you want, I can create a pull request to implement this feature.

Add option to use service.portName instead of service.portNumber to determine the service port.

Add option to set ingressClassName on creation of a new Ingress.

This looks like a very neat plugin I'd like to try out. It would be nice if there was a darwin arm64 build for Apple Silicon

Add a option to delete rules by host or a combination of host and path.

Add cli options to enable tls-protection on host basis.

When adding a new rule the host can be added to tls.hosts by supplying a --tls <secret-name> option.