pika-operator is a Kubernetes operator for managing Pika.
This operator is responsible for managing the lifecycle of Pika. It is responsible for creating and managing the following resources:
- StatefulSet
- Service
- PersistentVolumeClaim
You’ll need a Kubernetes cluster to run against. You can use MiniKube or 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).
-
Install MiniKube
-
Start a local cluster:
make minikube-up # run this if you don't have a minikube cluster
make local-deploy
Or if you want to use a development pika image:
make local-deploy PIKA_IMAGE=<your-pika-image>
If you see some message like the following, it means that the pika-operator is running successfully:
************ TEST PIKA ************
kubectl run pika-minikub-test ...
pika_version:3.4.0
pika_git_sha:bd30511bf82038c2c6531b3d84872c9825fe836a
pika_build_compile_date: Dec 1 2020
- 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>/pika-operator:tag
- Deploy the controller to the cluster with the image specified by
IMG
:
make deploy IMG=<some-registry>/pika-operator:tag
- Create a Pika instance:
kubectl apply -f examples/pika-sample/
- Check the status of the Pika instance:
kubectl get pika pika-sample
- Connection to the Pika instance:
kubectl run pika-sample-test --image redis -it --rm --restart=Never \
-- /usr/local/bin/redis-cli -h pika-sample -p 9221 info
To delete the CRDs from the cluster:
make uninstall
UnDeploy the controller to the cluster:
make undeploy
This project is still in its early stages and contributions are welcome. Please feel free to open issues and PRs. Please see this issue to discuss the design of the operator.
This project aims to follow the Kubernetes Operator pattern
It uses Controllers which provides a reconcile function responsible for synchronizing resources untile 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
Copyright 2023.
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.