Currently knctl install does not install any build templates, and both knctl deploy and knctl build create do not use them by default (without --template flag). Instead, they manually construct build steps that mirror an existing template https://github.com/knative/build-templates/tree/master/kaniko
Perhaps we move towards knctl install preinstalling some/all the known build template CRDs, and knctl deploy always using one, e.g. --template kaniko by default.
This would make it easier to explain what the default behavior is - it would show up in knctl deploy --help as the default value for --template flag.
This topic ("what are the default steps?") came up in the comments of one of my blog posts https://starkandwayne.com/blog/build-docker-images-inside-kubernetes-with-knative-build/#comment-4189493232
Currently
knctl installdoes not install any build templates, and bothknctl deployandknctl build createdo not use them by default (without--templateflag). Instead, they manually construct build steps that mirror an existing template https://github.com/knative/build-templates/tree/master/kanikoPerhaps we move towards
knctl installpreinstalling some/all the known build template CRDs, andknctl deployalways using one, e.g.--template kanikoby default.This would make it easier to explain what the default behavior is - it would show up in
knctl deploy --helpas the default value for--templateflag.This topic ("what are the default steps?") came up in the comments of one of my blog posts https://starkandwayne.com/blog/build-docker-images-inside-kubernetes-with-knative-build/#comment-4189493232