Tomas Kral
Tomas Kral
> And when we have requests to support multiple branches, we can have different branches for different Kubernetes versions that we support, instead of putting all in the master. Multiple...
So If I want to convert for multiple for Kuberntes version I'll have to download multiple different binaries? That doesn't feel user-friendly. > The multiple branches approach is followed by...
Yep, as @surajssd there shouldn't be any vending issues, we just have to take care of outputting right stuff
I think we should increase the priority of this. We can start working on this as soon as https://github.com/kedgeproject/kedge/pull/181 is merged.
I think that adding `--k8s-version` as command line argument would be the best solution for this.
yes, it can be `--kubernetes-version`
I'm bumping priority on this, as I think we should solve this soon.
because we are also doing #210 we need also think about supporting multiple OpenShift versions, so this issue should also take into account that.
It might be time to reopen discussion on this. Here are some information changes in Workloads API in versions 1.8 and 1.9 https://kubernetes.io/docs/reference/workloads-18-19/ With default selector changes and introducing apps/v1...
One important thing is that this should be only in `kedge init`.