Skip to content

FizzBuzz on k8s using ingress rules, because why not?

Notifications You must be signed in to change notification settings

larsrh/fizzbuzz-k8s

Repository files navigation

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://<endpoint>/$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

No credits to RE2 because it doesn't accept look-ahead assertions, even though Nginx supports them.

About

FizzBuzz on k8s using ingress rules, because why not?

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages