litmuschaos
/
litmus
mirror of https://github.com/litmuschaos/litmus.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fixed target port and listen port mentions in http chaos latency (#3663) 

Signed-off-by: avaakash <as86414@gmail.com>
This commit is contained in:
Akash Shrivastava 2022-07-15 19:33:20 +05:30 committed by GitHub
parent 2908008152
commit aba7459fbe
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
mkdocs/docs/experiments/categories/pods/pod-http-latency.md
View File

@ -203,13 +203,13 @@
Refer the [common attributes](../common/common-tunables-for-all-experiments.md) and [Pod specific tunable](common-tunables-for-pod-experiments.md) to tune the common tunables for all experiments and pod specific tunables. Refer the [common attributes](../common/common-tunables-for-all-experiments.md) and [Pod specific tunable](common-tunables-for-pod-experiments.md) to tune the common tunables for all experiments and pod specific tunables.
### Target Port ### Target Service Port
It defines the target port of the service that is being targetted. It can be tuned via `TARGET_SERVICE_PORT` ENV. It defines the target port of the service that is being targetted. It can be tuned via `TARGET_SERVICE_PORT` ENV.
Use the following example to tune this: Use the following example to tune this:
[embedmd]:# (pod-http-latency/target-port.yaml yaml) [embedmd]:# (pod-http-latency/target-service-port.yaml yaml)
```yaml ```yaml
## provide the target port of the service ## provide the target port of the service
apiVersion: litmuschaos.io/v1alpha1 apiVersion: litmuschaos.io/v1alpha1
@ -233,15 +233,15 @@ spec:
- name: TARGET_SERVICE_PORT - name: TARGET_SERVICE_PORT
value: "80" value: "80"
``` ```
### Listen Port ### Proxy Port
It defines the listen port for the proxy server. It can be tuned via `PROXY_PORT` ENV. It defines the port on which the proxy server will listen for requests. It can be tuned via `PROXY_PORT` ENV.
Use the following example to tune this: Use the following example to tune this:
[embedmd]:# (pod-http-latency/listen-port.yaml yaml) [embedmd]:# (pod-http-latency/proxy-port.yaml yaml)
```yaml ```yaml
## provide the listen port for proxy # provide the port for proxy to listen on
apiVersion: litmuschaos.io/v1alpha1 apiVersion: litmuschaos.io/v1alpha1
kind: ChaosEngine kind: ChaosEngine
metadata: metadata:
@ -259,7 +259,7 @@ spec:
spec: spec:
components: components:
env: env:
# provide the listen port for proxy # provide the port for proxy to listen on
- name: PROXY_PORT - name: PROXY_PORT
value: '8080' value: '8080'
# provide the target port of the service # provide the target port of the service

4
mkdocs/docs/experiments/categories/pods/pod-http-latency/listen-port.yaml → mkdocs/docs/experiments/categories/pods/pod-http-latency/proxy-port.yaml
View File

@ -1,4 +1,4 @@
## provide the listen port for proxy # provide the port for proxy to listen on
apiVersion: litmuschaos.io/v1alpha1 apiVersion: litmuschaos.io/v1alpha1
kind: ChaosEngine kind: ChaosEngine
metadata: metadata:
@ -16,7 +16,7 @@ spec:
spec: spec:
components: components:
env: env:
# provide the listen port for proxy # provide the port for proxy to listen on
- name: PROXY_PORT - name: PROXY_PORT
value: '8080' value: '8080'
# provide the target port of the service # provide the target port of the service

0
mkdocs/docs/experiments/categories/pods/pod-http-latency/target-port.yaml → mkdocs/docs/experiments/categories/pods/pod-http-latency/target-service-port.yaml
View File