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 <ustcweiz...@gmail.com> 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 <kurushi4...@gmail.com> 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 ? > > >
