Catalog Details
CATEGORY
deploymentCREATED BY
UPDATED AT
June 19, 2024VERSION
1.0
What this pattern does:
Creates a Kubernetes deployment with two replicas running NGINX containers and a service to expose these pods internally within the Kubernetes cluster. The NGINX containers are configured to listen on port 80, and the service routes traffic to these containers.
Caveats and Consideration:
ImagePullPolicy: In the Deployment spec, the imagePullPolicy is set to Never. This means that Kubernetes will never attempt to pull the NGINX image from a container registry, assuming it's already present on the node where the pod is scheduled. This can be problematic if the image is not present or if you need to update to a newer version. Consider setting the imagePullPolicy to Always or IfNotPresent depending on your deployment requirements. Resource Allocation: The provided manifest doesn't specify resource requests and limits for the NGINX container. Without resource limits, the container can consume excessive resources, impacting other workloads on the same node. It's recommended to define resource requests and limits based on the expected workload characteristics to ensure stability and resource efficiency.
Compatibility:
Recent Discussions with "meshery" Tag
- Jun 18 | Accidently pushed my commit to running PR
- Jun 17 | Error while setting up Meshery Dev Environment in Windows
- Jun 15 | Where I can find the code of Layer5 Cloud ui?
- Jun 13 | Meshery Build and Release Meeting | June 13th 2024
- Jun 10 | Error while setting up local dev environment for docker desktop extension
- Jun 07 | Unable to deploy Meshery Adapters
- Jun 07 | Looking for a meshmate to help me with Docker extension development
- Jun 04 | Error on terminal when I ran `mesheryctl system start`
- Jun 04 | How to setup Meshery Operator for local machine
- Jun 05 | Meshery Development Meeting | July 5th 2024