Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sync created resources upon edit of CustomResource #39

Closed
goncalo-oliveira opened this issue Nov 2, 2020 · 6 comments
Closed

Sync created resources upon edit of CustomResource #39

goncalo-oliveira opened this issue Nov 2, 2020 · 6 comments
Labels
good first issue Good for newcomers help wanted Extra attention is needed

Comments

@goncalo-oliveira
Copy link

Expected Behaviour

When adding/updating annotations to the FunctionIngress, these should be added/updated on the underlying Ingress.

Current Behaviour

If the FunctionIngress and the underlying Ingress already exist, changes to the FunctionIngress annotations aren't passed to the underlying Ingress.

Possible Solution

There's probably a validation on whether the ingress already exists that is bypassing the expected behaviour.

Steps to Reproduce (for bugs)

  1. Create a FunctionIngress with no custom annotations
  2. Apply with kubectl
  3. Add a custom annotation, for example nginx.ingress.kubernetes.io/limit-connections: 10
  4. Apply with kubectl
  5. Annotations aren't in the ingress

Your Environment

  • ingress-operator 0.6.5
  • v1.18.8 (DigitalOcean)
  • Linux
@alexellis
Copy link
Member

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?

@alexellis
Copy link
Member

/add label: good first issue, help wanted

@derek derek bot added good first issue Good for newcomers help wanted Extra attention is needed labels Nov 17, 2020
@alexellis
Copy link
Member

/set title: Sync created resources upon edit of CustomResource

@derek derek bot changed the title Annotations not added to an existing ingress Sync created resources upon edit of CustomResource Nov 17, 2020
@alexellis
Copy link
Member

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?

@alexellis
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants