kind: Namespace #40
-
kubemod is super useful so far, but I have a potential use case where I would like to manage
First question would be would this even work? I have tried putting the rule in a specific namespace and then updated the namespace and haven't been able to get the operator to seem to see the namespace kind. The same test works great on deployments etc (per namespace). So thats my question. I haven't dug into the code too much and thought I would throw this out before doing so. Thanks |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments
-
+1 wondering this as well |
Beta Was this translation helpful? Give feedback.
-
I am planning to introduce support for cluster-wide resources before release 1.0. It sounds like this will cover your use case. Thoughts? |
Beta Was this translation helpful? Give feedback.
-
I just released KubeMod v0.9.0 which includes support for patching cluster-wide resources including namespaces. You can see an example of a ModRule which patches a namespace with |
Beta Was this translation helpful? Give feedback.
-
Awesome! That was fast. You added that before I could even respond to your first message. Great work - and this is exactly the use case I had in mind. I will holler with any feedback and contributions. Thanks |
Beta Was this translation helpful? Give feedback.
@llamashoes, @molliejaeron,
I just released KubeMod v0.9.0 which includes support for patching cluster-wide resources including namespaces.
If you plan to upgrade to this version, make sure to follow the upgrade instructions.
You can see an example of a ModRule which patches a namespace with
istio.io/rev
label here.Note how the ModRule is deployed to namespace
kubemod-system
in order to intercept cluster-level resources.Also, note the use of
~1
escape for/
when specifying the label name in the patchpath
.