Hi Devs,

I have now fixed the kubernetes pod id issue in the master branch, earlier
we used member id as the pod id and the pod id became too long after
appending application id to member id.

Now the Kubernetes pod and service ids are generated using sequence numbers
and they are stored against the kubernetes cluster context:

*Format:*
pod-<kubernetes-cluster-pod-sequence-no>
service-<kubernetes-cluster-service-sequence-no>

Sequence numbers are generated using AtomicLong, and they can go up to 263-1
per kubernetes cluster.

Thanks

-- 
Imesh Gunaratne

Technical Lead, WSO2
Committer & PMC Member, Apache Stratos

Reply via email to