feat: improve how ingress annotations are handled #693
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This pull request refines how Ingress annotations managed by the FlowFuse Helm chart are handled.
The high-level logic is:
cert-manager.io/cluster-issue
r with the value ofingress.certManagerIssuer
.1a. Add other non–cert-manager annotations as provided.
2 If
ingress.certManagerIssuer
is not defined, add all annotations defined iningress.annotations
.3 Add the
spec.tls
block whenever any cert-manager annotation is present, either viaingress.certManagerIssuer
or defined viaingress.annotations
.ingress.certManagerIssuer
takes precedence over anycert-manager.io/*
annotations specified iningress.annotations
.The same logic is applied to the broker Ingress resources.
Additionally, driver configuration values has been extended by
projectIngressAnnotations
andcustomHostname.ingressAnnotations
properties.Related Issue(s)
#683
FlowFuse/driver-k8s#242
Checklist
flowforge.yml
?FlowFuse/helm
to update ConfigMap TemplateFlowFuse/CloudProject
to update values for Staging/ProductionLabels
area:migration
label