https://github.com/larsrh/fizzbuzz-k8s
FizzBuzz on k8s using ingress rules, because why not?
https://github.com/larsrh/fizzbuzz-k8s
Last synced: about 2 months ago
JSON representation
FizzBuzz on k8s using ingress rules, because why not?
- Host: GitHub
- URL: https://github.com/larsrh/fizzbuzz-k8s
- Owner: larsrh
- Created: 2021-01-09T10:24:18.000Z (over 4 years ago)
- Default Branch: main
- Last Pushed: 2022-06-29T12:09:01.000Z (almost 3 years ago)
- Last Synced: 2025-03-22T22:42:32.630Z (2 months ago)
- Language: Shell
- Size: 11.7 KB
- Stars: 17
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# fizzbuzz-k8s
FizzBuzz on k8s using ingress rules, because why not?
## Usage
Deploy all resources with `kubectl apply -f .`.
Try it out:
```
$ for i in `seq 1 20`; do curl -s http:///$i | jq .args.response; done
"1"
"2"
"fizz"
"4"
"buzz"
"fizz"
"7"
"8"
"fizz"
"buzz"
"11"
"fizz"
"13"
"14"
"fizzbuzz"
"16"
"17"
"fizz"
"19"
"buzz"
```
## Why?
Because we can.
## Credits
* https://stackoverflow.com/a/24195550/4776939
* http://blogs.perl.org/users/mauke/2017/08/fizzbuzz.html
* https://regexr.com/
No credits to RE2 because it doesn't accept look-ahead assertions, even though Nginx supports them.