Skip to content
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

Fix XGBoost container name in log message #1362

Merged

Conversation

andreyvelich
Copy link
Member

I fixed name in XGBoostJob validation.
Btw, is it fine that we don't run this validation before Job submission ?

As I can see, user can detect that Job is not valid only from the controller logs, even if YAML is incorrect: https://github.com/kubeflow/tf-operator/blob/master/pkg/controller.v1/xgboost/xgboostjob_controller.go#L146-L148.
Do we have any method to detect that YAML is valid other than validation webhook ?

cc @kubeflow/wg-training-leads

@Jeffwan
Copy link
Member

Jeffwan commented Aug 14, 2021

/lgtm
/approve

@google-oss-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Jeffwan

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

The pull request process is described here

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

@google-oss-robot google-oss-robot merged commit 08c0d03 into kubeflow:master Aug 14, 2021
@Jeffwan
Copy link
Member

Jeffwan commented Aug 14, 2021

@andreyvelich Yes, we do.

I may forget to create that issue. We planned to use CRD Validation and this is client side validation and validation rules will be populated in the CRD definition.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants