Need to set additional `nerc.mghpcc.org/allow-unencrypted-routes: 'true'` label by default to any newly approved or already existing OpenShift allocations

[Milstein]

All OCP namespaces that want to use the letsencrypt-production-http01 cluster-issuer in their Ingress with a DNS CNAME record must include the label nerc.mghpcc.org/allow-unencrypted-routes: 'true' otherwise they will not be able to use it.

Since we have some live DNS-based Ingress running in production, we need to carefully verify and apply the nerc.mghpcc.org/allow-unencrypted-routes: 'true' label only where necessary, ensuring no duplicates while maintaining uninterrupted service.

Related to this issue

[knikolla]

@Milstein is this something you want to expose as an allocation attribute? How are users going to express their intent of adopting this?

[Milstein]

can't we do set is by default to all namespace level without showing as an allocation attribute. So any one can use external hostname to their ingress?

[knikolla]

can't we do set is by default to all namespace level without showing as an allocation attribute. So any one can use external hostname to their ingress?

Yes, we absolutely can.

[Milstein]

@knikolla Any updates on this?

[knikolla]

@QuanMPhm sorry for suddenly assigning this to you. Milson would like this to be merged in time for the next maintenance window on May 13.

@joachimweyl cc^

[morantara]

@QuanMPhm do you think this will be completed this sprint or should it be pushed to the next sprint (that includes 5/13)?

[joachimweyl]

@QuanMPhm I want to confirm that this PR is part of the May 13th maintenance and will need to be ready at the latest by then.