[Attacknet] We're trying to use chaos-mesh against a kubernetes workload deployed by Kurtosis. Chaos-mesh can target pods based on the pods name, labels, annotations, and fields.
We have a use case where we want to be able to target a subset of pods with a chaos-mesh fault, such as targeting all prysm pods in an ethereum devnet, or targeting based off some other criteria.
Without this additional metadata, we will have to encode the metadata into pod names and try to extract it on the fly.
Desired behaviour
Update the Plan.add_service/Plan.add_services API to accept a key/value dict of metadata. This metadata should be attached to kubernetes pods as labels. I think docker has a label abstraction that this can apply to as well.
Example:
we call Plan.add_service with a metadata dict of the following:
Background & motivation
[Attacknet] We're trying to use chaos-mesh against a kubernetes workload deployed by Kurtosis. Chaos-mesh can target pods based on the pods name, labels, annotations, and fields.
We have a use case where we want to be able to target a subset of pods with a chaos-mesh fault, such as targeting all prysm pods in an ethereum devnet, or targeting based off some other criteria.
Without this additional metadata, we will have to encode the metadata into pod names and try to extract it on the fly.
Desired behaviour
Update the Plan.add_service/Plan.add_services API to accept a key/value dict of metadata. This metadata should be attached to kubernetes pods as labels. I think docker has a label abstraction that this can apply to as well.
Example: we call Plan.add_service with a metadata dict of the following:
When Kurtosis spins up the pod for the service, it would contain the following additional labels:
How important is this to you?
Nice to have; this feature would make using Kurtosis more enjoyable.
What area of the product does this pertain to?
Other: anything not covered by the above