Outdated usage report message in kfctl with kustomize

[IronPan]

Saw following error message when running

kfctl generate all -V --zone ${ZONE}

Building kfctl from head(https://github.com/kubeflow/kubeflow/tree/31a9bb666a13e3aea60f9a246574db27f2ee9d05) which uses kustomize.

---

Notice anonymous usage reporting enabled using spartakus
To disable it
If you have already deployed it run the following commands:
cd $(pwd)
ks delete default -c spartakus
kubectl -n ${K8S_NAMESPACE} delete deploy -l app=spartakus

Then run the following command to remove it from your ksonnet app:
ks component rm spartakus

For more info: https://www.kubeflow.org/docs/guides/usage-reporting/

---

[issue-label-bot]

Issue-Label Bot is automatically applying the label kind/bug to this issue, with a confidence of 0.91. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

[jlewi]

@xauthulei committed kubeflow/kfctl#9

However, kubeflow/kubeflow is still source of truth for kfctl; so we need to get that PR cherry-picked onto kubeflow/kubeflow so the changes don't get overwritten on the next sync of kubeflow/kubeflow to kubeflow/kfctl

/assign @xauthulei

[k8s-ci-robot]

@jlewi: GitHub didn't allow me to assign the following users: xauthulei.

Note that only kubeflow members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

@xauthulei committed kubeflow/kfctl#9

However, kubeflow/kubeflow is still source of truth for kfctl; so we need to get that PR cherry-picked onto kubeflow/kubeflow so the changes don't get overwritten on the next sync of kubeflow/kubeflow to kubeflow/kfctl

/assign @xauthulei

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.

[xauthulei]

@jlewi , I commit my fixes in PR #3941

[jlewi]

@xauthulei Thank you so much.
Just one more thing. After #3941 is merged can you follow these instructions to cherry-pick it onto the v0.6-branch.

Its just a simple script you have to run to auto-create a PR with the same changes.

[xauthulei]

@jlewi , I will try to do it later. Thanks.

[xauthulei]

@xauthulei Thank you so much.
Just one more thing. After #3941 is merged can you follow these instructions to cherry-pick it onto the v0.6-branch.

Its just a simple script you have to run to auto-create a PR with the same changes.

It is done , see PR #3942, Could you review that. Many Thanks.

[jlewi]

#3941 has been merged so I'm closing this out.