fix: Separate project's and core app ingress annotations #511
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 separates the ingress annotations for the project's (NR instances) and the core application.
Custom annotations for NR instances can now be defined using the
forge.projectIngressAnnotation
variable.To prevent breaking changes, the existing
ingress.annotations
will continue to be used as the value for theINGRESS_ANNOTATIONS
environment variable within the core application ifforge.projectIngressAnnotation
is not defined.Related Issue(s)
Closes #475
Checklist
flowforge.yml
?FlowFuse/helm
to update ConfigMap TemplateFlowFuse/CloudProject
to update values for Staging/ProductionLabels
area:migration
label