-
Notifications
You must be signed in to change notification settings - Fork 3
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
add coverage for phase2 synchronizer #81
Conversation
Summary:
|
Summary:
|
Summary:
|
Summary:
|
Summary:
|
Summary:
|
Summary:
|
Signed-off-by: Matthias Bertschy <matthias.bertschy@gmail.com>
Summary:
|
_, err = c.dynamicClient.Resource(c.res).Namespace(id.Namespace).Apply(context.Background(), id.Name, &obj, metav1.ApplyOptions{FieldManager: "application/apply-patch"}) | ||
options := metav1.ApplyOptions{ | ||
FieldManager: "application/apply-patch", | ||
Force: true, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@amirmalka I think I ran into the issue that we saw last month - do you think it's OK to force here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Eventually we discovered that the problem was trying to apply a namespaced object for a non-namespaced resource definition.
Why do we need to force? What is the issue you are seeing?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
right... well in this case we really need it since it's an existing object, that was updated in both sides, but we want the backend to have the last word on it
I think mechanism 1 applies here: https://pkg.go.dev/k8s.io/client-go/applyconfigurations#hdr-Controller_Support
Summary:
|
No description provided.