kfctl: pin configs to v0.6.1

[yanniszark]

Fixes #3862

This PR pins the kubeflow and manifests repo versions to v0.6.1 (which is the latest release) for all configs.

/assign @abhi-g @lluunn

Signed-off-by: Yannis Zarkadas yanniszark@arrikto.com

---

This change is 

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign yanniszark
You can assign the PR to them by writing /assign @yanniszark in a comment when ready.

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

Needs approval from an approver in each of these files:

• bootstrap/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[lluunn]

I think we want to pin only at 0.6, so PR should make to v0.6-branch?

[yanniszark]

@lluunn why is that? The latest release is v0.6.1. Why not use that?

cc @abhi-g

[lluunn]

Why not master points to master, 0.6 points to 0.6?

Also test is using the config file, and master should be tested.

[abhi-g]

I think Lun-kai's point is to pin to the v0.6-branch rather than a tag such as v0.6.0, v0.6.1 etc. That way if we have patch releases, we won't need to update these. Abhishek

…

On Sat, Aug 10, 2019 at 10:47 AM Yannis Zarkadas ***@***.***> wrote: @lluunn <https://github.com/lluunn> why is that? The latest release is v0.6.1. Why not use that? cc @abhi-g <https://github.com/abhi-g> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3864?email_source=notifications&email_token=ACZ2UZTIHSSKRDCYCNMDZKLQD35LHA5CNFSM4IKZLBNKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4ASB7Y#issuecomment-520167679>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACZ2UZVGYR4X6TQAF2WZS43QD35LHANCNFSM4IKZLBNA> .

[jlewi]

It looks like this PR would be pinning the version on master.
Should we instead check this change in to the v0.6-branch of kubeflow/kubeflow?

I think it makes sense for kubeflow/kubeflow master to point to master of kubeflow/manifests

[yanniszark]

@jlewi sounds good to me.
I'll submit a pr for the v0.6-branch.

[yanniszark]

I'm closing this one for #3867