Read the source code the get an idea of how the kubelet works and make maybe some contributions
[x] Understand authentication flow (bootstrap token, certificates and basic auth) #27 => Krustlet uses bootstrap token from bootstrap.conf and saves TLS certs for future communication
[x] Understand the kubelet API and how it communicates with the k8s server => It uses an "informer" which listens for pod updates from the server and forwards them to the runtime Provider.
Technically Krustlet spawns an informer which listens for pod updates and forwards them to a queue. The queue uses pattern matching to handle the event (e.g. Apply, Delete). That is, it both handles the state transition of the pod via the runtime Provider and patches the server via the OCI client.
[x] Understand how the WASM runtime works => The runtime Provider is activated by Krustlet and handles different aspects of the pod. Default implementations are available to handle common scenarios.
Image pulling
Volume mounting
Logs
[x] How WASM images are distributed #24
[x] Maybe contribute with a way to simplify authentication with k3s via only a token and random password The k3s auth flow is custom and not standard in k8s. It doesn't make sense to make a PR.
Read the source code the get an idea of how the kubelet works and make maybe some contributions
Apply, Delete). That is, it both handles the state transition of the pod via the runtime Provider and patches the server via the OCI client.Maybe contribute with a way to simplify authentication with k3s via only a token and random passwordThe k3s auth flow is custom and not standard in k8s. It doesn't make sense to make a PR.