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

Set the Programmed condition in the KongUpstreamPolicy ancestor status #5249

Closed
1 of 2 tasks
Tracked by #5291
mlavacca opened this issue Nov 28, 2023 · 2 comments · Fixed by #5444
Closed
1 of 2 tasks
Tracked by #5291

Set the Programmed condition in the KongUpstreamPolicy ancestor status #5249

mlavacca opened this issue Nov 28, 2023 · 2 comments · Fixed by #5444
Assignees
Labels
area/feature New feature or request
Milestone

Comments

@mlavacca
Copy link
Member

mlavacca commented Nov 28, 2023

Is there an existing issue for this?

  • I have searched the existing issues

Problem Statement

#4932 aims at introducing the Accepted condition in the KongUpstreamPolicy object status. This issue is about adding the ancestor's programmed condition, which should be set after the clients push the configuration affected by the KongUpstreamPolicy to the dataplane.

Proposed Solution

When the client pushes a Service or a KongServiceFacade affected by a KongUpstreamPolicy, such an event is bubbled up to the controller, and the controller properly sets the ancestor's Programmed condition to True or False depending on the push outcome.

Additional information

No response

Acceptance Criteria

  • When a Service or a KongServiceFacade affected by a KongUpstreamPolicy is pushed, the ancestor status in the KongUpstreamPolicy gets updated according to the outcome of the push action.
@mlavacca mlavacca added the area/feature New feature or request label Nov 28, 2023
@mlavacca mlavacca added this to the KIC v3.1.x milestone Nov 28, 2023
@mlavacca
Copy link
Member Author

mlavacca commented Nov 28, 2023

Blocked by #4932

@mflendrich
Copy link
Contributor

No longer blocked - #4932 is done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/feature New feature or request
Projects
None yet
4 participants