52c5aedc63
'make manifests' attempts to generate all airshipctl API types,
but several types throw errors and the resulting CRDs can't be
properly generated. This change:
- updates the controller-gen version to pull in a bug fix for the
error 'map values must be a named type, not *ast.StarExpr'
- modifies the Templater type's Values member to be of type JSON
since controller-gen does not support map[string]interface{},
and unmarshals it separately in the templater itself
- adds 'image_repositories' to the VersionsCatalogueSpec struct
to ensure it doesn't get deleted from the schema when manifests
get regenerated
- checks in generated copies of all CRDs from airshipctl's API
types, not just catalogues, to be used for validation
Closes: #574
Change-Id: I89a12cfd307a08da9aaec9773eac01169ea43ace
Airshipctl
Airshipctl is a command-line interface that enables users to manage declarative infrastructure and software.
Airshipctl aims to provide a seamless experience for operators wishing to leverage the best open source options such as the Cluster API, Metal Kubed, Kustomize, and kubeadm by providing a straight forward and easily approachable interface.
This project is the heart of our effort to produce Airship 2.0, which has three main evolutions from Airship 1.0:
- Expand our use of entrenched upstream projects.
- Embrace Kubernetes Custom Resource Definitions (CRD) – everything becomes an object in Kubernetes.
- Make the Airship control plane ephemeral.
To learn more about the Airship 2.0 evolution, reference the Airship blog series.
Contributing
Airshipctl is under active development and welcomes new developers! Please read our developer guide to begin contributing.
We also encourage new contributors and operators alike to join us in our Slack workspace and subscribe to our mailing lists.
You can learn more about Airship on the Airship wiki.