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.

Sign up for GitHub

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

Kubernetes deployment minor fixes. #310

Merged
merged 1 commit into from
Sep 21, 2022
Merged

Kubernetes deployment minor fixes. #310

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions Federated-Deployment/kubernetes/DevDeployment.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,9 +20,9 @@ kind create cluster --config Federated-Deployment/kubernetes/kind_configuration/
2. After the nodes are started, you need to taint them properly:
```
kubectl taint nodes kind-control-plane node-role.kubernetes.io/master-
kubectl label node kind-control-plane nodeType=master
kubectl label node kind-worker nodeType=worker
kubectl label node kind-worker2 nodeType=worker
kubectl label node kind-control-plane master=true
kubectl label node kind-worker worker=true
kubectl label node kind-worker2 worker=true
```

3. (Optional) Load the docker images to the kuberentes cluster, if not the images will be pulled from dockerhub:
Expand Down
4 changes: 2 additions & 2 deletions Federated-Deployment/kubernetes/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ kubectl apply -f https://docs.projectcalico.org/v3.20/manifests/calico.yaml

```
kubectl taint nodes --all node-role.kubernetes.io/master-
kubectl label node <master-node-name> nodeType=master
kubectl label node <master-node-name> master=true
```

### Add a worker node to the cluster
Expand All @@ -64,7 +64,7 @@ Use the provided on the **worker** node, with `sudo`, to join the cluster.
2. Allow worker-specific pods to run on the **worker** node with:

```
kubectl label node <worker-node-name> nodeType=worker
kubectl label node <worker-node-name> worker=true
```

3. If the node has status `Ready,SchedulingDisabled` run:
Expand Down
2 changes: 1 addition & 1 deletion Federated-Deployment/kubernetes/templates/exareme-keystore.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ spec:
app: exareme-keystore
spec:
nodeSelector:
nodeType: master
master: "true"
containers:
- name: exareme-keystore
image: bitnami/consul:1.8.3
Expand Down
4 changes: 2 additions & 2 deletions Federated-Deployment/kubernetes/templates/exareme-master.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ spec:
app: exareme-master
spec:
nodeSelector:
nodeType: master
master: "true"
containers:
- name: exareme-master
image: {{ .Values.exareme_images.repository }}/exareme:{{ .Values.exareme_images.version }}
Expand Down Expand Up @@ -61,4 +61,4 @@ spec:
- protocol: TCP
port: 9090
targetPort: 9090
nodePort: 30000
nodePort: 31000
2 changes: 1 addition & 1 deletion Federated-Deployment/kubernetes/templates/exareme-worker.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ spec:
app: exareme-worker
spec:
nodeSelector:
nodeType: worker
worker: "true"
affinity:
podAntiAffinity:
requiredDuringSchedulingIgnoredDuringExecution:
Expand Down