liveBook · Manning

Component specification

As explained in Machine Learning Platform Engineering

A component specification is a declarative definition of a pipeline component's inputs, outputs, container image, command, and arguments.

A component specification is a YAML contract that makes a containerized pipeline step usable by Kubeflow. It declares the component name, inputs, outputs, data types, container image, command, and argument bindings. section 5.1.1

Read data from MinIO

A read component downloads a Parquet file from MinIO, writes a processed dataset path, and exposes that path as a Dataset output. Its specification invokes the packaged Python entry point and binds storage parameters to declared inputs.

How Machine Learning Platform Engineering covers it

How deep it goes
Explains YAML fields, container commands, argument bindings, and artifact typing, while deferring broader pipeline orchestration.
Examples
Uses read-data, feature-retrieval, inference, and write-data components backed by Docker images and YAML definitions.
What it assumes
Assumes Python component code and Docker packaging, while demonstrating the specification interface from its YAML fields.
What you can do after
Builds a containerized component and applies its specification in a Kubeflow pipeline.
How it connects
Connects Docker, YAML, Kubeflow pipelines, Dataset artifacts, MinIO, Feast, and MLflow.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Machine Learning Platform Engineering. The section links point to the parts of the book it draws on.