-
Notifications
You must be signed in to change notification settings - Fork 297
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
BadRequest: the name of the object (admin based on URL) was undeterminable: name must be provided #1214
Comments
could you please share the patch code? |
@tg123 Here is the json data I am sending for deployment update. |
|
I tried with setting the Name value as well. It still gives the same error. Any other solution you can help with ? |
not sure how you create your patch obj, the err means you did not provide name of the obj correctly
|
@tg123 Here is the updated patch obj where I assigned all the name values which were null previously. But I am still facing the same issue. [ |
if your patch object is generated by asp.net json patch, please migrate to https://www.nuget.org/packages/JsonPatch.Net see #772 |
see #772 (comment) |
Describe the bug
I am getting BadRequest response while updating the deployment.
It was working fine with older version. I recently upgraded k8s client to 10.0.1
Kubernetes C# SDK Client Version
10.0.1
Server Kubernetes Version
1.25.6
Dotnet Runtime Version
net6
To Reproduce
Steps to reproduce the behavior:
Try updating the deployment,
PatchNamespacedDeployment(V1Patch, Name, NamespaceName)
Error
{
"kind": "Status",
"apiVersion": "v1",
"metadata": {},
"status": "Failure",
"message": "the name of the object (admin based on URL) was undeterminable: name must be provided",
"reason": "BadRequest",
"code": 400
}
Expected behavior
A clear and concise description of what you expected to happen.
KubeConfig
If applicable, add a KubeConfig file with secrets redacted.
Where do you run your app with Kubernetes SDK (please complete the following information):
Additional context
I am able to update the deployment image, but not the entire deployment with full json data.
The text was updated successfully, but these errors were encountered: