- Introduce podAntiAffinity settings to avoid scheduling
multiple Pods with the same app: taw label on the same
node.
- This is a soft requirement, meaning that if there are
not enough nodes, Pods may still be scheduled on the
same node.
This change enhances the deployment strategy by improving
availability and fault tolerance of the taw application.
- Change the number of replicas from 1 to 3 in the
deployment configuration.
- This adjustment aims to improve load balancing and
availability of the application.
Increasing the replicas allows the application to handle
more traffic and provides redundancy in case of failures.
- Change kind from DaemonSet to Deployment
- Uncomment replicas setting to ensure proper scaling
This change corrects the resource type for the application
in the Kubernetes configuration, ensuring it is deployed as a
Deployment instead of a DaemonSet. This allows for better
management of replicas and scaling capabilities.
- Change kind from Deployment to DaemonSet
- Remove previous node selector configuration
- Add tolerations for scheduling restrictions
- Introduce node affinity for specific hostnames
These changes facilitate deployment across all nodes instead of a single replica,
allowing for improved resource utilization and management in the
Kubernetes environment.
