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

Add best practice for tekton and other argo executors #338

Merged
merged 3 commits into from Oct 21, 2020

Conversation

Tomcli
Copy link
Member

@Tomcli Tomcli commented Oct 20, 2020

Which issue is resolved by this Pull Request:
Resolves #

Description of your changes:
Add some best practice to address #330 for some of the volume problem for Tekton and Argo executors that need volume mount. Currently the root path artifact/parameter files only works well with Argo's docker executor, so we need to find a way to parametrize the volume path inside the kale sdk.

Environment tested:

  • Python Version (use python --version):
  • Tekton Version (use tkn version):
  • Kubernetes Version (use kubectl version):
  • OS (e.g. from /etc/os-release):

Checklist:

  • The title for your pull request (PR) should follow our title convention. Learn more about the pull request title convention used in this repository.

    PR titles examples:

    • fix(frontend): fixes empty page. Fixes #1234
      Use fix to indicate that this PR fixes a bug.
    • feat(backend): configurable service account. Fixes #1234, fixes #1235
      Use feat to indicate that this PR adds a new feature.
    • chore: set up changelog generation tools
      Use chore to indicate that this PR makes some changes that users don't need to know.
    • test: fix CI failure. Part of #1234
      Use part of to indicate that a PR is working on an issue, but shouldn't close the issue when merged.
  • Do you want this pull request (PR) cherry-picked into the current release branch?

    If yes, use one of the following options:

    • (Recommended.) Ask the PR approver to add the cherrypick-approved label to this PR. The release manager adds this PR to the release branch in a batch update.
    • After this PR is merged, create a cherry-pick PR to add these changes to the release branch. (For more information about creating a cherry-pick PR, see the Kubeflow Pipelines release guide.)

@kubeflow-bot
Copy link

This change is Reviewable

@Tomcli
Copy link
Member Author

Tomcli commented Oct 20, 2020

/approve cancel

samples/kfp-user-guide/README.md Outdated Show resolved Hide resolved
samples/kfp-user-guide/README.md Outdated Show resolved Hide resolved
samples/kfp-user-guide/README.md Outdated Show resolved Hide resolved
samples/kfp-user-guide/README.md Outdated Show resolved Hide resolved
Co-authored-by: Animesh Singh <singhan@us.ibm.com>
@animeshsingh
Copy link
Collaborator

/lgtm
/approve

@k8s-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: animeshsingh

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

@k8s-ci-robot k8s-ci-robot merged commit a116132 into kubeflow:master Oct 21, 2020
jizg added a commit to jizg/kfp-tekton that referenced this pull request Nov 3, 2020
…sanitizing-k8s-objects

* commit '3d3ecfb05fc13f400d4aec5ee5a0ca9b13b1566f':
  feat(sdk): added sanitizing k8s object process and test. Fixes: kubeflow#332 (kubeflow#345)
  add a warning label to kustomize page (kubeflow#350)
  make user guide prominent (kubeflow#349)
  feat(backend): ARTIFACT_COPY_STEP_TEMPLATE - custom template for copy step (kubeflow#336)
  Add KFP Tekton release deployment yaml (kubeflow#347)
  Fix UI merge conflict that blocks the UI image build. (kubeflow#346)
  KFP 1.0.4 Rebase (kubeflow#337)
  fix(sdk): Quick fix for sanitizing conditional variables (kubeflow#344)
  fix(backend): cover nil status race condition from Tekton (kubeflow#329)
  updated titanic-ml generated with kale 0.5.1 (kubeflow#330)
  Add s3 endpoint instructions for admin use case (kubeflow#323)
  Add best practice for tekton and other argo executors (kubeflow#338)
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.

None yet

4 participants