I’ve an existing cluster. To create a cluster on local machine I would recommend using Kind

Install using helm

kubectl create namespace rabbitmq
helm repo add bitnami https://charts.bitnami.com/bitnami
helm install myrmq bitnami/rabbitmq --namespace rabbitmq


RabbitMQ can be accessed within the cluster on port `5672` at `myrmq-rabbitmq.rabbitmq.svc`.

Username : user

Password : kubectl get secret --namespace rabbitmq myrmq-rabbitmq -o jsonpath="{.data.rabbitmq-password}" | base64 --decode

ErLang Cookie : kubectl get secret --namespace rabbitmq myrmq-rabbitmq -o jsonpath="{.data.rabbitmq-erlang-cookie}" | base64 --decode


# Run a debug pod
kubectl run -i --tty --rm debug --image=python:3.10-slim-bullseye --restart=Never -- bash
pip3 install pika# Type python for replpython

# Inside the repl
import pika
credentials = pika.PlainCredentials('user', '<password from credentials above>')
parameters = pika.ConnectionParameters('myrmq-rabbitmq.rabbitmq.svc',5672,'/',credentials)
connection = pika.BlockingConnection(parameters)
channel = connection.channel()
hello_q = channel.queue_declare(queue='hello')
body='Hello W0rld!')



Not able for find springboot jar file when running helm chart for kubernetes pod (deployment) (though the docker container has a copy jar)

use this pattern

- "java"
- "@/opt/foo/ce/conf/stage/java.options"
- "-jar"
- "/opt/foo/ce/ce.jar"
- "--logging.config=/opt/foo/ce/conf/stage/logback.xml"



Forget the past and focus on the present. If you don’t like the present, focus on the future.

If a man in line behind you at the convenience store buys a lottery ticket and wins a million dollars, do you kick yourself for not buying that ticket when it was your turn in line? Life is chaos; pretending things like this are in your control is useless. Punishing yourself for not knowing what you didn’t know in the past is cruel.

Your misery comes from your own self-imprisonement. Happiness will not come from a time machine. Rather you should work on keeping your ego out of the driver’s seat.