Provide a "no cni mode" in OpenPAI
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2.7k
- Forks
- 554
- Avg merge
- 20h 42m
- Merged PRs (30d)
- 14
Description
Sometimes k8s network plugin causes some problems in OpenPAI. Users can follow the steps below to solve the problem:
-
remove CNI in Kubernetes
Detailed steps are provided here : https://openpai.readthedocs.io/en/latest/manual/cluster-admin/installation-faqs-and-troubleshooting.html#how-to-remove-the-k8s-network-plugin -
change OpenPAI source code
- Change pylon and rest-server to use hostNetwork
- Change pylon/rest-server config, make them use “localhost” to connect PAI service in master node
- Change hivedScheduler service type from “NodePort” to “ClusterIP”
The solution is not easy to perform. Maybe we can provide a "no cni mode" in OpenPAI for this need.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Kubernetes network-plugin troubleshooting documentation and inspect the pylon, rest-server, and hivedScheduler deployment configuration. Define what a supported no-CNI mode must change across host networking, service connectivity, and service type, then document and validate the complete setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- infrastructure, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100