-
Notifications
You must be signed in to change notification settings - Fork 716
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
Failed to update TFJob status in version v1 #1003
Comments
Issue-Label Bot is automatically applying the label Links: app homepage, dashboard and code for this bot. |
/assign @richardsliu |
I can reproduce it. We define status as status subresource in client but we do not define it in CRD yaml. |
Fixed it with apiVersion: apiextensions.k8s.io/v1beta1
kind: CustomResourceDefinition
metadata:
name: tfjobs.kubeflow.org
spec:
group: kubeflow.org
scope: Namespaced
versions:
- name: v1
served: true
storage: true
names:
kind: TFJob
singular: tfjob
plural: tfjobs
+ subresources:
+ status: {}
validation:
openAPIV3Schema:
properties:
spec:
properties:
tfReplicaSpecs:
properties:
# The validation works when the configuration contains
# `Worker`, `PS` or `Chief`. Otherwise it will not be validated.
Worker:
properties:
replicas:
type: integer
minimum: 1
PS:
properties:
replicas:
type: integer
minimum: 1
Chief:
properties:
replicas:
type: integer
minimum: 1
maximum: 1 |
/close |
@gaocegege: 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. |
I'm trying v0.5.1, after all pods & services created, there is an error msg:
error syncing tfjob: the server could not find the requested resource (put tfjobs.kubeflow.org tfjob-smoke-v1-1)
And this is coming from here:
My CRD looks like this:
The text was updated successfully, but these errors were encountered: