Revision 31d2e10bf0b053fbe7905065d951548ad18eabcc authored by Jeremy Lewi on 21 September 2018, 09:17:41 UTC, committed by k8s-ci-robot on 21 September 2018, 09:17:41 UTC
* Related to #141 katib releaser * Related to kubeflow/kubeflow#1574 use prow to build our images * We are moving to using prow to run our release workflows and treating them just like regular workflows. * We are doing this because we need to get regular signal about whether the image builds are succeeding by running on postsubmit. * We also want to run them on presubmit so that we can verify any changes to the workflwo don't break the workflow. * Rather than define a new workflow to build the images; we can just reuse the existing E2E workflow which already builds all the images. We just change postsubmit to push to kubeflow-images-public. * Delete the releaser app; we will just the existing E2E test workflow and have that push to gcr.io/kubeflow-images-public on postsubmit.
1 parent 81f2b74
grid-example.yaml
apiVersion: "kubeflow.org/v1alpha1"
kind: StudyJob
metadata:
namespace: katib
labels:
controller-tools.k8s.io: "1.0"
name: grid-example
spec:
studyName: grid-example
owner: crd
optimizationtype: maximize
objectivevaluename: Validation-accuracy
optimizationgoal: 0.99
metricsnames:
- accuracy
parameterconfigs:
- name: --lr
parametertype: double
feasible:
min: "0.01"
max: "0.03"
- name: --num-layers
parametertype: int
feasible:
min: "2"
max: "5"
- name: --optimizer
parametertype: categorical
feasible:
list:
- sgd
- adam
- ftrl
workerSpec:
goTemplate:
templatePath: "/worker-template/cpuWorkerTemplate.yaml"
suggestionSpec:
suggestionAlgorithm: "grid"
suggestionParameters:
-
name: "DefaultGrid"
value: "1"
-
name: "--lr"
value: "4"
Computing file changes ...
