Deploy pylon to a non-master node
Open
@abuccts is already working on this.
Since Jul 21, 2020.
pai-dev
- Dominant language
- JavaScript
- Stars
- 2.7k
- Forks
- 554
- Avg merge
- 20h 42m
- Merged PRs (30d)
- 14
Description
In aks-engine, the 443 ports is ocuppied with api-server. It's a un-configurable option. So pylon with 443 port can't deployed on master node.
-
Solution 1: Change the label from
openpai-master: truetoopenpai-pylon: true -
Solution 2: Support multiple nodeAffinity rule in our service.yml. In official doc, it says
If you specify multiple nodeSelectorTerms associated with nodeAffinity types, then the pod can be scheduled onto a node if one of the nodeSelectorTerms can be satisfied.
For example
affinity:
nodeAffinity:
requiredDuringSchedulingIgnoredDuringExecution:
nodeSelectorTerms:
- matchExpressions:
- key: pai-master
operator: In
values:
- true
- key: pai-pylon
operator: NotIn
values:
- false
- matchExpressions:
- key: pai-pylon
operator: In
values:
- true
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.
Assessment
This issue has not been assessed yet.