[jira] [Updated] (CLOUDSTACK-10443) CloudStack Terraform Provider - Add support for Kubernetes Clusters

["David Jumani (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-10443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Jumani updated CLOUDSTACK-10443:
--------------------------------------
    Description: 
As of now the CloudStack Terraform Provider does not support managing CKS clusters

This proposal aims to add support to the CloudStack Terraform Provider to manage CKS clusters

This would involve supporting the following actions on CKS clusters :
- Create
- Stop / Start
- Scale
- Upgrade
- Delete

#### [Optional]
Support the following actions on the binary ISOs :
- Register
- Enable / Disable
- Delete

## Difficulty
Medium

## Duration
175 hours

## Potential Mentors
- Harikrishna Patnala
- David Jumani

## References
https://github.com/apache/cloudstack/issues/6040

 

  was:
To provide easy access to VMs without the need for password-based authentication, Cloudstack provides users with the ability to set or reset an SSH key for their VMs. These SSH keys can either be uploaded to, or generated by cloudstack.
As of now, it is limited to just a single SSH key. This requires the key to be shared amongst users with access to the VM and can be quite cumbersome when there are several VMs (perhaps across different projects), each with a different SSH key. It can also cause issues when a user is removed and the key needs to be reset since it's a common key, and shared to the remaining users all over again.

This feature proposes extending the functionality to allow multiple SSH keys to be set / reset on a VM. This will allow users to add their own personal SSH key to the VM, thereby allowing them to directly access the VM without the need to manage multiple shared keys. New users can add their own keys to the list and access the VM instantly. It also solves the problem when a user is removed as their key can be removed from the list, thereby revoking their access without the need for a new key to be regenerated and shared.

It proposes the following changes :
 # Modify the API to accept multiple SSH keys
 # Change the service layer that handles the request
 # Alter the database accordingly
 # Update the UI to align with the new API

It requires the following relevant skills :
 * Java (basic)
 * SQL (basic)
 * Javascript (basic)
 * VueJS (Learning on the fly)

Further details can be found here 
 [https://github.com/apache/cloudstack/issues/4813]

 


> CloudStack Terraform Provider - Add support for Kubernetes Clusters
> -------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-10443
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10443
>             Project: CloudStack
>          Issue Type: Improvement
>            Reporter: David Jumani
>            Priority: Major
>              Labels: gsoc2021, mentor
>
> As of now the CloudStack Terraform Provider does not support managing CKS clusters
> This proposal aims to add support to the CloudStack Terraform Provider to manage CKS clusters
> This would involve supporting the following actions on CKS clusters :
> - Create
> - Stop / Start
> - Scale
> - Upgrade
> - Delete
> #### [Optional]
> Support the following actions on the binary ISOs :
> - Register
> - Enable / Disable
> - Delete
> ## Difficulty
> Medium
> ## Duration
> 175 hours
> ## Potential Mentors
> - Harikrishna Patnala
> - David Jumani
> ## References
> https://github.com/apache/cloudstack/issues/6040
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)