Re: ACS 4.16 - Change SystemVM template for CKS
See inline On Tuesday, April 16, 2024, benoit lair wrote: > Ok and so there's no interaction with CS for firewalling and public ips > access par example ? CAPC automatically adds some lb rules and firewall rules for the k8s apiserver. To support k8s services with Type=LoadBalancer, you can deploy https://github.com/apache/cloudstack-kubernetes-provider getting it in a vpc tier for internal dmz use ? No. vpc is not supported. Refer to https://github.com/kubernetes-sigs/cluster-api-provider-cloudstack/issues/314 > Le mar. 16 avr. 2024 à 11:12, Wei ZHOU a écrit : > > > Hi benoit, > > > > You can try CAPC, it should work with 4.16 > > https://github.com/kubernetes-sigs/cluster-api-provider-cloudstack > > > > You need a local kind cluster to manage the CAPC clusters. They are > > not managed by CloudStack. > > > > > > -Wei > > > > On Fri, Apr 12, 2024 at 2:43 PM benoit lair > wrote: > > > > > > Hi Wei, > > > > > > upgrading from 4.16 to 4.19 will be a huge work for me > > > I have to test vpc/shared network, vrrp vpc with public lb Netscaler > and > > > withou it on several VPCs, i added support for VPX 12 and VPX 13 on it > > with > > > a nginx middleware rewriting rules from CS > > > I am on xcp-ng 8.2.1 > > > i kept during years with a CS 4.3, restarting from 4.16, i would like > > this > > > time to keep LTS in production > > > Is there a specific upgrade path to respect ? a specific process to > > observe > > > ? what rollback mechanism is possible ? > > > > > > For my K8S needs, I would like to upgrade it, but it was looking first > > for > > > a preproduction K8s working on 1.28 in order integrating CI/CD > pipelines > > > So this would not too be a problem upgrading CS after installing a k8s > > > cluster for CI/CD > > > > > > Rohit was talking about CAPC, i can use it independently of the version > > of > > > ACS i use ? > > > > > >
Re: ACS 4.16 - Change SystemVM template for CKS
Ok and so there's no interaction with CS for firewalling and public ips access par example ? getting it in a vpc tier for internal dmz use ? Le mar. 16 avr. 2024 à 11:12, Wei ZHOU a écrit : > Hi benoit, > > You can try CAPC, it should work with 4.16 > https://github.com/kubernetes-sigs/cluster-api-provider-cloudstack > > You need a local kind cluster to manage the CAPC clusters. They are > not managed by CloudStack. > > > -Wei > > On Fri, Apr 12, 2024 at 2:43 PM benoit lair wrote: > > > > Hi Wei, > > > > upgrading from 4.16 to 4.19 will be a huge work for me > > I have to test vpc/shared network, vrrp vpc with public lb Netscaler and > > withou it on several VPCs, i added support for VPX 12 and VPX 13 on it > with > > a nginx middleware rewriting rules from CS > > I am on xcp-ng 8.2.1 > > i kept during years with a CS 4.3, restarting from 4.16, i would like > this > > time to keep LTS in production > > Is there a specific upgrade path to respect ? a specific process to > observe > > ? what rollback mechanism is possible ? > > > > For my K8S needs, I would like to upgrade it, but it was looking first > for > > a preproduction K8s working on 1.28 in order integrating CI/CD pipelines > > So this would not too be a problem upgrading CS after installing a k8s > > cluster for CI/CD > > > > Rohit was talking about CAPC, i can use it independently of the version > of > > ACS i use ? > > >
Re: ACS 4.16 - Change SystemVM template for CKS
Hi benoit, You can try CAPC, it should work with 4.16 https://github.com/kubernetes-sigs/cluster-api-provider-cloudstack You need a local kind cluster to manage the CAPC clusters. They are not managed by CloudStack. -Wei On Fri, Apr 12, 2024 at 2:43 PM benoit lair wrote: > > Hi Wei, > > upgrading from 4.16 to 4.19 will be a huge work for me > I have to test vpc/shared network, vrrp vpc with public lb Netscaler and > withou it on several VPCs, i added support for VPX 12 and VPX 13 on it with > a nginx middleware rewriting rules from CS > I am on xcp-ng 8.2.1 > i kept during years with a CS 4.3, restarting from 4.16, i would like this > time to keep LTS in production > Is there a specific upgrade path to respect ? a specific process to observe > ? what rollback mechanism is possible ? > > For my K8S needs, I would like to upgrade it, but it was looking first for > a preproduction K8s working on 1.28 in order integrating CI/CD pipelines > So this would not too be a problem upgrading CS after installing a k8s > cluster for CI/CD > > Rohit was talking about CAPC, i can use it independently of the version of > ACS i use ? >
Re: ACS 4.16 - Change SystemVM template for CKS
bles = 1 > >> > [init] Using Kubernetes version: v1.25.0 > >> > [preflight] Running pre-flight checks > >> > [WARNING SystemVerification]: missing optional cgroups: blkio > >> > error execution phase preflight: [preflight] Some fatal errors occurred: > >> > [ERROR CRI]: container runtime is not running: output: E0411 > >> > 11:38:11.935458 12988 remote_runtime.go:948] "Status from runtime > >> service > >> > failed" err="rpc error: code = Unimplemented desc = unknown service > >> > runtime.v1alpha2.RuntimeService" > >> > time="2024-04-11T11:38:11Z" level=fatal msg="getting status of runtime: > >> rpc > >> > error: code = Unimplemented desc = unknown service > >> > runtime.v1alpha2.RuntimeService" > >> > , error: exit status 1 > >> > [preflight] If you know what you are doing, you can make a check > >> non-fatal > >> > with `--ignore-preflight-errors=...` > >> > To see the stack trace of this error execute with --v=5 or higher > >> > [init] Using Kubernetes version: v1.25.0 > >> > [preflight] Running pre-flight checks > >> > [WARNING SystemVerification]: missing optional cgroups: blkio > >> > error execution phase preflight: [preflight] Some fatal errors occurred: > >> > [ERROR CRI]: container runtime is not running: output: E0411 > >> > 11:38:12.079422 13015 remote_runtime.go:948] "Status from runtime > >> service > >> > failed" err="rpc error: code = Unimplemented desc = unknown service > >> > runtime.v1alpha2.RuntimeService" > >> > time="2024-04-11T11:38:12Z" level=fatal msg="getting status of runtime: > >> rpc > >> > error: code = Unimplemented desc = unknown service > >> > runtime.v1alpha2.RuntimeService" > >> > , error: exit status 1 > >> > [preflight] If you know what you are doing, you can make a check > >> non-fatal > >> > with `--ignore-preflight-errors=...` > >> > To see the stack trace of this error execute with --v=5 or higher > >> > [init] Using Kubernetes version: v1.25.0 > >> > [preflight] Running pre-flight checks > >> > [WARNING SystemVerification]: missing optional cgroups: blkio > >> > error execution phase preflight: [preflight] Some fatal errors occurred: > >> > [ERROR CRI]: container runtime is not running: output: E0411 > >> > 11:38:12.228669 13043 remote_runtime.go:948] "Status from runtime > >> service > >> > failed" err="rpc error: code = Unimplemented desc = unknown service > >> > runtime.v1alpha2.RuntimeService" > >> > time="2024-04-11T11:38:12Z" level=fatal msg="getting status of runtime: > >> rpc > >> > error: code = Unimplemented desc = unknown service > >> > runtime.v1alpha2.RuntimeService" > >> > , error: exit status 1 > >> > [preflight] If you know what you are doing, you can make a check > >> non-fatal > >> > with `--ignore-preflight-errors=...` > >> > To see the stack trace of this error execute with --v=5 or higher > >> > Error: kubeadm init failed! > >> > > >> > > >> > Le jeu. 11 avr. 2024 à 12:03, Rohit Yadav a > >> > écrit : > >> > > >> > > Hi Benoit, > >> > > > >> > > The CKS feature has been improving over versions, I don't know if what > >> > > you're trying to achieve is possible with it. Maybe try a different > >> > version > >> > > of the data iso: > >> > > http://download.cloudstack.org/cks/ > >> > > > >> > > Alternatively, you can also have a look at the CAPC project: > >> > > https://cluster-api-cloudstack.sigs.k8s.io > >> > > > >> > > > >> > > Regards. > >> > > > >> > > > >> > > > >> > > > >> > > > >> > > From: benoit lair > >> > > Sent: Thursday, April 11, 2024 14:16 > >> > > To: us...@cloudstack.apache.org ; dev < > >> > > dev@cloudstack.apache.org> > >> > > Subject: Re: ACS 4.16 - Change SystemVM template for CKS > >> > > > >> > > Any advices ? > >> > > > >> > > Best regards > >> > > > >> > > Le lun. 8 avr. 2024 à 16:53, benoit lair a > >> > écrit : > >> > > > >> > > > I am opened to every alternatives of changing system vm templates > >> > > > I just need to run K8s clyusters 1.28 with my CS 4.16 :) > >> > > > > >> > > > Le lun. 8 avr. 2024 à 16:52, benoit lair a > >> > > écrit : > >> > > > > >> > > >> Hello Folks, > >> > > >> > >> > > >> I am trying to install K8s cluster with community iso 1.28.4 > >> > > >> I am with a ACS 4.16.0 environment > >> > > >> It seems K8S is not working out of the box with v > 1.23.3 due to > >> > > >> containerd.io version > >> > > >> > >> > > >> I would like to release a template who will work with K8s > 1.23.3 > >> on > >> > > acs > >> > > >> 4.16 > >> > > >> How can i tell CS to take another system vm template, avoiding to > >> mess > >> > > >> normal features with VR and VPC VR keeping the systemvm template > >> > issued > >> > > >> with CS 4.16 ? > >> > > >> > >> > > >> I am with XCP-NG 8.2.1 in production > >> > > >> > >> > > >> Thanks for your help or advises > >> > > >> Best regards, > >> > > >> Benoit > >> > > >> > >> > > > > >> > > > >> > > >> > > > -- Sent with Vivaldi Mail. Download Vivaldi for free at vivaldi.com
Re: ACS 4.16 - Change SystemVM template for CKS
ntroller-manager:v1.25.0 > > >> > e4d19dd12df2: Loading layer > > >> > [==>] > 7.631MB/7.631MB > > >> > ba3637ccd78a: Loading layer > > >> > [==>] > 12.63MB/12.63MB > > >> > Loaded image: registry.k8s.io/kube-proxy:v1.25.0 > > >> > 026969d859f7: Loading layer > > >> > [==>] > 14.29MB/14.29MB > > >> > Loaded image: registry.k8s.io/kube-scheduler:v1.25.0 > > >> > d01384fea991: Loading layer > > >> > [==>] > 19.74MB/19.74MB > > >> > bcec7eb9e567: Loading layer > > >> > [==>] 530B/530B > > >> > Loaded image: kubernetesui/metrics-scraper:v1.0.8 > > >> > 961e93cda9dd: Loading layer > > >> > [==>]307kB/307kB > > >> > Loaded image: registry.k8s.io/pause:3.8 > > >> > 1b3ee35aacca: Loading layer > > >> > [==>] > 2.796MB/2.796MB > > >> > 17d89e2a5199: Loading layer > > >> > [==>] > 7.425MB/7.425MB > > >> > 148b94859892: Loading layer > > >> > [==>]8.1MB/8.1MB > > >> > dbea472c1ced: Loading layer > > >> > [==>] > 4.376MB/4.376MB > > >> > e81f1a367c17: Loading layer > > >> > [==>] 131B/131B > > >> > 351848f6b295: Loading layer > > >> > [==>] > 8.216MB/8.216MB > > >> > Loaded image: weaveworks/weave-kube:latest > > >> > b20f7ff12b24: Loading layer > > >> > [==>] > 727.9kB/727.9kB > > >> > 1d49e386162e: Loading layer > > >> > [==>] > 9.281MB/9.281MB > > >> > 20145eeac146: Loading layer > > >> > [==>] 297B/297B > > >> > d4cc72748587: Loading layer > > >> > [==>] 600B/600B > > >> > Loaded image: weaveworks/weave-npc:latest > > >> > net.bridge.bridge-nf-call-iptables = 1 > > >> > [init] Using Kubernetes version: v1.25.0 > > >> > [preflight] Running pre-flight checks > > >> > [WARNING SystemVerification]: missing optional cgroups: > blkio > > >> > error execution phase preflight: [preflight] Some fatal errors > occurred: > > >> > [ERROR CRI]: container runtime is not running: output: E0411 > > >> > 11:38:11.935458 12988 remote_runtime.go:948] "Status from runtime > > >> service > > >> > failed" err="rpc error: code = Unimplemented desc = unknown service > > >> > runtime.v1alpha2.RuntimeService" > > >> > time="2024-04-11T11:38:11Z" level=fatal msg="getting status of > runtime: > > >> rpc > > >> > error: code = Unimplemented desc = unknown service > > >> > runtime.v1alpha2.RuntimeService" > > >> > , error: exit status 1 > > >> > [preflight] If you know what you are doing, you can make a check > > >> non-fatal > > >> > with `--ignore-preflight-errors=...` > > >> > To see the stack trace of this error execute with --v=5 or higher > > >> > [init] Using Kubernetes version: v1.25.0 > > >> > [preflight] Running pre-flight checks > > >> > [WARNING SystemVerification]: missing optional cgroups: > blkio > > >> > error execution phase preflight: [preflight] Some fatal errors > occurred: > > >> > [ERROR CRI]: container runtime is not running: output: E0411 > > >> > 11:38:12.079422 13015 remote_runtime.go:948] "Status from runtime > > >> service > > >> > failed" err="rpc error: code = Unimplemented desc = unknown service > > >> > runtime.v1alpha2.RuntimeService" > > >> > time="2024-04-11T11:38:12Z" level=fatal msg="getting status of > runtime: > > >> rpc > > >> > error: code = Unimplemented desc = unknown service > > >> > runtime.v1alpha2.RuntimeService" > > >> > , error: exit status 1 > > >> > [preflight] If you know what you are doing, you can make a check > > >> non-fatal > > >> > with `--ignore-preflight-errors=...` > > >> > To see the stack trace of this error execute with --v=5 or higher > > >> > [init] Using Kubernetes version: v1.25.0 > > >> > [preflight] Running pre-flight checks > > >> > [WARNING SystemVerification]: missing optional cgroups: > blkio > > >> > error execution phase preflight: [preflight] Some fatal errors > occurred: > > >> > [ERROR CRI]: container runtime is not running: output: E0411 > > >> > 11:38:12.228669 13043 remote_runtime.go:948] "Status from runtime > > >> service > > >> > failed" err="rpc error: code = Unimplemented desc = unknown service > > >> > runtime.v1alpha2.RuntimeService" > > >> > time="2024-04-11T11:38:12Z" level=fatal msg="getting status of > runtime: > > >> rpc > > >> > error: code = Unimplemented desc = unknown service > > >> > runtime.v1alpha2.RuntimeService" > > >> > , error: exit status 1 > > >> > [preflight] If you know what you are doing, you can make a check > > >> non-fatal > > >> > with `--ignore-preflight-errors=...` > > >> > To see the stack trace of this error execute with --v=5 or higher > > >> > Error: kubeadm init failed! > > >> > > > >> > > > >> > Le jeu. 11 avr. 2024 à 12:03, Rohit Yadav < > rohit.ya...@shapeblue.com> a > > >> > écrit : > > >> > > > >> > > Hi Benoit, > > >> > > > > >> > > The CKS feature has been improving over versions, I don't know if > what > > >> > > you're trying to achieve is possible with it. Maybe try a > different > > >> > version > > >> > > of the data iso: > > >> > > http://download.cloudstack.org/cks/ > > >> > > > > >> > > Alternatively, you can also have a look at the CAPC project: > > >> > > https://cluster-api-cloudstack.sigs.k8s.io > > >> > > > > >> > > > > >> > > Regards. > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > From: benoit lair > > >> > > Sent: Thursday, April 11, 2024 14:16 > > >> > > To: us...@cloudstack.apache.org ; > dev < > > >> > > dev@cloudstack.apache.org> > > >> > > Subject: Re: ACS 4.16 - Change SystemVM template for CKS > > >> > > > > >> > > Any advices ? > > >> > > > > >> > > Best regards > > >> > > > > >> > > Le lun. 8 avr. 2024 à 16:53, benoit lair > a > > >> > écrit : > > >> > > > > >> > > > I am opened to every alternatives of changing system vm > templates > > >> > > > I just need to run K8s clyusters 1.28 with my CS 4.16 :) > > >> > > > > > >> > > > Le lun. 8 avr. 2024 à 16:52, benoit lair > a > > >> > > écrit : > > >> > > > > > >> > > >> Hello Folks, > > >> > > >> > > >> > > >> I am trying to install K8s cluster with community iso 1.28.4 > > >> > > >> I am with a ACS 4.16.0 environment > > >> > > >> It seems K8S is not working out of the box with v > 1.23.3 due > to > > >> > > >> containerd.io version > > >> > > >> > > >> > > >> I would like to release a template who will work with K8s > > 1.23.3 > > >> on > > >> > > acs > > >> > > >> 4.16 > > >> > > >> How can i tell CS to take another system vm template, avoiding > to > > >> mess > > >> > > >> normal features with VR and VPC VR keeping the systemvm > template > > >> > issued > > >> > > >> with CS 4.16 ? > > >> > > >> > > >> > > >> I am with XCP-NG 8.2.1 in production > > >> > > >> > > >> > > >> Thanks for your help or advises > > >> > > >> Best regards, > > >> > > >> Benoit > > >> > > >> > > >> > > > > > >> > > > > >> > > > >> > > > >
Re: ACS 4.16 - Change SystemVM template for CKS
gt; net.bridge.bridge-nf-call-iptables = 1 > >> > [init] Using Kubernetes version: v1.25.0 > >> > [preflight] Running pre-flight checks > >> > [WARNING SystemVerification]: missing optional cgroups: blkio > >> > error execution phase preflight: [preflight] Some fatal errors occurred: > >> > [ERROR CRI]: container runtime is not running: output: E0411 > >> > 11:38:11.935458 12988 remote_runtime.go:948] "Status from runtime > >> service > >> > failed" err="rpc error: code = Unimplemented desc = unknown service > >> > runtime.v1alpha2.RuntimeService" > >> > time="2024-04-11T11:38:11Z" level=fatal msg="getting status of runtime: > >> rpc > >> > error: code = Unimplemented desc = unknown service > >> > runtime.v1alpha2.RuntimeService" > >> > , error: exit status 1 > >> > [preflight] If you know what you are doing, you can make a check > >> non-fatal > >> > with `--ignore-preflight-errors=...` > >> > To see the stack trace of this error execute with --v=5 or higher > >> > [init] Using Kubernetes version: v1.25.0 > >> > [preflight] Running pre-flight checks > >> > [WARNING SystemVerification]: missing optional cgroups: blkio > >> > error execution phase preflight: [preflight] Some fatal errors occurred: > >> > [ERROR CRI]: container runtime is not running: output: E0411 > >> > 11:38:12.079422 13015 remote_runtime.go:948] "Status from runtime > >> service > >> > failed" err="rpc error: code = Unimplemented desc = unknown service > >> > runtime.v1alpha2.RuntimeService" > >> > time="2024-04-11T11:38:12Z" level=fatal msg="getting status of runtime: > >> rpc > >> > error: code = Unimplemented desc = unknown service > >> > runtime.v1alpha2.RuntimeService" > >> > , error: exit status 1 > >> > [preflight] If you know what you are doing, you can make a check > >> non-fatal > >> > with `--ignore-preflight-errors=...` > >> > To see the stack trace of this error execute with --v=5 or higher > >> > [init] Using Kubernetes version: v1.25.0 > >> > [preflight] Running pre-flight checks > >> > [WARNING SystemVerification]: missing optional cgroups: blkio > >> > error execution phase preflight: [preflight] Some fatal errors occurred: > >> > [ERROR CRI]: container runtime is not running: output: E0411 > >> > 11:38:12.228669 13043 remote_runtime.go:948] "Status from runtime > >> service > >> > failed" err="rpc error: code = Unimplemented desc = unknown service > >> > runtime.v1alpha2.RuntimeService" > >> > time="2024-04-11T11:38:12Z" level=fatal msg="getting status of runtime: > >> rpc > >> > error: code = Unimplemented desc = unknown service > >> > runtime.v1alpha2.RuntimeService" > >> > , error: exit status 1 > >> > [preflight] If you know what you are doing, you can make a check > >> non-fatal > >> > with `--ignore-preflight-errors=...` > >> > To see the stack trace of this error execute with --v=5 or higher > >> > Error: kubeadm init failed! > >> > > >> > > >> > Le jeu. 11 avr. 2024 à 12:03, Rohit Yadav a > >> > écrit : > >> > > >> > > Hi Benoit, > >> > > > >> > > The CKS feature has been improving over versions, I don't know if what > >> > > you're trying to achieve is possible with it. Maybe try a different > >> > version > >> > > of the data iso: > >> > > http://download.cloudstack.org/cks/ > >> > > > >> > > Alternatively, you can also have a look at the CAPC project: > >> > > https://cluster-api-cloudstack.sigs.k8s.io > >> > > > >> > > > >> > > Regards. > >> > > > >> > > > >> > > > >> > > > >> > > > >> > > From: benoit lair > >> > > Sent: Thursday, April 11, 2024 14:16 > >> > > To: us...@cloudstack.apache.org ; dev < > >> > > dev@cloudstack.apache.org> > >> > > Subject: Re: ACS 4.16 - Change SystemVM template for CKS > >> > > > >> > > Any advices ? > >> > > > >> > > Best regards > >> > > > >> > > Le lun. 8 avr. 2024 à 16:53, benoit lair a > >> > écrit : > >> > > > >> > > > I am opened to every alternatives of changing system vm templates > >> > > > I just need to run K8s clyusters 1.28 with my CS 4.16 :) > >> > > > > >> > > > Le lun. 8 avr. 2024 à 16:52, benoit lair a > >> > > écrit : > >> > > > > >> > > >> Hello Folks, > >> > > >> > >> > > >> I am trying to install K8s cluster with community iso 1.28.4 > >> > > >> I am with a ACS 4.16.0 environment > >> > > >> It seems K8S is not working out of the box with v > 1.23.3 due to > >> > > >> containerd.io version > >> > > >> > >> > > >> I would like to release a template who will work with K8s > 1.23.3 > >> on > >> > > acs > >> > > >> 4.16 > >> > > >> How can i tell CS to take another system vm template, avoiding to > >> mess > >> > > >> normal features with VR and VPC VR keeping the systemvm template > >> > issued > >> > > >> with CS 4.16 ? > >> > > >> > >> > > >> I am with XCP-NG 8.2.1 in production > >> > > >> > >> > > >> Thanks for your help or advises > >> > > >> Best regards, > >> > > >> Benoit > >> > > >> > >> > > > > >> > > > >> > > >> > >
Re: ACS 4.16 - Change SystemVM template for CKS
; > 8d7366c22fd8: Loading layer >> > [==>] 804.1kB/804.1kB >> > 7d5f5bba7c45: Loading layer >> > [==>] 694.9kB/694.9kB >> > 8154c9483a6c: Loading layer >> > [==>] 32.72MB/32.72MB >> > Loaded image: registry.k8s.io/kube-apiserver:v1.25.0 >> > c5f1a47b47bc: Loading layer >> > [==>] 29.76MB/29.76MB >> > Loaded image: registry.k8s.io/kube-controller-manager:v1.25.0 >> > e4d19dd12df2: Loading layer >> > [==>] 7.631MB/7.631MB >> > ba3637ccd78a: Loading layer >> > [==>] 12.63MB/12.63MB >> > Loaded image: registry.k8s.io/kube-proxy:v1.25.0 >> > 026969d859f7: Loading layer >> > [==>] 14.29MB/14.29MB >> > Loaded image: registry.k8s.io/kube-scheduler:v1.25.0 >> > d01384fea991: Loading layer >> > [==>] 19.74MB/19.74MB >> > bcec7eb9e567: Loading layer >> > [==>] 530B/530B >> > Loaded image: kubernetesui/metrics-scraper:v1.0.8 >> > 961e93cda9dd: Loading layer >> > [==>]307kB/307kB >> > Loaded image: registry.k8s.io/pause:3.8 >> > 1b3ee35aacca: Loading layer >> > [==>] 2.796MB/2.796MB >> > 17d89e2a5199: Loading layer >> > [==>] 7.425MB/7.425MB >> > 148b94859892: Loading layer >> > [==>]8.1MB/8.1MB >> > dbea472c1ced: Loading layer >> > [==>] 4.376MB/4.376MB >> > e81f1a367c17: Loading layer >> > [==>] 131B/131B >> > 351848f6b295: Loading layer >> > [==>] 8.216MB/8.216MB >> > Loaded image: weaveworks/weave-kube:latest >> > b20f7ff12b24: Loading layer >> > [==>] 727.9kB/727.9kB >> > 1d49e386162e: Loading layer >> > [==>] 9.281MB/9.281MB >> > 20145eeac146: Loading layer >> > [==>] 297B/297B >> > d4cc72748587: Loading layer >> > [==>] 600B/600B >> > Loaded image: weaveworks/weave-npc:latest >> > net.bridge.bridge-nf-call-iptables = 1 >> > [init] Using Kubernetes version: v1.25.0 >> > [preflight] Running pre-flight checks >> > [WARNING SystemVerification]: missing optional cgroups: blkio >> > error execution phase preflight: [preflight] Some fatal errors occurred: >> > [ERROR CRI]: container runtime is not running: output: E0411 >> > 11:38:11.935458 12988 remote_runtime.go:948] "Status from runtime >> service >> > failed" err="rpc error: code = Unimplemented desc = unknown service >> > runtime.v1alpha2.RuntimeService" >> > time="2024-04-11T11:38:11Z" level=fatal msg="getting status of runtime: >> rpc >> > error: code = Unimplemented desc = unknown service >> > runtime.v1alpha2.RuntimeService" >> > , error: exit status 1 >> > [preflight] If you know what you are doing, you can make a check >> non-fatal >> > with `--ignore-preflight-errors=...` >> > To see the stack trace of this error execute with --v=5 or higher >> > [init] Using Kubernetes version: v1.25.0 >> > [preflight] Running pre-flight checks >> > [WARNING SystemVerification]: missing optional cgroups: blkio >> > error execution phase preflight: [preflight] Some fatal errors occurred: >> > [ERROR CRI]: container runtime is not running: output: E0411 >> > 11:38:12.079422 13015 remote_runtime.go:948] "Status from runtime >> service >> > failed" err="rpc error: code = Unimplemented desc = unknown service >> > runtime.v1alpha2.RuntimeService" >> > time="2024-04-11T11:38:12Z" level=fatal msg="getting status of runtime: >> rpc >> > error: code = Unimplemented desc = unknown service >>
Re: ACS 4.16 - Change SystemVM template for CKS
tables = 1 > > [init] Using Kubernetes version: v1.25.0 > > [preflight] Running pre-flight checks > > [WARNING SystemVerification]: missing optional cgroups: blkio > > error execution phase preflight: [preflight] Some fatal errors occurred: > > [ERROR CRI]: container runtime is not running: output: E0411 > > 11:38:11.935458 12988 remote_runtime.go:948] "Status from runtime > service > > failed" err="rpc error: code = Unimplemented desc = unknown service > > runtime.v1alpha2.RuntimeService" > > time="2024-04-11T11:38:11Z" level=fatal msg="getting status of runtime: > rpc > > error: code = Unimplemented desc = unknown service > > runtime.v1alpha2.RuntimeService" > > , error: exit status 1 > > [preflight] If you know what you are doing, you can make a check > non-fatal > > with `--ignore-preflight-errors=...` > > To see the stack trace of this error execute with --v=5 or higher > > [init] Using Kubernetes version: v1.25.0 > > [preflight] Running pre-flight checks > > [WARNING SystemVerification]: missing optional cgroups: blkio > > error execution phase preflight: [preflight] Some fatal errors occurred: > > [ERROR CRI]: container runtime is not running: output: E0411 > > 11:38:12.079422 13015 remote_runtime.go:948] "Status from runtime > service > > failed" err="rpc error: code = Unimplemented desc = unknown service > > runtime.v1alpha2.RuntimeService" > > time="2024-04-11T11:38:12Z" level=fatal msg="getting status of runtime: > rpc > > error: code = Unimplemented desc = unknown service > > runtime.v1alpha2.RuntimeService" > > , error: exit status 1 > > [preflight] If you know what you are doing, you can make a check > non-fatal > > with `--ignore-preflight-errors=...` > > To see the stack trace of this error execute with --v=5 or higher > > [init] Using Kubernetes version: v1.25.0 > > [preflight] Running pre-flight checks > > [WARNING SystemVerification]: missing optional cgroups: blkio > > error execution phase preflight: [preflight] Some fatal errors occurred: > > [ERROR CRI]: container runtime is not running: output: E0411 > > 11:38:12.228669 13043 remote_runtime.go:948] "Status from runtime > service > > failed" err="rpc error: code = Unimplemented desc = unknown service > > runtime.v1alpha2.RuntimeService" > > time="2024-04-11T11:38:12Z" level=fatal msg="getting status of runtime: > rpc > > error: code = Unimplemented desc = unknown service > > runtime.v1alpha2.RuntimeService" > > , error: exit status 1 > > [preflight] If you know what you are doing, you can make a check > non-fatal > > with `--ignore-preflight-errors=...` > > To see the stack trace of this error execute with --v=5 or higher > > Error: kubeadm init failed! > > > > > > Le jeu. 11 avr. 2024 à 12:03, Rohit Yadav a > > écrit : > > > > > Hi Benoit, > > > > > > The CKS feature has been improving over versions, I don't know if what > > > you're trying to achieve is possible with it. Maybe try a different > > version > > > of the data iso: > > > http://download.cloudstack.org/cks/ > > > > > > Alternatively, you can also have a look at the CAPC project: > > > https://cluster-api-cloudstack.sigs.k8s.io > > > > > > > > > Regards. > > > > > > > > > > > > > > > > > > From: benoit lair > > > Sent: Thursday, April 11, 2024 14:16 > > > To: us...@cloudstack.apache.org ; dev < > > > dev@cloudstack.apache.org> > > > Subject: Re: ACS 4.16 - Change SystemVM template for CKS > > > > > > Any advices ? > > > > > > Best regards > > > > > > Le lun. 8 avr. 2024 à 16:53, benoit lair a > > écrit : > > > > > > > I am opened to every alternatives of changing system vm templates > > > > I just need to run K8s clyusters 1.28 with my CS 4.16 :) > > > > > > > > Le lun. 8 avr. 2024 à 16:52, benoit lair a > > > écrit : > > > > > > > >> Hello Folks, > > > >> > > > >> I am trying to install K8s cluster with community iso 1.28.4 > > > >> I am with a ACS 4.16.0 environment > > > >> It seems K8S is not working out of the box with v > 1.23.3 due to > > > >> containerd.io version > > > >> > > > >> I would like to release a template who will work with K8s > 1.23.3 > on > > > acs > > > >> 4.16 > > > >> How can i tell CS to take another system vm template, avoiding to > mess > > > >> normal features with VR and VPC VR keeping the systemvm template > > issued > > > >> with CS 4.16 ? > > > >> > > > >> I am with XCP-NG 8.2.1 in production > > > >> > > > >> Thanks for your help or advises > > > >> Best regards, > > > >> Benoit > > > >> > > > > > > > > > >
Re: ACS 4.16 - Change SystemVM template for CKS
e: weaveworks/weave-kube:latest > b20f7ff12b24: Loading layer > [==>] 727.9kB/727.9kB > 1d49e386162e: Loading layer > [==>] 9.281MB/9.281MB > 20145eeac146: Loading layer > [==>] 297B/297B > d4cc72748587: Loading layer > [==>] 600B/600B > Loaded image: weaveworks/weave-npc:latest > net.bridge.bridge-nf-call-iptables = 1 > [init] Using Kubernetes version: v1.25.0 > [preflight] Running pre-flight checks > [WARNING SystemVerification]: missing optional cgroups: blkio > error execution phase preflight: [preflight] Some fatal errors occurred: > [ERROR CRI]: container runtime is not running: output: E0411 > 11:38:11.935458 12988 remote_runtime.go:948] "Status from runtime service > failed" err="rpc error: code = Unimplemented desc = unknown service > runtime.v1alpha2.RuntimeService" > time="2024-04-11T11:38:11Z" level=fatal msg="getting status of runtime: rpc > error: code = Unimplemented desc = unknown service > runtime.v1alpha2.RuntimeService" > , error: exit status 1 > [preflight] If you know what you are doing, you can make a check non-fatal > with `--ignore-preflight-errors=...` > To see the stack trace of this error execute with --v=5 or higher > [init] Using Kubernetes version: v1.25.0 > [preflight] Running pre-flight checks > [WARNING SystemVerification]: missing optional cgroups: blkio > error execution phase preflight: [preflight] Some fatal errors occurred: > [ERROR CRI]: container runtime is not running: output: E0411 > 11:38:12.079422 13015 remote_runtime.go:948] "Status from runtime service > failed" err="rpc error: code = Unimplemented desc = unknown service > runtime.v1alpha2.RuntimeService" > time="2024-04-11T11:38:12Z" level=fatal msg="getting status of runtime: rpc > error: code = Unimplemented desc = unknown service > runtime.v1alpha2.RuntimeService" > , error: exit status 1 > [preflight] If you know what you are doing, you can make a check non-fatal > with `--ignore-preflight-errors=...` > To see the stack trace of this error execute with --v=5 or higher > [init] Using Kubernetes version: v1.25.0 > [preflight] Running pre-flight checks > [WARNING SystemVerification]: missing optional cgroups: blkio > error execution phase preflight: [preflight] Some fatal errors occurred: > [ERROR CRI]: container runtime is not running: output: E0411 > 11:38:12.228669 13043 remote_runtime.go:948] "Status from runtime service > failed" err="rpc error: code = Unimplemented desc = unknown service > runtime.v1alpha2.RuntimeService" > time="2024-04-11T11:38:12Z" level=fatal msg="getting status of runtime: rpc > error: code = Unimplemented desc = unknown service > runtime.v1alpha2.RuntimeService" > , error: exit status 1 > [preflight] If you know what you are doing, you can make a check non-fatal > with `--ignore-preflight-errors=...` > To see the stack trace of this error execute with --v=5 or higher > Error: kubeadm init failed! > > > Le jeu. 11 avr. 2024 à 12:03, Rohit Yadav a > écrit : > > > Hi Benoit, > > > > The CKS feature has been improving over versions, I don't know if what > > you're trying to achieve is possible with it. Maybe try a different > version > > of the data iso: > > http://download.cloudstack.org/cks/ > > > > Alternatively, you can also have a look at the CAPC project: > > https://cluster-api-cloudstack.sigs.k8s.io > > > > > > Regards. > > > > > > > > > > > > From: benoit lair > > Sent: Thursday, April 11, 2024 14:16 > > To: us...@cloudstack.apache.org ; dev < > > dev@cloudstack.apache.org> > > Subject: Re: ACS 4.16 - Change SystemVM template for CKS > > > > Any advices ? > > > > Best regards > > > > Le lun. 8 avr. 2024 à 16:53, benoit lair a > écrit : > > > > > I am opened to every alternatives of changing system vm templates > > > I just need to run K8s clyusters 1.28 with my CS 4.16 :) > > > > > > Le lun. 8 avr. 2024 à 16:52, benoit lair a > > écrit : > > > > > >> Hello Folks, > > >> > > >> I am trying to install K8s cluster with community iso 1.28.4 > > >> I am with a ACS 4.16.0 environment > > >> It seems K8S is not working out of the box with v > 1.23.3 due to > > >> containerd.io version > > >> > > >> I would like to release a template who will work with K8s > 1.23.3 on > > acs > > >> 4.16 > > >> How can i tell CS to take another system vm template, avoiding to mess > > >> normal features with VR and VPC VR keeping the systemvm template > issued > > >> with CS 4.16 ? > > >> > > >> I am with XCP-NG 8.2.1 in production > > >> > > >> Thanks for your help or advises > > >> Best regards, > > >> Benoit > > >> > > > > > >
Re: ACS 4.16 - Change SystemVM template for CKS
@Embedded, did you take a look on https://docs.cloudstack.apache.org/en/latest/plugins/cloudstack-kubernetes-service.html ? You have registered k8s iso image ? What is your error message ? you can connect to your control node via pub.key hosted on mgmt server with "ssh -i rsa_test.cloud -p core@ Take a look at logs from control node (via port ) Le jeu. 11 avr. 2024 à 12:22, Embedded a écrit : > > > > On Thursday 11 April 2024 03:46:49 PM (+07:00), benoit lair wrote: > > > Any advices ? > > > > Best regards > > Im headed down the exact same path with debian manager and xcp-ng 8.2.1 > so i can see how the CKS works, only im on 4.19, i also used shapeblues > image > > happy to help once im at that point, its a fresh install > > > > > Le lun. 8 avr. 2024 à 16:53, benoit lair a > écrit : > > > > > I am opened to every alternatives of changing system vm templates > > > I just need to run K8s clyusters 1.28 with my CS 4.16 :) > > > > > > Le lun. 8 avr. 2024 à 16:52, benoit lair a > écrit : > > > > > >> Hello Folks, > > >> > > >> I am trying to install K8s cluster with community iso 1.28.4 > > >> I am with a ACS 4.16.0 environment > > >> It seems K8S is not working out of the box with v > 1.23.3 due to > > >> containerd.io version > > >> > > >> I would like to release a template who will work with K8s > 1.23.3 on > acs > > >> 4.16 > > >> How can i tell CS to take another system vm template, avoiding to mess > > >> normal features with VR and VPC VR keeping the systemvm template > issued > > >> with CS 4.16 ? > > >> > > >> I am with XCP-NG 8.2.1 in production > > >> > > >> Thanks for your help or advises > > >> Best regards, > > >> Benoit > > >> > > > > > > > -- > Sent with Vivaldi Mail. Download Vivaldi for free at vivaldi.com >
Re: ACS 4.16 - Change SystemVM template for CKS
Benoit, I haven't tested it but could work - worth testing. CAPC was tested on 4.17/4.18+. Regards. From: benoit lair Sent: Thursday, April 11, 2024 17:09 To: us...@cloudstack.apache.org Cc: dev Subject: Re: ACS 4.16 - Change SystemVM template for CKS Rohit, It is possible to install CAPC on a CS 4.16 ? Le jeu. 11 avr. 2024 à 12:03, Rohit Yadav a écrit : > Hi Benoit, > > The CKS feature has been improving over versions, I don't know if what > you're trying to achieve is possible with it. Maybe try a different version > of the data iso: > http://download.cloudstack.org/cks/ > > Alternatively, you can also have a look at the CAPC project: > https://cluster-api-cloudstack.sigs.k8s.io > > > Regards. > > > > > > From: benoit lair > Sent: Thursday, April 11, 2024 14:16 > To: us...@cloudstack.apache.org ; dev < > dev@cloudstack.apache.org> > Subject: Re: ACS 4.16 - Change SystemVM template for CKS > > Any advices ? > > Best regards > > Le lun. 8 avr. 2024 à 16:53, benoit lair a écrit : > > > I am opened to every alternatives of changing system vm templates > > I just need to run K8s clyusters 1.28 with my CS 4.16 :) > > > > Le lun. 8 avr. 2024 à 16:52, benoit lair a > écrit : > > > >> Hello Folks, > >> > >> I am trying to install K8s cluster with community iso 1.28.4 > >> I am with a ACS 4.16.0 environment > >> It seems K8S is not working out of the box with v > 1.23.3 due to > >> containerd.io version > >> > >> I would like to release a template who will work with K8s > 1.23.3 on > acs > >> 4.16 > >> How can i tell CS to take another system vm template, avoiding to mess > >> normal features with VR and VPC VR keeping the systemvm template issued > >> with CS 4.16 ? > >> > >> I am with XCP-NG 8.2.1 in production > >> > >> Thanks for your help or advises > >> Best regards, > >> Benoit > >> > > >
Re: ACS 4.16 - Change SystemVM template for CKS
Rohit, It is possible to install CAPC on a CS 4.16 ? Le jeu. 11 avr. 2024 à 12:03, Rohit Yadav a écrit : > Hi Benoit, > > The CKS feature has been improving over versions, I don't know if what > you're trying to achieve is possible with it. Maybe try a different version > of the data iso: > http://download.cloudstack.org/cks/ > > Alternatively, you can also have a look at the CAPC project: > https://cluster-api-cloudstack.sigs.k8s.io > > > Regards. > > > > > > From: benoit lair > Sent: Thursday, April 11, 2024 14:16 > To: us...@cloudstack.apache.org ; dev < > dev@cloudstack.apache.org> > Subject: Re: ACS 4.16 - Change SystemVM template for CKS > > Any advices ? > > Best regards > > Le lun. 8 avr. 2024 à 16:53, benoit lair a écrit : > > > I am opened to every alternatives of changing system vm templates > > I just need to run K8s clyusters 1.28 with my CS 4.16 :) > > > > Le lun. 8 avr. 2024 à 16:52, benoit lair a > écrit : > > > >> Hello Folks, > >> > >> I am trying to install K8s cluster with community iso 1.28.4 > >> I am with a ACS 4.16.0 environment > >> It seems K8S is not working out of the box with v > 1.23.3 due to > >> containerd.io version > >> > >> I would like to release a template who will work with K8s > 1.23.3 on > acs > >> 4.16 > >> How can i tell CS to take another system vm template, avoiding to mess > >> normal features with VR and VPC VR keeping the systemvm template issued > >> with CS 4.16 ? > >> > >> I am with XCP-NG 8.2.1 in production > >> > >> Thanks for your help or advises > >> Best regards, > >> Benoit > >> > > >
Re: ACS 4.16 - Change SystemVM template for CKS
errors occurred: [ERROR CRI]: container runtime is not running: output: E0411 11:38:11.935458 12988 remote_runtime.go:948] "Status from runtime service failed" err="rpc error: code = Unimplemented desc = unknown service runtime.v1alpha2.RuntimeService" time="2024-04-11T11:38:11Z" level=fatal msg="getting status of runtime: rpc error: code = Unimplemented desc = unknown service runtime.v1alpha2.RuntimeService" , error: exit status 1 [preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...` To see the stack trace of this error execute with --v=5 or higher [init] Using Kubernetes version: v1.25.0 [preflight] Running pre-flight checks [WARNING SystemVerification]: missing optional cgroups: blkio error execution phase preflight: [preflight] Some fatal errors occurred: [ERROR CRI]: container runtime is not running: output: E0411 11:38:12.079422 13015 remote_runtime.go:948] "Status from runtime service failed" err="rpc error: code = Unimplemented desc = unknown service runtime.v1alpha2.RuntimeService" time="2024-04-11T11:38:12Z" level=fatal msg="getting status of runtime: rpc error: code = Unimplemented desc = unknown service runtime.v1alpha2.RuntimeService" , error: exit status 1 [preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...` To see the stack trace of this error execute with --v=5 or higher [init] Using Kubernetes version: v1.25.0 [preflight] Running pre-flight checks [WARNING SystemVerification]: missing optional cgroups: blkio error execution phase preflight: [preflight] Some fatal errors occurred: [ERROR CRI]: container runtime is not running: output: E0411 11:38:12.228669 13043 remote_runtime.go:948] "Status from runtime service failed" err="rpc error: code = Unimplemented desc = unknown service runtime.v1alpha2.RuntimeService" time="2024-04-11T11:38:12Z" level=fatal msg="getting status of runtime: rpc error: code = Unimplemented desc = unknown service runtime.v1alpha2.RuntimeService" , error: exit status 1 [preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...` To see the stack trace of this error execute with --v=5 or higher Error: kubeadm init failed! Le jeu. 11 avr. 2024 à 12:03, Rohit Yadav a écrit : > Hi Benoit, > > The CKS feature has been improving over versions, I don't know if what > you're trying to achieve is possible with it. Maybe try a different version > of the data iso: > http://download.cloudstack.org/cks/ > > Alternatively, you can also have a look at the CAPC project: > https://cluster-api-cloudstack.sigs.k8s.io > > > Regards. > > > > > > From: benoit lair > Sent: Thursday, April 11, 2024 14:16 > To: us...@cloudstack.apache.org ; dev < > dev@cloudstack.apache.org> > Subject: Re: ACS 4.16 - Change SystemVM template for CKS > > Any advices ? > > Best regards > > Le lun. 8 avr. 2024 à 16:53, benoit lair a écrit : > > > I am opened to every alternatives of changing system vm templates > > I just need to run K8s clyusters 1.28 with my CS 4.16 :) > > > > Le lun. 8 avr. 2024 à 16:52, benoit lair a > écrit : > > > >> Hello Folks, > >> > >> I am trying to install K8s cluster with community iso 1.28.4 > >> I am with a ACS 4.16.0 environment > >> It seems K8S is not working out of the box with v > 1.23.3 due to > >> containerd.io version > >> > >> I would like to release a template who will work with K8s > 1.23.3 on > acs > >> 4.16 > >> How can i tell CS to take another system vm template, avoiding to mess > >> normal features with VR and VPC VR keeping the systemvm template issued > >> with CS 4.16 ? > >> > >> I am with XCP-NG 8.2.1 in production > >> > >> Thanks for your help or advises > >> Best regards, > >> Benoit > >> > > >
Re: ACS 4.16 - Change SystemVM template for CKS
On Thursday 11 April 2024 03:46:49 PM (+07:00), benoit lair wrote: > Any advices ? > > Best regards Im headed down the exact same path with debian manager and xcp-ng 8.2.1 so i can see how the CKS works, only im on 4.19, i also used shapeblues image happy to help once im at that point, its a fresh install > > Le lun. 8 avr. 2024 à 16:53, benoit lair a écrit : > > > I am opened to every alternatives of changing system vm templates > > I just need to run K8s clyusters 1.28 with my CS 4.16 :) > > > > Le lun. 8 avr. 2024 à 16:52, benoit lair a écrit : > > > >> Hello Folks, > >> > >> I am trying to install K8s cluster with community iso 1.28.4 > >> I am with a ACS 4.16.0 environment > >> It seems K8S is not working out of the box with v > 1.23.3 due to > >> containerd.io version > >> > >> I would like to release a template who will work with K8s > 1.23.3 on acs > >> 4.16 > >> How can i tell CS to take another system vm template, avoiding to mess > >> normal features with VR and VPC VR keeping the systemvm template issued > >> with CS 4.16 ? > >> > >> I am with XCP-NG 8.2.1 in production > >> > >> Thanks for your help or advises > >> Best regards, > >> Benoit > >> > > > -- Sent with Vivaldi Mail. Download Vivaldi for free at vivaldi.com
Re: ACS 4.16 - Change SystemVM template for CKS
Hi Benoit, The CKS feature has been improving over versions, I don't know if what you're trying to achieve is possible with it. Maybe try a different version of the data iso: http://download.cloudstack.org/cks/ Alternatively, you can also have a look at the CAPC project: https://cluster-api-cloudstack.sigs.k8s.io Regards. From: benoit lair Sent: Thursday, April 11, 2024 14:16 To: us...@cloudstack.apache.org ; dev Subject: Re: ACS 4.16 - Change SystemVM template for CKS Any advices ? Best regards Le lun. 8 avr. 2024 à 16:53, benoit lair a écrit : > I am opened to every alternatives of changing system vm templates > I just need to run K8s clyusters 1.28 with my CS 4.16 :) > > Le lun. 8 avr. 2024 à 16:52, benoit lair a écrit : > >> Hello Folks, >> >> I am trying to install K8s cluster with community iso 1.28.4 >> I am with a ACS 4.16.0 environment >> It seems K8S is not working out of the box with v > 1.23.3 due to >> containerd.io version >> >> I would like to release a template who will work with K8s > 1.23.3 on acs >> 4.16 >> How can i tell CS to take another system vm template, avoiding to mess >> normal features with VR and VPC VR keeping the systemvm template issued >> with CS 4.16 ? >> >> I am with XCP-NG 8.2.1 in production >> >> Thanks for your help or advises >> Best regards, >> Benoit >> >
Re: ACS 4.16 - Change SystemVM template for CKS
Any advices ? Best regards Le lun. 8 avr. 2024 à 16:53, benoit lair a écrit : > I am opened to every alternatives of changing system vm templates > I just need to run K8s clyusters 1.28 with my CS 4.16 :) > > Le lun. 8 avr. 2024 à 16:52, benoit lair a écrit : > >> Hello Folks, >> >> I am trying to install K8s cluster with community iso 1.28.4 >> I am with a ACS 4.16.0 environment >> It seems K8S is not working out of the box with v > 1.23.3 due to >> containerd.io version >> >> I would like to release a template who will work with K8s > 1.23.3 on acs >> 4.16 >> How can i tell CS to take another system vm template, avoiding to mess >> normal features with VR and VPC VR keeping the systemvm template issued >> with CS 4.16 ? >> >> I am with XCP-NG 8.2.1 in production >> >> Thanks for your help or advises >> Best regards, >> Benoit >> >
Re: ACS 4.16 - Change SystemVM template for CKS
I am opened to every alternatives of changing system vm templates I just need to run K8s clyusters 1.28 with my CS 4.16 :) Le lun. 8 avr. 2024 à 16:52, benoit lair a écrit : > Hello Folks, > > I am trying to install K8s cluster with community iso 1.28.4 > I am with a ACS 4.16.0 environment > It seems K8S is not working out of the box with v > 1.23.3 due to > containerd.io version > > I would like to release a template who will work with K8s > 1.23.3 on acs > 4.16 > How can i tell CS to take another system vm template, avoiding to mess > normal features with VR and VPC VR keeping the systemvm template issued > with CS 4.16 ? > > I am with XCP-NG 8.2.1 in production > > Thanks for your help or advises > Best regards, > Benoit >
ACS 4.16 - Change SystemVM template for CKS
Hello Folks, I am trying to install K8s cluster with community iso 1.28.4 I am with a ACS 4.16.0 environment It seems K8S is not working out of the box with v > 1.23.3 due to containerd.io version I would like to release a template who will work with K8s > 1.23.3 on acs 4.16 How can i tell CS to take another system vm template, avoiding to mess normal features with VR and VPC VR keeping the systemvm template issued with CS 4.16 ? I am with XCP-NG 8.2.1 in production Thanks for your help or advises Best regards, Benoit
