k8s-rds
A Custom Resource Definition for provisioning AWS RDS databases.
State: BETA - use with caution
Assumptions
The node running the pod should have an instance profile that allows creation and deletion of RDS databases and Subnets.
The codes will search for the first node, and take the subnets from that node. And depending on wether or not your DB should be public, then filter them on that. If any subnets left it will attach the DB to that.
Building
go build
Installing
You can start the the controller by applying kubectl apply -f deploy/deployment.yaml
RBAC deployment
To create ClusterRole and bindings, apply the following instead:
kubectl apply -f deploy/operator-cluster-role.yaml
kubectl apply -f deploy/operator-service-account.yaml
kubectl apply -f deploy/operator-cluster-role-binding.yaml
kubectl apply -f deploy/deployment-rbac.yaml
Deploying
When the controller is running in the cluster you can deploy/create a new database by running kubectl apply
on the following
file.
apiVersion: v1
kind: Secret
metadata:
name: mysecret
type: Opaque
data:
mykey: cGFzc3dvcmRvcnNvbWV0aGluZw==
---
apiVersion: k8s.io/v1
kind: Database
metadata:
name: pgsql
namespace: default
spec:
class: db.t2.medium # type of the db instance
engine: postgres # what engine to use postgres, mysql, aurora-postgresql etc.
dbname: pgsql # name of the initial created database
name: pgsql # name of the database at the provider
password: # link to database secret
key: mykey # the key in the secret
name: mysecret # the name of the secret
username: postgres # Database username
size: 10 # size in BG
backupretentionperiod: 10 # days to keep backup, 0 means diable
encrypted: true # should the database be encrypted
iops: 1000 # number of iops
multiaz: true # multi AZ support
storagetype: gp2 # type of the underlying storage
After the deploy is done you should be able to see your database via kubectl get databases
NAME AGE
test-pgsql 11h
And on the AWS RDS page
TODO