The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Taints in Kubernetes (K8s)
Taints in Kubernetes are used to control which pods can be scheduled on specific nodes. They act as restrictions placed on nodes, preventing pods from being scheduled unless the pods have matching tolerations. This helps in reserving nodes for specific workloads, improving resource management, and maintaining cluster stability. Taints are especially useful for dedicating nodes to high-priority applications or isolating specialized hardware resources.
Git:https://github.com/abdur-rehman-tech/taint-tolerations-k8s
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
KUDLA 🐾
Kyiv, Ukraine · One-woman pet grooming studio
The problem: Marta handles every booking, message and schedule change herself, so even a simple customer enquiry can turn into hours of manual work.
The build: KUDLA is an AI-assisted booking and studio management system designed around how a solo groomer actually works.
Instead of a traditional booking form, clients simply chat with Pip. They can send a photo, describe what they need, get an estimated duration and price, see only the available slots that fit, and confirm the appointment — with no extra work for the owner.
On Marta's side, Pip handles the follow-through: rescheduling, client communication, filling cancelled slots and keeping a record of every message. Marta stays in control and approves changes before anything is sent.
❗ The system also reflects a reality specific to running a business in Kyiv. When an air-raid alert interrupts the day, Marta can pause the schedule, prepare the right messages for affected clients, and rebuild the remaining appointments around the time left — including prioritising an animal whose groom was interrupted.
KUDLA isn't another calendar. It's an AI layer that helps a one-person studio keep running when the owner is busy — or when the day doesn't go to plan.
Try the build
Customer experience:
https://kudla-grooming.lovable.app/
Owner system:
https://kudla-grooming.lovable.app/signin
Click “Sign in as owner” — no credentials required.
You did so great! Very inspiring example :)
An alert fired for a scheduled maintenance window.
The monitoring didn't know a planned deploy was happening. False alarm, but it eroded trust in the alerts fast. Now it checks the maintenance calendar before it ever pages anyone.
→ An alert system needs context, not just a raw signal.
Adding the calendar check cuts the noise before a page goes out, so the team can trust alerts again.
How a small glitch gets caught before it becomes downtime:
1. Checks run continuously across the systems that matter
2. An anomaly gets detected against normal baseline behavior
3. The team gets alerted with context, not just a red light
→ Want this monitoring your systems? Happy to set it up.
Continuous checks that flag anomalies before they snowball act as a solid safety net. Context rich alerts cut the noise and speed up response.