Thank you for the info. What are the ways with which I can implement these versions? Does using any other template will work, what about ACS 4.16, will it work with that?
On Wed, Oct 27, 2021, 14:37 Rohit Yadav <rohit.ya...@shapeblue.com> wrote: > Hi, > > CKS v1.20+ isn't tested and supported with CoreOS template with ACS 4.15.2. > > Pearl - should a compatibility matrix be maintained with the CKS feature? > > > Regards. > > ________________________________ > From: Pearl d'Silva <pearl.dsi...@shapeblue.com> > Sent: Wednesday, October 27, 2021 11:51 > To: dev@cloudstack.apache.org <dev@cloudstack.apache.org> > Subject: Re: Not able to implement latest CKS versions 1.21, 1.22 > > Hi, > > This issue is noticed in ACS 4.15 for kubernetes versions >= 1.18 as > conntrack dependency is required, which isn't present on the CoreOS > template. Absence of this dependency leads to failure in initializing the > k8s cluster with the following error: "[ERROR FileExisting-conntrack]: > conntrack not found in system path". > > Regards, > ________________________________ > From: R R <mrrishabhrapat...@gmail.com> > Sent: Wednesday, October 27, 2021 11:17 AM > To: dev@cloudstack.apache.org <dev@cloudstack.apache.org> > Subject: Re: Not able to implement latest CKS versions 1.21, 1.22 > > No. I used ACS 4.15.2.0. > > On Wed, Oct 27, 2021, 02:58 Wei ZHOU <ustcweiz...@gmail.com> wrote: > > > Did you use cloudstack 4.16.0.0-rc2 ? > > > > -Wei > > > > On Tuesday, 26 October 2021, R R <mrrishabhrapat...@gmail.com> wrote: > > > > > Hello all, > > > > > > I have been trying to implement the latest versions CKS- 1.22.2, and > > 1.21.3 > > > that were uploaded on http://download.cloudstack.org/cks/ . The > > instances > > > are starting and in running state, but when we access the console, got > > > the following error message: failed to start deploy kube system service > > > > > > Also, The kubernetes cluster just shows in a starting state for a long > > > time, and gives the following error message: > > > Error encountered while fetching async job result > > > > > > On management server, these were the logs: > > > 2021-10-27 00:49:31,622 DEBUG [c.c.a.ApiServlet] > > > (qtp576020159-654907:ctx-535a55e3 ctx-52688c9f) (logid:13603980) > > ===END=== > > > 10.1.1.106 -- GET > > > command=queryAsyncJobResult&jobId=b28bf567-2eee-487b-9b3d- > > > bc361589654c&response=json&_=1635275636716 > > > 2021-10-27 00:49:32,956 WARN [c.c.k.c.u.KubernetesClusterUtil] > > > (API-Job-Executor-51:ctx-8a55e9af job-110000 ctx-67f116db) > > > (logid:b28bf567) > > > API endpoint for Kubernetes cluster ID: > > > 7242b057-8f91-4eba-9dac-535f8f7336ac not available > > > javax.net.ssl.SSLHandshakeException: Remote host terminated the > handshake > > > at > > > java.base/sun.security.ssl.SSLSocketImpl.handleEOF( > > > SSLSocketImpl.java:1588) > > > at > > > > java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1416) > > > at > > > java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord( > > > SSLSocketImpl.java:1314) > > > at > > > java.base/sun.security.ssl.SSLSocketImpl.startHandshake( > > > SSLSocketImpl.java:440) > > > > > > > > > Can anyone help in this case? > > > > > > > > > > > >
