Make edl controller jobparser workable #7
Conversation
example/examplejob.yaml
Outdated
| name: example | ||
| spec: | ||
| #image: "paddlepaddle/paddlecloud-job" | ||
| image: "typhoon1986/paddlecloud-job:wuyitest" |
There was a problem hiding this comment.
Maybe we can keep the official Docker image.
| kind: Deployment | ||
| metadata: | ||
| name: training-job-controller | ||
| namespace: paddlecloud |
There was a problem hiding this comment.
do we need to create the namespace before this yaml can claim?
There was a problem hiding this comment.
Indeed. We should update the documents later.
|
excellent! I was trying the same yesterday to make the whole thing work. also, to make the training job work as CRD, do we just need to change the yaml(thirdpartyresource.yaml) or there are go code need to change with that? |
| WORKDIR $GOPATH/src/github.com/paddlepaddle/edl | ||
| RUN glide install --strip-vendor | ||
| ADD . $GOPATH/src/github.com/paddlepaddle/edl |
There was a problem hiding this comment.
Thanks! This is the correct solution.
edl_controller.yaml
Outdated
| containers: | ||
| - name: training-job-controller | ||
| image: paddlepaddle/edl-controller | ||
| imagePullPolicy: Never |
There was a problem hiding this comment.
should we change the policy to IfNotPresent?
User cert management
@putcn Yes, I'm afraid we have to put the CRD implement in another branch, it should have a lot of difference from this one. |
Fix #6 and add some examples.