kopf
kopf copied to clipboard
nolar
A Python framework to write Kubernetes operators in just a few lines of code
## Question I have a CRD with a state machine that is a super set of what kubernetes provides, so my intention is to formalize all states and transitions using...
## Question ### Context I have an operator that is managed by a non-declarative API that acts like a compatibility layer with a legacy, non kubernetes, execution model. Today the...
## Long story short Don't know if it is a problem of kubectl or of kopf itself. ## Description I'm creating a pod using this: ``` kubectl run --image nginx...
## Long story short MODIFIED events on just CREATED resources might arrive before last-handled-configuration was written. This leads to the MODIFIED event being treated as `Reason.CREATE` b/c its `old` version...
operator entered into to a situation where it was not handling any events. that time we noticed following messaged in the log. what might be the reason ? we had...
Context: * Assume that kopf failed to handle the on.create/on.update event (some business logic error). In this case desired state is saved in etcd database, right?. * Later if we...
* Replicaset automatically creates the pod when we delete it * Replicaset also shows status of its pods in the status of the Replicaset How we can implement this using...
**patch.status** call also raising "MODIFIED" event, so I could not find a way to identify only the "MODIFIED" event which happens as part of **spec change**. I am doing **patch.status**...
I have checked: https://github.com/nolar/kopf/issues/112 https://github.com/nolar/kopf/issues/241 Is there any way to resume **only creation/updation failed objects** (or objects not in deployed/created state) on operator restart ?
## Problem After implementing the hotfix offered in #686 of aligning the handler `id=`, I noticed some operator handlers were not firing for certain events. I was kind of lucky...