stack: dont provide CRI socket#95
Conversation
|
@jcvenegas might i ask you to take a quick peek at the containerd patch and see if we this can be pulled in with that? a.k.a can we fix that one and make it merge-able? |
16fa7ea to
98d3a1f
Compare
|
@ganeshmaharaj right, I did not wanted to modify a lot because there was that PR that is looking to fully enable containerd. On this PR we only add the logic to point to a cri socket, in the containerd PR there the approach used is to duplicate the kubeadm.yml file, I prefer this way. The containerd PR additionally do the next:
|
|
423f94f to
f7871d7
Compare
|
@mythi seems that works fine with containerd, I'll need to check with crio Be explicit and allow the user change the default paths or let kubeadm pick the path based en well known paths. |
|
Yes lets keep it simple. I have been using autodetection for a few days. Seems to be working. If the user wants custom location they can add. Out of the box crio and containerd locations as packaged by clear must work. |
f7871d7 to
0abd925
Compare
|
@krsna1729 thanks for confirm. I squashed the commits. |
kubeadm autodetects the socket path based on defaults from well known CRI servers. Signed-off-by: Jose Carlos Venegas Munoz <jose.carlos.venegas.munoz@intel.com>
|
@krsna1729 @jcvenegas sounds good! Note typo in the commit message |
0abd925 to
35d3d12
Compare
|
typo fixed |
|
Seems we are all happy with this change. time to hit merge. |
kubeadm autodetects the socket path based on defaults from well known
CRI servers.
Signed-off-by: Jose Carlos Venegas Munoz jose.carlos.venegas.munoz@intel.com