https://github.com/sverrirab/kube-test-container
Kubernetes Test Container
https://github.com/sverrirab/kube-test-container
docker helm kubernetes testing
Last synced: about 1 year ago
JSON representation
Kubernetes Test Container
- Host: GitHub
- URL: https://github.com/sverrirab/kube-test-container
- Owner: sverrirab
- License: mit
- Created: 2017-01-17T19:03:49.000Z (over 9 years ago)
- Default Branch: master
- Last Pushed: 2019-02-28T20:30:25.000Z (over 7 years ago)
- Last Synced: 2025-03-26T13:53:59.726Z (about 1 year ago)
- Topics: docker, helm, kubernetes, testing
- Language: HTML
- Size: 854 KB
- Stars: 30
- Watchers: 1
- Forks: 9
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Kubernetes Test Container
This is a very simple [](https://microbadger.com/images/sverrirab/kube-test-container:v1.0 "Get your own image badge on microbadger.com") container that you can use to test your [Kubernetes](https://kubernetes.io) cluster.
Simply create a deployment and service with the yaml file:
```bash
kubectl create -f ./kubernetes/kube-test-container.yaml
```
The containers have already been uploaded so you don't need to build anything here. But the full
source is provided here if you want to extend this (Pull Request welcome).
## Scale the deployment
```bash
kubectl scale deployment kube-test-container --replicas=30
```
## Automatic scaling
Turn on automatic scaling with [HPA](https://kubernetes.io/docs/user-guide/horizontal-pod-autoscaling/)
```bash
kubectl autoscale deployment kube-test-container --min=10 --max=20
```
## View the status
```bash
kubectl get deploy,svc kube-test-container
```
## View the status page and generate load
View the external IP Address using the Load Balancer IP `http://IPADDRESS/`. You will see the correct address marked
as `EXTERNAL-IP` in the service status (see above).
If you click the "Let one use too much RAM" `http://IPADDRESS/ram` or "Let one use too much CPU" `http://IPADDRESS/cpu`
to trigger one of the container to use too much RAM / CPU (this will grow unbound).
Click "Fetch multiple status pages" for requesting status `http://IPADDRESS/status`
## External load testing
You can use your favorite benchmarking tool. The simplest for many would be Apache Benchmark:
```bash
ab -n 1000 -c 10 http://IPADDRESS/status
```
## Testing upgrades
There are three different versions of this component that only differ in reporting a different version:
* sverrirab/kube-test-container:v1.0
* sverrirab/kube-test-container:v1.1
* sverrirab/kube-test-container:v1.2
```bash
kubectl set image deployment/kube-test-container kube-test-container=sverrirab/kube-test-container:v1.1
```
## Cleanup
```bash
kubectl delete deploy,svc kube-test-container
```
# Helm installation
For testing your cluster with [Helm](https://github.com/kubernetes/helm):
```bash
helm repo add kube-test-container https://raw.githubusercontent.com/sverrirab/kube-test-container/master/helm/charts/
```
To see available versions:
```bash
helm search --versions kube-test-container
```
And to install:
```bash
helm install --version 1.1.0 --name ktc kube-test-container/kube-test-container
```
# Screenshot
# Building and testing
If you want to make modifications you can use the `./build.sh` script to build a local docker container
and `./run.sh` to test it locally through `http://localhost:8000/`.
# License
MIT License - read the LICENSE file for details.