[
https://issues.apache.org/jira/browse/CLOUDSTACK-10444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jumani updated CLOUDSTACK-10444:
--------------------------------------
Description:
ClouStack Kubernetes Service [CKS] is CloudStack's own managed Kubernetes
offering which users can use to deploy and manage Kubernetes Clusters from
CloudStack. However, there might be cases in which users may want to deploy
their own Virtual Machines and convert them into Kubernetes Nodes to run their
own personally managed Kubernetes Clusters outside the scope of CloudStack.
In such cases, CloudStack is unaware of these clusters and sees them as just a
bunch of VMs running on its infrastructure. Although this might be acceptable,
it would be a good idea for users to make CloudStack aware of the existing
unmanaged Kubernetes Clusters and be able to view them in the UI or via an API
Provide the ability to make CloudStack aware of these unmanaged Kubernetes
Clusters
Add / Modify existing API (and/or UI) support to :
* Add an unmanaged Kubernetes Cluster
* Update an unmanaged Kubernetes Cluster
* Delete an unmanaged Kubernetes Cluster
Duration
* 175 hours
Potential Mentors
- David Jumani
- Abhishek Kumar
References
* [https://github.com/apache/cloudstack/issues/6036]
was:
ClouStack Kubernetes Service [CKS] is CloudStack's own managed Kubernetes
offering which users can use to deploy and manage Kubernetes Clusters from
CloudStack. However, there might be cases in which users may want to deploy
their own Virtual Machines and convert them into Kubernetes Nodes to run their
own personally managed Kubernetes Clusters outside the scope of CloudStack.
In such cases, CloudStack is unaware of these clusters and sees them as just a
bunch of VMs running on its infrastructure. Although this might be acceptable,
it would be a good idea for users to make CloudStack aware of the existing
unmanaged Kubernetes Clusters and be able to view them in the UI or via an API
Provide the ability to make CloudStack aware of these unmanaged Kubernetes
Clusters
Add / Modify existing API (and/or UI) support to :
* Add an unmanaged Kubernetes Cluster
* Update an unmanaged Kubernetes Cluster
* Delete an unmanaged Kubernetes Cluster
Duration
* 175 hours
Potential Mentors
- David Jumani
References
* https://github.com/apache/cloudstack/issues/6036
> Make CloudStack aware of Unmanaged Kubernetes Clusters
> ------------------------------------------------------
>
> Key: CLOUDSTACK-10444
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10444
> Project: CloudStack
> Issue Type: New Feature
> Reporter: David Jumani
> Priority: Major
> Labels: gsoc2022, mentor
>
> ClouStack Kubernetes Service [CKS] is CloudStack's own managed Kubernetes
> offering which users can use to deploy and manage Kubernetes Clusters from
> CloudStack. However, there might be cases in which users may want to deploy
> their own Virtual Machines and convert them into Kubernetes Nodes to run
> their own personally managed Kubernetes Clusters outside the scope of
> CloudStack.
> In such cases, CloudStack is unaware of these clusters and sees them as just
> a bunch of VMs running on its infrastructure. Although this might be
> acceptable, it would be a good idea for users to make CloudStack aware of the
> existing unmanaged Kubernetes Clusters and be able to view them in the UI or
> via an API
> Provide the ability to make CloudStack aware of these unmanaged Kubernetes
> Clusters
> Add / Modify existing API (and/or UI) support to :
> * Add an unmanaged Kubernetes Cluster
> * Update an unmanaged Kubernetes Cluster
> * Delete an unmanaged Kubernetes Cluster
>
> Duration
> * 175 hours
>
> Potential Mentors
> - David Jumani
> - Abhishek Kumar
>
> References
> * [https://github.com/apache/cloudstack/issues/6036]
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
