Package: hikaru
Version 1.3.0Try it: see Hikaru convert your K8s YAMLRelease notesFull documentation at Read the DocsHikaru is a collection of tools that allow you to work with Kubernetes resources from within Python in
a variety of ways:Hikaru provides type-annotated classes that model all of the Kubernetes resources in Python
and supports CRUD operations on those classes to manage their lifecycle in your Kubernetes cluster.Hikaru also provides tooling to shift formats for these objects, allowing you to turn K8s YAML
into Python objects, JSON, or Python dicts, and vice-versa. It can also generate Python source code for K8s
objects loaded from non-Python sources.Hikaru also supports a number of features that aid in the management of
your objects such as searching for specific fields or diffing two instances of a K8s resource.Hikaru includes support for creating ‘watches’ on your objects, providing a means to monitor events
on your provisioned K8s resources.Hikaru provides support for creation of CRDs which support all the above features such as CRUD operations
and watches.Finally, Hikaru includes a facility to specify a collection of
resources as an ‘application’, similar in spirit to a Helm chart, and provides the same CRUD,
watch, and management capabilities on the entire application as it does on single resource objects
(full format shifting support to come).Thishikarupackage is a meta-package that has as dependencies:hikaru-corefor core Hikaru capabilitieshikaru-codegenfor generating formatted Python source from Hikaru objectsThe four most recenthikaru-model-*packages, currently:25.x26.x27.x28.xSee each package’s specific PyPI page for any details on that package.While you can continue to use this meta-package as before, we suggest you migrate to using the model
versions that match the version of the Kubernetes API you need to interact with. This package just helps
make that smoother.From PythonHikaru uses type-annotated Python dataclasses to represent each of the
kinds of objects defined in the Kubernetes API, so when used with an
IDE that understands Python type annotations, Hikaru enables the IDE to
provide the user direct assistance as to what parameters are available,
what type each parameter must be, and which parameters are optional. Assembled
Hikaru object can be rendered into YAML that can be processed by regular
Kubernetes tools.From YAMLBut you don’t have to start with authoring Python: you can use Hikaru to
parse Kubernetes YAML into these same Python objects, at which point you
can inspect the created objects, modify them and re-generate new YAML,
or even have Hikaru emit Python source
code that will re-create the same structure but from the Python
interface.From JSONYou can also process JSON or Python dict representations of Kubernetes configs
into the corresponding Python objectsTo YAML, Python, or JSONHikaru can output a Python Kubernetes object as Python source code,
YAML, JSON, or a Python dict, and go back to any of these representations, allowing you
to shift easily between representational formats for various purposes.Supports multiple versions of KubernetesHikaru allows you to use multiple releases of the Kubernetes client, providing
appropriate bindings/methods/attributes for every object in each version of a
release.Direct Kubernetes via CRUD or low-level methodsYou can use Hikaru objects to interact with a Kubernetes system. Hikaru wraps the Kubernetes
Python client and maps API operations on to the Hikaru model they involve. For example, you
can now create a Pod directly from a Pod object. Hikaru supports a higher-level CRUD-style
set of methods as well as all the operations defined in the Swagger API specification.Hikaru can work with any Kubernetes-compliant system such asK3sandminikube.Monitor Kubernetes activities with watchesHikaru provides an abstraction on over the K8swatchAPIs, which allow you to easily
create code that receives events for all activites carried out in your K8s cluster on
a per-kind basis. Or, you can create a watch container that multiplexes the output
from individual watches into a single stream.Create Custom Resource DefinitionsAs of release 1.0.0, Hikaru supports the creation of CRDs that integrate with the rest
of Hikaru. Automatically generate schema from a Hikaru class, define CRDs to
Kubernetes, manage CRD instances with CRUD methods, and create watchers that allow
you to build your own controllers for your CRDs.Model entire applicationsHikaru provides an Application base class that can be derived from to allow the creation
of sets of resources that comprise the infra for an application system. This Application model
can be inspected, provisioned into a cluster, read from a cluster, and watched, just like
with individual Hikaru K8s objects.Integrate your own subclassesYou can not only in create your own subclasses of Hikaru document classes for your own
use, but you can also register these classes with Hikaru and it will make instances
of your classes when Hikaru encounters the relevantapiVersionandkindvalues. So for example, you can create your ownMyPodsubclass ofPod, and
Hikaru will instantiate your subclass when reading Pod YAML.Alternative to templating for customisationUsing Hikaru, you can assemble Kubernetes objects using previously
defined libraries of objects in Python, craft replacements procedurally, or
even tweak the values of an existing object and turn it back into YAML.Build models for uses other than controlling systemsYou can use Hikaru in the process of issuing instructions to Kubernetes,
but the same Hikaru models can be used as high-fidelity replicas of the
YAML for other processes as well.Type checking, diffing, merging, and inspectionHikaru supports a number of other operations on the Python objects it defines. For
example, you can check the types of all attributes in a config against the defined
types for each attribute, you can diff two configs to see where they aren’t the same,
and you can search through a config for specific values and contained objects.API coverageHikaru supports all objects in the OpenAPI swagger spec for
the Kubernetes APIv 1.26, and has initial support for methods on those objects
from the same swagger spec. Additionally, it defines some higher-level CRUD-style
methods on top of these foundation methods.Usage examplesTo create Python objects from a Kubernetes YAML source, useload_full_yaml():fromhikaruimportload_full_yaml# or just 'from hikaru import *'docs=load_full_yaml(stream=open("test.yaml","r"))p=docs[0]load_full_yaml()loads every Kubernetes YAML document in a YAML file and returns
a list of the resulting Hikaru objects found. You can then use the YAML
property names to navigate the resulting object. If you assert that an
object is of a known object type, your IDE can provide you assistance in
navigation:fromhikaru.model.rel_1_16importPodassertisinstance(p,Pod)print(p.metadata.labels["lab2"])print(p.spec.containers[0].ports[0].containerPort)fork,vinp.metadata.labels.items():print(f"key:{k}value:{v}")You can create Hikaru representations of Kubernetes objects in Python:fromhikaru.model.rel_1_16importPod,PodSpec,Container,ObjectMetax=Pod(apiVersion='v1',kind='Pod',metadata=ObjectMeta(name='hello-kiamol-3'),spec=PodSpec(containers=[Container(name='web',image='kiamol/ch02-hello-kiamol')]))…and then render it in YAML:fromhikaruimportget_yamlprint(get_yaml(x))…which yields:---apiVersion:v1kind:Podmetadata:name:hello-kiamol-3spec:containers:-name:webimage:kiamol/ch02-hello-kiamolIf you use Hikaru to parse this back in as Python objects, you can then
ask Hikaru to output Python source code that will re-create it (thus
providing a migration path):fromhikaruimportget_python_source,load_full_yamldocs=load_full_yaml(path="to/the/above.yaml")print(get_python_source(docs[0],assign_to='x',style="black"))…which results in:x=Pod(apiVersion="v1",kind="Pod",metadata=ObjectMeta(name="hello-kiamol-3"),spec=PodSpec(containers=[Container(name="web",image="kiamol/ch02-hello-kiamol")]),)…and then turn it into real Kubernetes resources using the CRUD methods:x.create(namespace='my-namespace')…or read an existing object back in:p=Pod().read(name='hello-kiamol-3',namespace='my-namespace')…or use a Hikaru object as a context manager to automatically perform updates:withPod().read(name='hello-kiamol-3',namespace='my-namespace')asp:p.metadata.labels["new-label"]='some-value'# and other changes# when the 'with' ends, the context manager sends an update()It is entirely possible to load YAML into Python, tailor it, and then
send it back to YAML; Hikaru can round-trip YAML through Python and
then back to the equivalent YAML.The pieces of complex objects can be created separately and even stored
in a standard components library module for assembly later, or returned as the
value of a factory function, as opposed to using a templating system to piece
text files together:fromcomponent_libimportweb_container,lb_containerfromhikaru.model.rel_1_16importPod,ObjectMeta,PodSpec# make an ObjectMeta instance here called "om"p=Pod(apiVersion="v1",kind="Pod",metadata=om,spec=PodSpec(containers=[web_container,lb_container]))You can also transform Hikaru objects into Python dicts:frompprintimportpprintpprint(get_clean_dict(x))…which yields:{'apiVersion':'v1','kind':'Pod','metadata':{'name':'hello-kiamol-3'},'spec':{'containers':[{'image':'kiamol/ch02-hello-kiamol','name':'web'}]}}…and go back into Hikaru objects. You can also render Hikaru objects as
JSON:fromhikaruimport*print(get_json(x))…which outputs the similar:{"apiVersion":"v1","kind":"Pod","metadata":{"name":"hello-kiamol-3"},"spec":{"containers":[{"name":"web","image":"kiamol/ch02-hello-kiamol"}]}}Hikaru lets you go from JSON back to Hikaru objects as well.Hikaru objects can be tested for equivalence with ‘==’, and you can also
easily create deep copies of entire object structures with dup(). This
latter is useful in cases where you have a component that you want to
use multiple times in a model but need it slightly tweaked in each use;
a shared instance can’t have different values at each use, so it’s easy
to make a copy that can be customised in isolation.Finally, every Hikaru object that holds other properties and objects
have methods that allow you to search the entire collection of objects.
This lets you find various objects of interest for review and checking
against policies and conventions. For example, if we had a Pod ‘p’ that was
pulled in with load_full_yaml(), we could examine all of the Container objects
with:containers=p.find_by_name("containers")forcincontainers:# check what you want...Or you can get all of the ExecAction object (the value of ‘exec’
properties) that are part the second container’s lifecycle’s httpGet
property like so:execs=p.find_by_name("exec",following='containers.1.lifecycle.httpGet')These queries result in a list ofCatalogEntryobjects, which are
named tuples that provide the path to the found element. You can acquire
the actual element for inspection with theobject_at_path()method:o=p.object_at_path(execs[0].path)This makes it easy to scan for specific items in a config under
automated control.Future workWith basic support of managing Kubernetes resources in place, other directions
are being considered such as event/watch support and bringing in support for
additional releases of Kubernetes.AboutHikaru is Mr. Sulu’s first name, a famed fictional helmsman.