-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
CRD's don't have dry_run option #1165
Comments
Hi @sniranjan, the support for /assign |
Hi @palnabarun , when can we expect the next version of the client? It's currently blocking us for the dry-run feature |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@sniranjan @LouisPlisso -- with #1280, this feature would come to the latest stable client release. Thank you for your patience. 👍 |
/remove-lifecycle rotten |
This has now been resolved with the latest client release. /close |
@palnabarun: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
While working with CRDs (create/patch/delete), there is no dry_run option similar to the other native objects.
API Call for creating a custom object
api_instance.create_namespaced_custom_object(group, version, namespace, plural, body, pretty=pretty)
Reference - create_namespaced_custom_object
API Call for Deployment
api_instance.create_namespaced_deployment(namespace, body, pretty=pretty, dry_run=dry_run, field_manager=field_manager)
Is there any workaround to this?
The text was updated successfully, but these errors were encountered: