Tsung as k8s pod#53
Conversation
| @@ -0,0 +1,33 @@ | |||
| apiVersion: apps/v1 | |||
There was a problem hiding this comment.
How are we going to pass tsung config file to the running container? Are we going to pass it when we are building the container or when we are deploying container?
There was a problem hiding this comment.
It should be passed when deploying the container as a mounted volume
There was a problem hiding this comment.
Yes, but using this yaml file, we are not passing anything when deploying.
There was a problem hiding this comment.
The user doesn't pass the file as a parameter while deploying Tsung. Instead, the path to the conf.xml file should be updated under volumes:hostPath:path.
There was a problem hiding this comment.
If the end user wants to pass different traffic scenario:
1- first discover where the load generator is going to be deployed (specified by k8s scheduler)
2- Then ssh to the node
3- create/update the tsung file under the path!
It makes the whole process of experiments complicated, we could easily pass it as configmap or environment variable.
There was a problem hiding this comment.
Yes, as discussed this will be modified accordingly with either configmap or env variables.
2 participants
This PR generates dockerfile and k8s deployment yaml files for Tsung.
Closes #5