I'm going through it now and it's particularly clunky but can easily be improved - I'd rather set a bunch of variables once, have the variables be passed through to the yaml (under a templates folder perhaps), and be good to go - or simply move everything I need to apply to be under the one folder (instead of docs) and everything to change goes in another.
One fancy approach would be to have a bash script, a variables file, and then do some sedding instead of having users replace xxx in six files.
Tidy the documentation up and make it as short, clean, and, in one go, kubectl applyable as possible, perhaps using tkn
I'm going through it now and it's particularly clunky but can easily be improved - I'd rather set a bunch of variables once, have the variables be passed through to the yaml (under a
templatesfolder perhaps), and be good to go - or simply move everything I need to apply to be under the one folder (instead ofdocs) and everything to change goes in another.One fancy approach would be to have a bash script, a variables file, and then do some sedding instead of having users replace
xxxin six files.Tidy the documentation up and make it as short, clean, and, in one go,
kubectl applyable as possible, perhaps using tkn