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

[feature] Add Helm Chart for tf-operator #1197

Closed
gaocegege opened this issue Dec 11, 2020 · 12 comments · May be fixed by #2263
Closed

[feature] Add Helm Chart for tf-operator #1197

gaocegege opened this issue Dec 11, 2020 · 12 comments · May be fixed by #2263

Comments

@gaocegege
Copy link
Member

No description provided.

@sanjeepan23
Copy link

I would like to work on this issue. Since I'm new here, can someone guide me?

@gaocegege
Copy link
Member Author

Thanks, @goat023

You can have a look at other operator's helm chart, like tidb-operator or etcd-operator. It should be similar to them.

@terrytangyuan
Copy link
Member

There's also helm chart for mpi-operator for reference but probably needs some update as well: https://github.com/kubeflow/mpi-operator/tree/master/hack/helm/mpi-operator

@sanjeepan23
Copy link

Thanks, I'll try

@sanjeepan23
Copy link

where can I get the maintainer's name and email address for this repo

@gaocegege
Copy link
Member Author

@gaocegege
Copy link
Member Author

@goat023 Hi, is there any progress?

@stale
Copy link

stale bot commented Jun 2, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the lifecycle/stale label Jun 2, 2021
@stale stale bot closed this as completed Jun 9, 2021
@ehudyonasi
Copy link

Do you still need one?

@johnugeorge
Copy link
Member

Inorder to ensure that helm charts are in sync, we can add one extra check in Github Actions.

@github-actions
Copy link

github-actions bot commented Oct 4, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions
Copy link

This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants