Deploy Dogecoin to k8s

1. Install the storage class for AWS
   • kubectl apply -f immedate-gp2-storageclass.yaml
   • May not be necessary for other cloud providers (gcloud, etc.)
2. Install with overridden rpcPassword
   • helm install dogecoin-<network> . --set rpcPassword=password_test --namespace default
   • Replace <network> wtih testnet or mainnet
   • Use -f values-mainnet.yaml for mainnet
   • Override --set storage.storageClassName=immediate-gp2 for AWS
   • Note: rpcPassword override creates a secret which is copied into the dogecoin.conf when the container starts

Accessing dogecoin-cli via kubectl

kubectl exec dogecoin-testnet-88c4bd4dc-tt85j -- /dogecoin/bin/dogecoin-cli -conf=/tmp/dogecoin.conf getblockchaininfo

• Replace dogecoin-testnet-88c4bd4dc-tt85j with the actual pod from kubectl get pods
• Replace getblockchaininfo wtih any cli command

Testing RPC from another pod

Check the services are running

kubectl get svc

NAME               TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)               AGE
dogecoin-mainnet   ClusterIP   10.100.104.208   <none>        22556/TCP,22555/TCP   20m
dogecoin-testnet   ClusterIP   10.100.108.164   <none>        44556/TCP,44555/TCP   22m

Spin up a debug pod with a terminal

kubectl run -i --tty --rm debug --image=busybox --restart=Never -n default -- sh

Make an RPC from the pod, using the service name and credentials

wget -qO- http://user:password_test@dogecoin-testnet:44555/ --post-data='{"jsonrpc": "1.0", "id":"test", "method": "getblockchaininfo", "params": []}'

Check that you get a valid response

{"result":{"chain":"test","blocks":217339,"headers":3499999,"bestblockhash":"2b175628405541cb5ba1f0329ff73985eab84e5bb94aaeed5b4dded130431434","difficulty":0.0002764590388906048,"mediantime":1412894572,"verificationprogress":0.04991828136432626,"initialblockdownload":true,"chainwork":"000000000000000000000000000000000000000000000000000000e216d503b2","size_on_disk":216713255,"pruned":false,"softforks":[{"id":"bip34","version":2,"reject":{"status":false}},{"id":"bip66","version":3,"reject":{"status":false}},{"id":"bip65","version":4,"reject":{"status":false}}],"bip9_softforks":{"csv":{"status":"defined","startTime":1456790400,"timeout":1493596800,"since":0}},"warnings":""},"error":null,"id":"test"}

Enabling public RPC

1. Make sure you have the nginx ingress helm repo

   helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx
   helm repo update
   

2. Install the nginx controller

   helm upgrade --install ingress-nginx ingress-nginx \
   --namespace ingress-nginx \
   -f ingress-controller-values.yaml
   

   • Note: the values in the repo are specific to AWS
   • On AWS, replace the specific subnets with your VPC public subnets
   • Specific values may not be necessary for other providers

3. Have TLS secret created for the hosts defined in ingress.yaml and install the services-ingress

   kubectl apply -f ingress.yaml
   

4. Test your RPC with a curl request

   curl -u "user:password_test" --data-binary '{"jsonrpc": "1.0", "id":"test", "method": "getblockchaininfo", "params": []}' -H "content-type: application/json" https://testnet.example.com/
   

Enabling incoming p2p traffic

1. Enable p2p in the dogecoinConf section of your values.yaml

   • Use listen: 1

2. Add public hosts to the ingress.yaml which expose the p2p port

   • Default port 22556 for mainnet and 44556 for testnet

3. Apply the ingress.yaml changes

   kubectl apply -f ingress.yaml
   

4. Check your node for incoming traffic using RPC

   curl -u "user:password_test" --data-binary '{"jsonrpc": "1.0", "id":"test", "method": "getconnectioncount", "params": []}' -H "content-type: application/json" https://testnet.example.com/
   

   • result > 8 connections means you have incoming connections
   • Node must be fully synched before incoming connections will appear