-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Sync created resources upon edit of CustomResource #39
Comments
This can be worked around easily by deleting and re-creating the FunctionIngress record, or editing the Ingress directly. Would you be willing to work on a PR in the meantime? |
/add label: good first issue, help wanted |
/set title: Sync created resources upon edit of CustomResource |
Having another look at this, it seems that we already have support for this in the code? Are you on the latest version of the build? |
It seems like we only synchronise the spec, and not annotations. That is probably a deliberate design decision due to the way Kubernetes adds automated annotations to some objects. |
Expected Behaviour
When adding/updating annotations to the
FunctionIngress
, these should be added/updated on the underlyingIngress
.Current Behaviour
If the
FunctionIngress
and the underlyingIngress
already exist, changes to theFunctionIngress
annotations aren't passed to the underlyingIngress
.Possible Solution
There's probably a validation on whether the ingress already exists that is bypassing the expected behaviour.
Steps to Reproduce (for bugs)
FunctionIngress
with no custom annotationskubectl
nginx.ingress.kubernetes.io/limit-connections: 10
kubectl
Your Environment
The text was updated successfully, but these errors were encountered: