-
Notifications
You must be signed in to change notification settings - Fork 524
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
Fix #756: Service re-apply error happening during k8s:watch
#757
Fix #756: Service re-apply error happening during k8s:watch
#757
Conversation
Codecov Report
@@ Coverage Diff @@
## master #757 +/- ##
=========================================
Coverage 46.21% 46.21%
+ Complexity 3246 3245 -1
=========================================
Files 413 413
Lines 19856 19856
Branches 2781 2781
=========================================
Hits 9176 9176
Misses 9661 9661
Partials 1019 1019
Continue to review full report at Codecov.
|
Please check and add references to the changes in the Fabric8 Kubernetes Client project that made this changes required. |
00c878f
to
716cc62
Compare
|
…atch` Use patch() instead of edit() in order to avoid 422 from APIServer. KubernetesClient no longer handles object modification in case of edit() when base object is provided. Signed-off-by: Rohan Kumar <[email protected]>
716cc62
to
f9b207b
Compare
Kudos, SonarCloud Quality Gate passed! |
Description
Fix #756
Use patch() instead of edit() since we don't seem to be making use of the
p
(argument in UnaryOperator which is usually resource fetched from Server).Based on discussion here fabric8io/kubernetes-client#3221 (comment)
Signed-off-by: Rohan Kumar [email protected]
Type of change
test, version modification, documentation, etc.)
Checklist