Feature: black- and whitelisting about chaoskube HOT 8 CLOSED

Hi @eljefedelrodeodeljefe,

that certainly makes sense. Let's collect a list of what would be useful and not too complicated to use and implement.

I can think of

• white- and blacklisting by namespace(s)
• white- and blacklisting by label selector

blacklisting trumps whitelisting, I guess. So pods matching a whitelisted label selector that are in a blacklisted namespace should not be killed.

• by namespaces
• by label selector
• by attributes (#12)

from chaoskube.

I think that concludes it to be lightweight. Sounds good to me.

from chaoskube.

Another possibility is attributes.

from chaoskube.

@kfox1111 want do you have in mind?

something like this maybe:

• all pods with some value for an attribute (e.g. serviceAccountName=default)
• all pods containing at least one container with some value for an attribute (e.g. image=nginx )

from chaoskube.

@eljefedelrodeodeljefe @kfox1111 Label based solution is here: #5. Let me know what you think.

from chaoskube.

@eljefedelrodeodeljefe Namespace-based filtering, both white- and blacklisting supported, no regexp shenanigans: #9 (comment)

from chaoskube.

Label-based and namespace-based selection is part of the v0.4.0 release

I'm going to close this and create a new issue for attribute based filtering: #12

from chaoskube.

thanks @eljefedelrodeodeljefe and @kfox1111 for the suggestions!

from chaoskube.