Code Monkey home page Code Monkey logo

Comments (6)

asobti avatar asobti commented on August 27, 2024

Are you thinking of a scenario where all deployments within the whitelisted namespaces will be enrolled into Kube monkey? We'd have to figure out a way to specify parameters like MTBF etc. in this case.

An alternative way to do that would be instead of opting in deployments, maybe there could be an option to opt-in namespaces instead (by adding the kubernetes labels to them).

In either case, this isn't something that is currently supported. I'll try to take a look, but PRs are also welcome.

from kube-monkey.

EIrwin avatar EIrwin commented on August 27, 2024

We too had discussed the preference of configuring opt-in vs opt-out. The cluster we would like to run this on has feature namespaces provisioned sometimes on daily basis in which case, we likely would not want to disturb those. This would also require us to constantly update the blacklisting of namespaces, versus explicitly saying which namespaces to run it against. I might look into branching off and making it configurable.

from kube-monkey.

asobti avatar asobti commented on August 27, 2024

@EIrwin I'm all for having an opt-in option. I just haven't figured out the best way to handle configurations like MTBF etc in this case. Perhaps we could use a system where you globally set the mode to opt-in and specify some global value for MTBF. individual deployments can then override this value.

I'll take a look at this but if you do end up forking and implementing this, do ping me and I'll take a look at it.

from kube-monkey.

EIrwin avatar EIrwin commented on August 27, 2024

@asobti that was similar to the approach I have started implementing. The first iteration could simply use a opt-in bool along with a global MTBF to be used. In later iteration(s), this could be extended to allow individual deployments to override this value.

from kube-monkey.

asobti avatar asobti commented on August 27, 2024

Sounds good. I'll hold off on working on this for now in that case so we're not repeating the same work.

from kube-monkey.

janwillies avatar janwillies commented on August 27, 2024

Facing the same use-case. We have a shared cluster and there's no way for us to know all the namespaces to blacklist.

Maybe another idea is to have kube-monkey run per namespace? Or limit via RBAC rules?

from kube-monkey.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.