Skip to content

Dependent Resource Creation behavior configurable #1999

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.

Sign up for GitHub

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

Jump to bottom
Closed
csviri opened this issue Aug 7, 2023 · 0 comments · Fixed by #2001
Closed

Dependent Resource Creation behavior configurable #1999

csviri opened this issue Aug 7, 2023 · 0 comments · Fixed by #2001
Assignees
@csviri
Milestone
4.5

Comments

@csviri
Copy link
Collaborator

csviri commented Aug 7, 2023 •
edited
Loading

With sever side apply in dependent resources, it can happen that the resource is already created ( if no owner reference present, the cache will not contain it). Currently in this case the creation will fail. Although there might be use cases when simply desired that this resource is overwritten. To delegate this decision to the user a feature flag can be introduced to make this configurable.
This is feature flag per resource (not a global one).

see also discussion: #1995
@csviri csviri self-assigned this Aug 7, 2023
@csviri csviri added this to the 4.5 milestone Aug 7, 2023
@csviri csviri linked a pull request Aug 7, 2023 that will close this issue
feat: create resource only if not exists #2001
Merged
@csviri csviri closed this as completed Aug 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@csviri csviri

Labels
None yet
Projects
None yet
Milestone
4.5
Development

Successfully merging a pull request may close this issue.

feat: create resource only if not exists operator-framework/java-operator-sdk
1 participant
@csviri