Steve Wade
Steve Wade
Issues go stale after 60d of inactivity.
This @garethahealy for this, will work on adding this over the weekend.
Hi @jpreese I’ve been thinking about the best way to structure this for a while now. So you’re saying that policies under folders which are specific to that Kubernetes version?...
I am wondering if I just release a container per kubernetes minor release containing just the deprecations for that release, thoughts?
@ckotzbauer @jpreese would you guys prefer a container per minor release or a directory structure similar to what @jpreese suggests? Waiting for feedback before implementation to make sure we are...
So if I re-structured the repo for a directory per minor release (e.g. `1.17`) and then inside that directory have all the deprecations for 1.17 and earlier, would that work?
I was actually wondering if having `kubernetes-1.16-deny.rego` and `kubernetes-1.16-warn.rego` makes sense. That way you have a location for all API versions that are denied by the specific version of Kubernetes...
I’ll get a new branch and PR setup tomorrow at some point and add you as a reviewer 😀
@ckotzbauer @jpreese I am actually thinking that specific containers for target versions may be easier.
I have just gone back and forward with the directory structure. My issue is the docker container itself, is it useful or not really?