Datum GCP Infrastructure Provider

This provider manages resources in GCP as a result of interpreting workload and network related API entities defined by users.

The primary APIs driving resource creation are defined in workload-operator and network-services-operator.

Documentation

Documentation will be available at docs.datum.net shortly.

Design Notes

Instances

Currently this provider leverages GCP Managed Instance Groups to manage instances within GCP. A future update will move toward more direct instance control, as MIG resources and entities such as templates that are required to use them take a considerably longer time to interact with than direct VM instance control.

Getting Started

Prerequisites

• go version v1.23.0+
• docker version 17.03+.
• kubectl version v1.31.0+.
• Access to a Kubernetes v1.31.0+ cluster.

This provider makes use of the GCP Config Connector project to manage resources in GCP. It is expected that the config connector and associated CRDs have been installed in the cluster.

To Deploy on the cluster

Build and push your image to the location specified by IMG:

make docker-build docker-push IMG=<some-registry>/tmp:tag

NOTE: 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 install

Deploy the Manager to the cluster with the image specified by IMG:

make deploy IMG=<some-registry>/tmp:tag

NOTE: 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.

To Uninstall

Delete the instances (CRs) from the cluster:

kubectl delete -k config/samples/

Delete the APIs(CRDs) from the cluster:

make uninstall

UnDeploy the controller from the cluster:

make undeploy

NOTE: Run make help for more information on all potential make targets

More information can be found via the Kubebuilder Documentation