[OCTRL-1081] Wrap kubectl into Mesos executor task#805
[OCTRL-1081] Wrap kubectl into Mesos executor task#805justonedev1 wants to merge 3 commits intomasterfrom
Conversation
user infor setup properly... kubectl passes arguments properly to the kubernetes attempt for fairmq bla
| // aux.Control.Mode = "direct" | ||
| // } | ||
|
|
||
| aux.Control.Mode = c.Control.Mode.String() |
There was a problem hiding this comment.
There is a change in behaviour for hooks though, no? Before they were getting direct instead of hook, which actually smells like a bug, but perhaps something is relying on it?
There was a problem hiding this comment.
This is probably my misunderstanding, as I thought that it is a bug to implicitly change hook to direct.. especially when we have hooktask that is created only if controlmode.HOOK is present.
see
docs/kubernetes_ecs.md
Outdated
| While prototyping we used many Kubernetes clusters, namely [`kind`](https://kind.sigs.k8s.io/), [`minikube`](https://minikube.sigs.k8s.io/docs/) and [`k3s`](https://k3s.io/) | ||
| in both local and remote cluster deployment. We used Openstack for remote deployment. | ||
| Follow the guides at the individual distributions in order to create the desired cluster setup. | ||
| For now we chose `k3s` for most of the activities performed because it is lightweight |
There was a problem hiding this comment.
That might give an impression that there was some kind of decision process in ALICE or FLP. Perhaps rephrase to:
k3sis recommended to run this prototype, as it is a lightweight and...
docs/kubernetes_ecs.md
Outdated
| All settings of `k3s` were used as default except one: locked-in-memory size. Use `ulimit -l` to learn | ||
| what is the limit for the current user and `LimitMEMLOCK` inside the k3s systemd service config | ||
| to set it for correct value. Right now the `flp` user has unlimited size (`LimitMEMLOCK=infinity`). | ||
| This config is necessary because even if you are running PODs with the privileged security context |
There was a problem hiding this comment.
| This config is necessary because even if you are running PODs with the privileged security context | |
| This config is necessary because even if you are running Pods with the privileged security context |
It's a detail, but "Pod" and "pod" are likely the correct spellings, since it's a proper English word, not an abbreviation, like "Plain Old Data". I mention this, so that we avoid having someone in ALICE read our documentation and then learn to read it "pee-o-dee".
2 participants
The task description is in the documentation
docs/kubernetes_ecs.md