This controller watches for nfs file shares in Gcore Cloud project and deploy storage classes and provisioner controller for each of them
Gcore SFS Controller allows us to integrate our File Share Servers with the Kubernetes cluster automatically. When you create File Share and give access to your Kubernetes cluster, the controller configures a storage class for your k8s cluster and installs the nfs provisioner.
You’ll need a Kubernetes cluster to run against. You can use KIND to get a local cluster for testing, or run against a remote cluster.
Note: Your controller will automatically use the current context in your kubeconfig file (i.e. whatever cluster kubectl cluster-info
shows).
kubectl apply -f example/deploy/gcore-sfs-controller-install.yaml
-
You must fill in the next values:
spec: apiToken: <put your api token here> region: <put your region id here> project: <put your project id here>
apiToken
: Create API token in CLOUD UI.region
: You can get a region id from our API: You will get a list of regions from the "v1/regions" handler, and then you can find the needed region by the "display_name" field. -
Install CRD
kubectl apply -f example/deploy/nfsprovisioner.yaml
Now, you can create a File Share and the controller configures a storage class and installs the nfs-provisioner automatically.
- Install Instances of Custom Resources:
kubectl apply -f config/samples/
- Build and push your image to the location specified by
IMG
:
make docker-build docker-push IMG=<some-registry>/gcore-sfs-controller:tag
- Deploy the controller to the cluster with the image specified by
IMG
:
make deploy IMG=<some-registry>/gcore-sfs-controller:tag
To delete the CRDs from the cluster:
make uninstall
UnDeploy the controller from the cluster:
make undeploy
// TODO(user): Add detailed information on how you would like others to contribute to this project
This project aims to follow the Kubernetes Operator pattern.
It uses Controllers, which provide a reconcile function responsible for synchronizing resources until the desired state is reached on the cluster.
- Install the CRDs into the cluster:
make install
- Run your controller (this will run in the foreground, so switch to a new terminal if you want to leave it running):
make run
NOTE: You can also run this in one step by running: make install run
If you are editing the API definitions, generate the manifests such as CRs or CRDs using:
make manifests
NOTE: Run make --help
for more information on all potential make
targets
More information can be found via the Kubebuilder Documentation