Skip to content

Conversation

ppawlowski
Copy link
Contributor

Description

This pull request refines how Ingress annotations managed by the FlowFuse Helm chart are handled.

The high-level logic is:

  1. If defined, add the cert-manager annotation cert-manager.io/cluster-issuer with the value of ingress.certManagerIssuer.
    1a. Add other non–cert-manager annotations as provided.
    2 If ingress.certManagerIssuer is not defined, add all annotations defined in ingress.annotations.
    3 Add the spec.tls block whenever any cert-manager annotation is present, either via ingress.certManagerIssuer or defined via ingress.annotations.
  2. For backward compatibility, ingress.certManagerIssuer takes precedence over any cert-manager.io/* annotations specified in ingress.annotations.

The same logic is applied to the broker Ingress resources.

Additionally, driver configuration values has been extended by projectIngressAnnotations and customHostname.ingressAnnotations properties.

Related Issue(s)

#683
FlowFuse/driver-k8s#242

Checklist

  • I have read the contribution guidelines
  • Suitable unit/system level tests have been added and they pass
  • Documentation has been updated
    • Upgrade instructions
    • Configuration details
    • Concepts
  • Changes flowforge.yml?
    • Issue/PR raised on FlowFuse/helm to update ConfigMap Template
    • Issue/PR raised on FlowFuse/CloudProject to update values for Staging/Production
  • Link to Changelog Entry PR, or note why one is not needed.

Labels

  • Includes a DB migration? -> add the area:migration label

@ppawlowski ppawlowski requested a review from hardillb October 6, 2025 13:07
"type": "boolean"
},
"customeHostname": {
"customHostname": {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wonder how long that's been there

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants