The workload operator defines APIs and core controllers for interacting with compute infrastructure related entities such as Workloads and Instances.
Workload and Instance API types include references to types defined in the network-services-operator project, such as Networks and Network Policies, in order to attach to networks or influence instance network connectivity.
The operator itself is not responsible for provisioning of resources, but instead relies on infrastructure providers such as the GCP Infrastructure Provider to interact with vendor or platform specific APIs in order to satisfy the intents defined in custom resources
See the Workloads RFC for details on the goals of this project.
Documentation will be available at docs.datum.net shortly.
- go version v1.23.0+
- docker version 17.03+.
- kubectl version v1.31.0+.
- Access to a Kubernetes v1.31.0+ cluster.
Build and push your image to the location specified by IMG:
make docker-build docker-push IMG=<some-registry>/tmp:tagNOTE: This image ought to be published in the personal registry you specified. And it is required to have access to pull the image from the working environment. Make sure you have the proper permission to the registry if the above commands don’t work.
Install the CRDs into the cluster:
make installDeploy the Manager to the cluster with the image specified by IMG:
make deploy IMG=<some-registry>/tmp:tagNOTE: If you encounter RBAC errors, you may need to grant yourself cluster-admin privileges or be logged in as admin.
Create instances of your solution You can apply the samples (examples) from the config/sample:
kubectl apply -k config/samples/NOTE: Ensure that the samples has default values to test it out.
Delete the instances (CRs) from the cluster:
kubectl delete -k config/samples/Delete the APIs(CRDs) from the cluster:
make uninstallUnDeploy the controller from the cluster:
make undeployNOTE: Run make help for more information on all potential make targets
More information can be found via the Kubebuilder Documentation