Hi Vladimir, The repository https://github.com/aws/cluster-api-provider-cloudstack under transition/donated to cncf's kubernetes-sigs. Pl test the integration and give us feedback. You may need to build the capi provider yourself (we'll be publishing the container image soon after the migration) and you can either build the templates on your own or test with http://download.cloudstack.org/templates/capi/
Regards. ________________________________ From: Vladimir Dombrovski <[email protected]> Sent: Tuesday, March 8, 2022 19:03 To: [email protected] <[email protected]> Subject: Re: Kubernetes ClusterAPI integration Hi Nux, Thank you for the heads up. This does look very promising, we'll try to set up and test this integration. Regards, Vladimir On Mon, 7 Mar 2022 at 14:13, Nux <[email protected]> wrote: > > Hi Vladimir, > > It looks like a CAPI provider for Cloudstack was developed already and > is now ready to be used, see the announcement. > https://markmail.org/thread/qmrc42csrqhpsv5m > > --- > Nux! > www.nux.ro > > On 2021-10-15 17:04, Vladimir Dombrovski wrote: > > Hello, > > > > We are currently looking into using Kubernetes inside Cloudstack. We > > have successfully tested the Kubernetes provider, which as it stands > > leverages a good amount of effort required to deploy the solution. > > > > However, we would like to go further with this, especially in order to > > provision and maintain multiple isolated K8S clusters on-demand. As it > > stands, a widely used solution for this would be ClusterAPI, which > > Cloudstack isn't listed on, as there is currently no cluster-api > > provider for it > > (https://cluster-api.sigs.k8s.io/reference/providers.html). We are > > seriously considering writing an implementation for it, which is why > > we are polling for potential interest in this thread. > > > > Do you think that there would be an interest around integrating > > Cloudstack with ClusterAPI as of today? Also would this conflict with > > either the currently available provider, or in terms of > > keeping/working on strictly Apache licensed projects? Or maybe some > > obvious missing components/API calls required to make it work? > > > > Vladimir -- *CONFIDENTIALITY AND DISCLAIMER NOTICE: * This email is intended only for the person to whom it is addressed and/or otherwise authorized personnel. The information contained herein and attached is confidential. If you are not the intended recipient, please be advised that viewing this message and any attachments, as well as copying, forwarding, printing, and disseminating any information related to this email is prohibited, and that you should not take any action based on the content of this email and/or its attachments. If you received this message in error, please contact the sender and destroy all copies of this email and any attachment. Please note that the views and opinions expressed herein are solely those of the author and do not necessarily reflect those of the company. While antivirus protection tools have been employed, you should check this email and attachments for the presence of viruses. No warranties or assurances are made in relation to the safety and content of this email and attachments. The Company accepts no liability for any damage caused by any virus transmitted by or contained in this email and attachments. No liability is accepted for any consequences arising from this email. *AVIS DE CONFIDENTIALITÉ ET DE NON RESPONSABILITE* : Ce courriel, ainsi que toute pièce jointe, est confidentiel et peut être protégé par le secret professionnel. Si vous n’en êtes pas le destinataire visé, veuillez en aviser l’expéditeur immédiatement et le supprimer. Vous ne devez pas le copier, ni l’utiliser à quelque fin que ce soit, ni divulguer son contenu à qui que ce soit. BSO se réserve le droit de contrôler toute transmission qui passe par son réseau. Veuillez noter que les opinions exprimées dans cet e-mail sont uniquement celles de l'auteur et ne reflètent pas nécessairement celles de la société. Bien que des outils de protection antivirus aient été utilisés, vous devez vérifier cet e-mail et les pièces jointes pour toute présence de virus. Aucune garantie ou assurance n'est donnée concernant la sécurité et le contenu de cet e-mail et de ses pièces jointes. La Société décline toute responsabilité pour tout dommage causé par tout virus transmis par ou contenu dans cet e-mail et ses pièces jointes. Aucune responsabilité n'est acceptée pour les conséquences découlant de cet e-mail.
