Feature Overview

Installing kata on Kubernetes manually is a tedious task, it involves multiples steps ranging from installation of packages, CRI runtime (e.g., CRI-O) configuration on the node, creating the runtime class, and so on. In an effort to make that simpler and to also provide support for bringing in Kata on Openshift, an operator was created that would take care of automating and reconciling all these mundane tasks in a declarative manner on-demand.

This feature covers all the efforts required to enable the operator and make it available for consumption, whether this is testing, packaging, lifecycle or publishing.

For reference: https://github.com/openshift/kata-operator

Background, and strategic fit

The operator is a key interface for Kata consumption, as a result, it could help a lot with the adoption of the Sandboxed Containers RH Product on Openshift serving key-customers.

Goals

• Have the operator installable/upgradable/un-installable
  • Meet OLM Operator requirements https://docs.engineering.redhat.com/display/CFC/Best_Practices 
• Provide all the packages required for use by the operator with the correct Kata version.
  • Identify and address gaps for package installation following the OS extensions mechanism.
• Have the operator published in the RH market place and upstream.
• Handle KataConfiguration scenarios such as:
  • Cluster-upgrades and upgrades to cluster binaries
  • Node selection, scheduling, node-pinning, ..

I.e., Perfect the wolf-palm.

Documentation Considerations

Questions to be addressed:

• What educational or reference material (docs) is required to support this product feature? For users/admins? Other functions (security officers, etc)?
• Does this feature have doc impact?
• New Content, Updates to existing content, Release Note, or No Doc Impact
• If unsure and no Technical Writer is available, please contact Content Strategy.
• What concepts do customers need to understand to be successful in [action]?
• How do we expect customers will use the feature? For what purpose(s)?
• What reference material might a customer want/need to complete [action]?
• Is there source material that can be used as a reference for the Technical Writer in writing the content? If yes, please link if available.
• What is the doc impact (New Content, Updates to existing content, or Release Note)?