The priorities of content and modes of use of the workshop should be centered around how EKS customers and users interact with the services.
The modules that make up the core EKS workshop should be focused on features that differentiate EKS from open source or other Kubernetes distributions or offerings. The aim of this workshop is not to provide education on general Kubernetes concepts or wider ecosystem projects unless it is how they specifically intersect with the EKS service.
We aim to develop the workshop content in an open environment as much as possible to promote inclusion and collaboration, whether inside or outside Amazon. This encompasses public access to the content as well as contribution.
It should be possible to run any given set of content modules in any order without dependencies on other modules. This allows modules to be selected “a la carte” and prevents cascading issues between content.
Workshop content that does not function, negatively affects both the confidence of those delivering customer workshops and the public perception of those using the content on their own time. We strive to produce content in a manner that remains stable and functional, and mechanisms that detect issues as early as possible.