Skip to content
This repository has been archived by the owner on Feb 22, 2022. It is now read-only.

Added Pachyderm chart #3114

Merged
merged 5 commits into from
Jan 4, 2018
Merged

Conversation

jonandernovella
Copy link
Collaborator

@jonandernovella jonandernovella commented Dec 20, 2017

Pachyderm is a language-agnostic and cloud infrastructure-agnostic large-scale data processing framework based on software containers. This chart can be used to deploy Pachyderm locally or backed by object stores of different Cloud providers.

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Dec 20, 2017
@mcapuccini
Copy link
Contributor

mcapuccini commented Dec 20, 2017

+1

@mcapuccini
Copy link
Contributor

@jonandernovella I think you are supposed to put this in the incubation directory.

@jonandernovella
Copy link
Collaborator Author

@mcapuccini I tried to meet all the guidelines for it to be stable!

@jonandernovella
Copy link
Collaborator Author

/assign @prydonius

Copy link
Member

@prydonius prydonius left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can I suggest moving etcd out into it's own chart (ideally improving the existing incubator chart and moving it to stable) and bringing it in as a dependency?

| Parameter | Description | Default |
|--------------------------|-----------------------|-------------------|
| `pachd.image.repository` | Container image name | `pachyderm/pachd` |
| `*.image.tag` | Container image tag | `1.6.6` |
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you could use something like <latest version> to avoid having to update this README each time the version is bumped

- distributed
- processing
version: 0.1.0
home: "https://pachyderm.io"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

would it make sense to add this icon? https://avatars2.githubusercontent.com/u/10432478?s=200&v=4


To check that installation was successful, you can try running pachctl help, which should return a list of Pachyderm commands. Please note that the client version should correspond to the pachd service version. For more information please consult: http://pachyderm.readthedocs.io/en/latest/index.html.

If you install the client on your master node, you should already be able to interact with the service. Also, if you have your kubernetes client properly configured to talk with your remote cluster, you can simply install `pachctl` on your local machine and execute: `pachctl port-forward &`.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we print out a useable pachctl command? e.g. pachctl port-forward -k -n {{.Release.Namespace}} & would be useful when pachd is not in the default/configured NS.

- reproducibility
- distributed
- processing
version: 0.1.0
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

appVersion should be set to 1.6.6


On Linux environments:

$ curl -o /tmp/pachctl.deb -L https://github.com/pachyderm/pachyderm/releases/download/v1.6.6/pachctl_1.6.6_amd64.deb && sudo dpkg -i /tmp/pachctl.deb
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

with appVersion set in Chart.yaml, you can template this with {{.Chart.AppVersion}} I think

Copy link
Member

@prydonius prydonius left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

almost there, just a few small fixes and then I think this is good to go!

We strongly suggest that the installation of Pachyderm should be performed in its own namespace. The default installation will deploy Pachyderm on your local Kubernetes cluster:

```console
$ helm install --name my-release stable/pachyderm
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Adding --namespace pachyderm would be good to illustrate the above recommendation.


To check that installation was successful, you can try running pachctl help, which should return a list of Pachyderm commands.

If you install the client on your master node, you should already be able to interact with the service. Also, if you have your kubernetes client properly configured to talk with your remote cluster, you can simply install `pachctl` on your local machine and execute: `pachctl -k ‘-n={{ .Release.Namespace }}’ port-forward &`.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

are the quote marks supposed to be around ‘-n={{ .Release.Namespace }}’?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think so. As far as I read it needs to be there

@prydonius
Copy link
Member

Can I suggest moving etcd out into it's own chart (ideally improving the existing incubator chart and moving it to stable) and bringing it in as a dependency?

@jonandernovella and I discussed this on Slack, unfortunately pachyderm expects a service called etcd and the pachctl client also expects a deployment named pachd to port-forward to. Therefore, this chart doesn't use the convention "fullname" template for naming deployments and services. In the README, we're recommending that the chart be installed in its own namespace.

@prydonius
Copy link
Member

/lgtm

@k8s-ci-robot k8s-ci-robot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jan 4, 2018
@prydonius
Copy link
Member

/ok-to-test

@k8s-ci-robot k8s-ci-robot removed the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Jan 4, 2018
@prydonius
Copy link
Member

/lgtm cancel

@k8s-ci-robot k8s-ci-robot removed lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jan 4, 2018
sources:
- "https://github.com/pachyderm/pachyderm"
maintainers:
- name: Jon Ander Novella
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you make sure all names are actually GitHub IDs? It makes it easier to reference back. Also, please add an OWNERS file (see format), which will allow anyone listed there to approve PRs.

@k8s-ci-robot k8s-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jan 4, 2018
Copy link
Member

@prydonius prydonius left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jonandernovella, prydonius

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

Needs approval from an approver in each of these OWNERS Files:

You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 4, 2018
@k8s-ci-robot k8s-ci-robot merged commit 856f6b5 into helm:master Jan 4, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm Indicates that a PR is ready to be merged. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants