Skip to content

Add a server-side apply example - #4890

Merged
kubernetes-prow[bot] merged 1 commit into
kubernetes-client:masterfrom
thev1ndu:add-server-side-apply-example
Aug 31, 2026
Merged

Add a server-side apply example#4890
kubernetes-prow[bot] merged 1 commit into
kubernetes-client:masterfrom
thev1ndu:add-server-side-apply-example

Conversation

@thev1ndu

Copy link
Copy Markdown
Contributor

What type of PR is this?

/kind documentation

What this PR does / why we need it:

The ServerSideApply utility in the util module has no accompanying example, even though server-side apply is a common operation. This adds ServerSideApplyExample, which:

  • applies a ConfigMap with a field manager,
  • re-applies an updated manifest with forceConflicts to show idempotent updates and field ownership,
  • runs a dry-run apply that the server validates without persisting.

It follows the style of the existing examples and passes spotless:check.

Which issue(s) this PR fixes:

None

Does this PR introduce a user-facing change?

NONE

The ServerSideApply utility had no accompanying example. This adds
ServerSideApplyExample, which applies a ConfigMap, re-applies it with
forceConflicts, and runs a dry-run apply.
@kubernetes-prow kubernetes-prow Bot added the kind/documentation Categorizes issue or PR as related to documentation. label Aug 31, 2026
@kubernetes-prow kubernetes-prow Bot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Aug 31, 2026
@kubernetes-prow

Copy link
Copy Markdown
Contributor

Welcome @thev1ndu!

It looks like this is your first PR to kubernetes-client/java 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-client/java has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

@kubernetes-prow kubernetes-prow Bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Aug 31, 2026
@brendandburns

Copy link
Copy Markdown
Contributor

/lgtm
/approve

@kubernetes-prow kubernetes-prow Bot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Aug 31, 2026
@kubernetes-prow

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: brendandburns, thev1ndu

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubernetes-prow kubernetes-prow Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 31, 2026
@kubernetes-prow
kubernetes-prow Bot merged commit bd9ff4e into kubernetes-client:master Aug 31, 2026
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/documentation Categorizes issue or PR as related to documentation. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants