Catalog Details
CATEGORY
deploymentCREATED BY
UPDATED AT
May 28, 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
- Mar 13 | Badge leveling system proposal
- Mar 11 | [Help Wanted] A list of open DevOps-centric needs on Meshery projects
- May 23 | Meshery Build and Release call Meeting minutes (23rd May 2024)
- May 22 | Meshery Development Meeting | May 22nd 2024
- May 20 | New member at Meshery, looking for a MeshMate
- May 19 | Newcomer looking for guidance
- May 17 | Doubt regarding plugins in Meshery UI
- Apr 14 | Unable to deploy meshery to minikube
- May 08 | No reachable contexts found in the uploaded kube config
- May 08 | Meshery Development Meeting | May 8th 2024