In this video we first set up a basic understanding of when would we need conversion webhook and that is where we talked about supporting/having a custom resource in more than one API versions.
We also looked into a simple demo of creating a CR from one version (v1alpha1) and checking that we get the same output even if we try to get the resource from another version (v1beta1). Apart from that we looked into the architecture of conversion webhook and also talked about how we can add the deprecation notice on a version of CR.
At the end we very briefly talked about how to configure conversion webhook while creating a CRD.
Web:
viveksingh.dev/
GitHub:
github.com/viveksinghggits/vi...
00:00 Introduction
00:24 Agenda
01:02 Brief look into Kluster CRD
02:03 Need to serve resource from two versions
03:46 Don't drop support for a version suddenly
05:23 Serve a resource from two versions
07:37 Creating resource from non storage version
08:18 Demo, Creating CRD and CRs
11:37 Canonical Versioning while getting a resource
13:00 Response from both the versions
14:13 Why conversion webhooks
15:41 Architecture of conversion webhook
17:45 Configure conversion webhook in your CRD
18:55 Add deprecation warning
21:03 Create resource from non storage version
21:58 Like, Share and Subscribe
28 июн 2024
