MOTOSHARE ššļø
Turning Idle Vehicles into Shared Rides & Earnings
From Idle to Income. From Parked to Purpose.
Earn by Sharing, Ride by Renting.
Where Owners Earn, Riders Move.
Owners Earn. Riders Move. Motoshare Connects.
With Motoshare, every parked vehicle finds a purpose.
Owners earn. Renters ride.
š Everyone wins.
- PodsĀ are the smallest deployable units of computing that you can create and manage in Kubernetes.
- AĀ Pod is a group of one or moreĀ containers, with shared storage and network resources, and a specification for how to run the containers.
- a Pod can containĀ init containersĀ that run during Pod startup.
- a Pod is similar to a group of Docker containers with shared namespaces and shared filesystem volumes.
- Some Pods haveĀ init containersĀ as well asĀ app containers. Init containers run and complete before the app containers are started.
- A Pod can specify a set of shared storageĀ volumes. All containers in the Pod can access the shared volumes, allowing those containers to share data.Ā
- Each Pod is assigned a unique IP address for each address family.
- Inside a Pod ., the containers that belong to the Pod can communicate with one another usingĀ localhost
- When containers in a Pod communicate with entitiesĀ outside the Pod, they must coordinate how they use the shared network resources (such as ports)
- any container in a Pod can enable privileged mode using theĀ privilegedĀ (Linux) flag on theĀ security contextĀ of the container spec
- Static PodsĀ are managed directly by the kubelet daemon on a specific node, without theĀ API serverĀ observing them.Ā
- POD cannot be created it can only be instantiated
- No POD is ever redeployed – Ephermal
- Atomicity – they are there or not
- Unit of Scheduling