Open roycaihw opened 3 years ago
It's not GA yet. Likely it's becoming GA in the upcoming 1.22 release.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
Now that kubernetes 1.22 is GA with https://kubernetes.io/blog/2021/08/04/kubernetes-1-22-release-announcement/#server-side-apply-graduates-to-ga are we comfortable making this happen?
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close
@k8s-triage-robot: Closing this issue.
/reopen /remove-lifecycle rotten
@roycaihw: Reopened this issue.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
/remove-lifecycle rotten
How about marking this one as frozen?
I am surprised that this problem has not been resolved yet. Are there any alternatives?
@ryota2425 I believe the dynamic client supports it
Thanks. That is what I was looking for.
What's the blocker with adding support for this outside of the dynamic client (e.g. for the AppsV1API client)? I see that many of the fields are already available, the only thing I don't see is how to change the Content-Type
header of requests to use application/apply-patch+yaml
. Is it a limitation of the openapi generator? Or do you just need someone willing to add support and put in a PR?
What is the feature and why do you need it: Kubernetes server-side apply is meant to be the new standard of patching objects and managing fields. Today the Python client supports v18 API (v18.17.0a1), where server-side apply went beta 2. We should explore what's missing to support the feature in this client.
cc @fabianvf