The presentation discusses the challenges of identifying types in a Kubernetes cluster and proposes a solution using package revisions and content addressability of OCI images.
- Identifiers of types in a Kubernetes cluster are mostly meaningless outside of a single physical cluster
- Types are not portable and can't be moved across clusters with a guarantee that the syntax has the same semantics
- Behavior is attached to types in both imperative and declarative programming models
- Package revisions and content addressability of OCI images can be used to expand the definition of types and include their behavior
- The demo shows the installation of a type using package revisions and dependencies