Allow configuration of nginx ingress controller

[mueller-ma]

Description

Allow configuration of default nginx certificate.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• Small minor change not affecting the Ansible Role code (GitHub Actions Workflow, Documentation etc.)

How Has This Been Tested?

I executed the role on my cluster and set rke2_ingress_nginx_default_certificate: "cert-manager/default-cert". With cert-manager I created a certificate in the secret cert-manager/default-cert.

[mueller-ma]

I updated the PR to make all values in this file configurable.

[MonolithProjects]

LGTM

[elbvdk]

I think this should be marked as a Breaking Change; if you previously used the custom manifest deployment method to deploy those nginx configuration options, this will overwrite that custom manifest.

In our case, our deployment was failing because use-forwarded-hearders: true was removed from the nginx config which caused our Rancher to get stuck in an HTTP 308 redirect loop.

[MonolithProjects]

That's a good point @elbvdk. Thanks. Will add that to the release notes

[MonolithProjects]

@elbvdk if you want to keep using custom manifest for nginx config, use release 1.34.1 where this issue is fixed (rke2_ingress_nginx_values will be used only if it's not empty)