Feature(update lab): Add kn func

[jkeam]

Add kn func

1. Update code fence blocks with valid language syntax, such as json, yaml, or shell. https://github.com/github/linguist/blob/master/lib/linguist/languages.yml
2. Add kn func lab

[dudash]

Looks good - but 2 questions. 1 - should we break func stuff out into a separate lab? Like 1.5? Just asking, seems like it be fine either way. 2 - do we have to force them to create quay.io account? That seems a bit complicated for a developer. And if the answer is yes, maybe we have them do that before the workshop starts in like a setup lab so as not to muddy the waters in the dev labs...

[jkeam]

Looks good - but 2 questions. 1 - should we break func stuff out into a separate lab? Like 1.5? Just asking, seems like it be fine either way. 2 - do we have to force them to create quay.io account? That seems a bit complicated for a developer. And if the answer is yes, maybe we have them do that before the workshop starts in like a setup lab so as not to muddy the waters in the dev labs...

For 1, ya I thought about that too and seems like both approaches make sense. I'm ok with either and don't feel passionate either way.

And for 2 every tutorial I've seen requires you to have access to an image repository. I was actually digging around in the source code for kn func and looks like it's an unavoidable step when deploying. https://github.com/boson-project/func/blob/923c788f4a21ec7c109388105ec9b513d9511a48/cmd/deploy.go#L107

[theckang]

I feel like I'm turning in the "homeroom police" so apologies :)

docker and podman are not in the homeroom image. So users won't be able to login to their registries. kn func build will fail too since it will look for a docker runtime for build.

Not sure how I feel - do you think the extra effort required (adding podman to our Dockerfile, making sure our workshop participants sign up for quay in advance) is worth it to showcase kn func?

Update: Actually, the more I think about it, this might be much harder to do. This would require docker in docker which we probably want to avoid.

[jkeam]

I feel like I'm turning in the "homeroom police" so apologies :)

docker and podman are not in the homeroom image. So users won't be able to login to their registries. kn func build will fail too since it will look for a docker runtime for build.

Not sure how I feel - do you think the extra effort required (adding podman to our Dockerfile, making sure our workshop participants sign up for quay in advance) is worth it to showcase kn func?

Update: Actually, the more I think about it, this might be much harder to do. This would require docker in docker which we probably want to avoid.

Def a great point. I'm ok with dropping this for now? Maybe we include a "you can also check this thing kn func out, read more about it here"

[jkeam]

Looks good - but 2 questions. 1 - should we break func stuff out into a separate lab? Like 1.5? Just asking, seems like it be fine either way. 2 - do we have to force them to create quay.io account? That seems a bit complicated for a developer. And if the answer is yes, maybe we have them do that before the workshop starts in like a setup lab so as not to muddy the waters in the dev labs...

For 1, ya I thought about that too and seems like both approaches make sense. I'm ok with either and don't feel passionate either way.

And for 2 every tutorial I've seen requires you to have access to an image repository. I was actually digging around in the source code for kn func and looks like it's an unavoidable step when deploying. https://github.com/boson-project/func/blob/923c788f4a21ec7c109388105ec9b513d9511a48/cmd/deploy.go#L107

Moved instructions to beginning of workshop.

[jkeam]

Going to close this PR as per the discussion here but leaving this branch open in case we ever want to revisit this and use some of the content that I've written.