Being charged for inaccessible pod
When I create a pod, I start getting charged even if it's not yet accessible. I was told that charges only start once the pod is fully connectable, but that's clearly not the case now. Why is everything so inconsistent and misleading? Is this a bug, or is this how it's actually supposed to work?
4 Replies
Just to clarify: the pod is still in the process of downloading the Docker image — it hasn't even started extracting yet.
And there is no uptime status obviously.
it should be like this
pulling your docker image: no charge
image starts (the host executed the CMD you provided): charge
so if your docker image takes time to do some stuff and be available
that time is charged
if this is true you should contact support for a refund
on pods pulling is charged
who told you the pod is fully connectable?