Re: CKS Storage Provisioner Info

[Bharat Bhushan Saini]

Hi Wei,

I am using shared network in the cluster with untagged as my network is 
isolated and it is provided by bridge internally.

Please suggest can i do through network offering!

Thanks and Regards,
Bharat Saini

[signature_3569743506]

From: Wei ZHOU 
Date: Wednesday, 28 February 2024 at 4:40 PM
To: users@cloudstack.apache.org 
Subject: Re: CKS Storage Provisioner Info
EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.


Hi,

Are you using a Shared network ? If yes, it will not work

-Wei

On Wed, Feb 28, 2024 at 11:17 AM Bharat Bhushan Saini
 wrote:

> Hi Wei,
>
>
>
> Just to inform you that I am able to ping management ip from a pod which I
> deployed for testing.
>
> Please refer below logs
>
>
>
> ping 10.x.xx.101
>
> PING 10.x.xx.101 (10.x.xx.101) 56(84) bytes of data.
>
> 64 bytes from 10.x.xx.101: icmp_seq=1 ttl=63 time=0.430 ms
>
> 64 bytes from 10.x.xx.101: icmp_seq=2 ttl=63 time=0.420 ms
>
> ^C
>
> --- 10.x.xx.101 ping statistics ---
>
> 2 packets transmitted, 2 received, 0% packet loss, time 1014ms
>
> rtt min/avg/max/mdev = 0.420/0.425/0.430/0.005 ms
>
>
>
> Also I done some more changes now the error was some different. Please
> have a look below
>
>
>
> Error syncing load balancer: failed to ensure load balancer: error
> associating new IP address: CloudStack API error 431 (CSExceptionErrorCode:
> 4350): Associate IP address can only be called on the shared networks in
> the advanced zone with Firewall/Source Nat/Static Nat/Port Forwarding/Load
> balancing services enabled
>
>
>
> @Jayanth,@Vivek, please have a look on that.
>
>
>
> Thanks and Regards,
>
> Bharat Saini
>
>
>
> [image: signature_1434537425]
>
>
>
> *From: *Wei ZHOU 
> *Date: *Wednesday, 28 February 2024 at 1:21 PM
> *To: *users@cloudstack.apache.org 
> *Subject: *Re: CKS Storage Provisioner Info
>
> EXTERNAL EMAIL: Please verify the sender email address before taking any
> action, replying, clicking any link or opening any attachment.
>
>
> Hi,
>
> The CloudStack management server must be accessible from the pod
> "cloud-controller-manager" in the CKS cluster.
>
> It looks like the issue is caused by your network configuration, not
> CloudStack.
>
> -Wei
>
> On Wed, Feb 28, 2024 at 7:19 AM Bharat Bhushan Saini
>  wrote:
>
> > Hi Kiran,
> >
> >
> >
> > I used a private ip range which is bridged in my internal organisation
> > network.
> >
> >
> >
> > JUST FYI, I also tested a simple deployment but it is also didn’t took
> > external ip.
> >
> >
> >
> >
> >
> > Thanks and Regards,
> >
> > Bharat Saini
> >
> >
> >
>
> --- Disclaimer: --
> This message and its contents are intended solely for the designated
> addressee and are proprietary to Kloudspot. The information in this email
> is meant exclusively for Kloudspot business use. Any use by individuals
> other than the addressee constitutes misuse and an infringement of
> Kloudspot's proprietary rights. If you are not the intended recipient,
> please return this email to the sender. Kloudspot cannot guarantee the
> security or error-free transmission of e-mail communications. Information
> could be intercepted, corrupted, lost, destroyed, arrive late or
> incomplete, or contain viruses. Therefore, Kloudspot shall not be liable
> for any issues arising from the transmission of this email.
>

--- Disclaimer: --
This message and its contents are intended solely for the designated addressee 
and are proprietary to Kloudspot. The information in this email is meant 
exclusively for Kloudspot business use. Any use by individuals other than the 
addressee constitutes misuse and an infringement of Kloudspot's proprietary 
rights. If you are not the intended recipient, please return this email to the 
sender. Kloudspot cannot guarantee the security or error-free transmission of 
e-mail communications. Information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or contain viruses. Therefore, Kloudspot 
shall not be liable for any issues arising from the transmission of this email.

Re: CKS Storage Provisioner Info

[Wei ZHOU]

Hi,

Are you using a Shared network ? If yes, it will not work

-Wei

On Wed, Feb 28, 2024 at 11:17 AM Bharat Bhushan Saini
 wrote:

> Hi Wei,
>
>
>
> Just to inform you that I am able to ping management ip from a pod which I
> deployed for testing.
>
> Please refer below logs
>
>
>
> ping 10.x.xx.101
>
> PING 10.x.xx.101 (10.x.xx.101) 56(84) bytes of data.
>
> 64 bytes from 10.x.xx.101: icmp_seq=1 ttl=63 time=0.430 ms
>
> 64 bytes from 10.x.xx.101: icmp_seq=2 ttl=63 time=0.420 ms
>
> ^C
>
> --- 10.x.xx.101 ping statistics ---
>
> 2 packets transmitted, 2 received, 0% packet loss, time 1014ms
>
> rtt min/avg/max/mdev = 0.420/0.425/0.430/0.005 ms
>
>
>
> Also I done some more changes now the error was some different. Please
> have a look below
>
>
>
> Error syncing load balancer: failed to ensure load balancer: error
> associating new IP address: CloudStack API error 431 (CSExceptionErrorCode:
> 4350): Associate IP address can only be called on the shared networks in
> the advanced zone with Firewall/Source Nat/Static Nat/Port Forwarding/Load
> balancing services enabled
>
>
>
> @Jayanth,@Vivek, please have a look on that.
>
>
>
> Thanks and Regards,
>
> Bharat Saini
>
>
>
> [image: signature_1434537425]
>
>
>
> *From: *Wei ZHOU 
> *Date: *Wednesday, 28 February 2024 at 1:21 PM
> *To: *users@cloudstack.apache.org 
> *Subject: *Re: CKS Storage Provisioner Info
>
> EXTERNAL EMAIL: Please verify the sender email address before taking any
> action, replying, clicking any link or opening any attachment.
>
>
> Hi,
>
> The CloudStack management server must be accessible from the pod
> "cloud-controller-manager" in the CKS cluster.
>
> It looks like the issue is caused by your network configuration, not
> CloudStack.
>
> -Wei
>
> On Wed, Feb 28, 2024 at 7:19 AM Bharat Bhushan Saini
>  wrote:
>
> > Hi Kiran,
> >
> >
> >
> > I used a private ip range which is bridged in my internal organisation
> > network.
> >
> >
> >
> > JUST FYI, I also tested a simple deployment but it is also didn’t took
> > external ip.
> >
> >
> >
> >
> >
> > Thanks and Regards,
> >
> > Bharat Saini
> >
> >
> >
>
> --- Disclaimer: --
> This message and its contents are intended solely for the designated
> addressee and are proprietary to Kloudspot. The information in this email
> is meant exclusively for Kloudspot business use. Any use by individuals
> other than the addressee constitutes misuse and an infringement of
> Kloudspot's proprietary rights. If you are not the intended recipient,
> please return this email to the sender. Kloudspot cannot guarantee the
> security or error-free transmission of e-mail communications. Information
> could be intercepted, corrupted, lost, destroyed, arrive late or
> incomplete, or contain viruses. Therefore, Kloudspot shall not be liable
> for any issues arising from the transmission of this email.
>

Re: CKS Storage Provisioner Info

[Bharat Bhushan Saini]

Hi Wei,

Just to inform you that I am able to ping management ip from a pod which I 
deployed for testing.
Please refer below logs

ping 10.x.xx.101
PING 10.x.xx.101 (10.x.xx.101) 56(84) bytes of data.
64 bytes from 10.x.xx.101: icmp_seq=1 ttl=63 time=0.430 ms
64 bytes from 10.x.xx.101: icmp_seq=2 ttl=63 time=0.420 ms
^C
--- 10.x.xx.101 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1014ms
rtt min/avg/max/mdev = 0.420/0.425/0.430/0.005 ms

Also I done some more changes now the error was some different. Please have a 
look below


Error syncing load balancer: failed to ensure load balancer: error associating 
new IP address: CloudStack API error 431 (CSExceptionErrorCode: 4350): 
Associate IP address can only be called on the shared networks in the advanced 
zone with Firewall/Source Nat/Static Nat/Port Forwarding/Load balancing 
services enabled

@Jayanth,@Vivek, please have a look on that.

Thanks and Regards,
Bharat Saini

[signature_1434537425]

From: Wei ZHOU 
Date: Wednesday, 28 February 2024 at 1:21 PM
To: users@cloudstack.apache.org 
Subject: Re: CKS Storage Provisioner Info
EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.


Hi,

The CloudStack management server must be accessible from the pod
"cloud-controller-manager" in the CKS cluster.

It looks like the issue is caused by your network configuration, not
CloudStack.

-Wei

On Wed, Feb 28, 2024 at 7:19 AM Bharat Bhushan Saini
 wrote:

> Hi Kiran,
>
>
>
> I used a private ip range which is bridged in my internal organisation
> network.
>
>
>
> JUST FYI, I also tested a simple deployment but it is also didn’t took
> external ip.
>
>
>
>
>
> Thanks and Regards,
>
> Bharat Saini
>
>
>

--- Disclaimer: --
This message and its contents are intended solely for the designated addressee 
and are proprietary to Kloudspot. The information in this email is meant 
exclusively for Kloudspot business use. Any use by individuals other than the 
addressee constitutes misuse and an infringement of Kloudspot's proprietary 
rights. If you are not the intended recipient, please return this email to the 
sender. Kloudspot cannot guarantee the security or error-free transmission of 
e-mail communications. Information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or contain viruses. Therefore, Kloudspot 
shall not be liable for any issues arising from the transmission of this email.

Re: CKS Storage Provisioner Info

[Wei ZHOU]

Hi,

The CloudStack management server must be accessible from the pod
"cloud-controller-manager" in the CKS cluster.

It looks like the issue is caused by your network configuration, not
CloudStack.

-Wei

On Wed, Feb 28, 2024 at 7:19 AM Bharat Bhushan Saini
 wrote:

> Hi Kiran,
>
>
>
> I used a private ip range which is bridged in my internal organisation
> network.
>
>
>
> JUST FYI, I also tested a simple deployment but it is also didn’t took
> external ip.
>
>
>
>
>
> Thanks and Regards,
>
> Bharat Saini
>
>
>

Re: CKS Storage Provisioner Info

[Jayanth Babu A]

Hello Bharat,
Please confirm if you’re using self-signed or a signed certificate from trusted 
CA on your management server API endpoint. The error indicates that the CKS 
cannot complete the TLS handshake due to the common name or SAN mismatch.
It is usually advised to put Trusted CA signed-certificates and have the proper 
domain names or SAN that match the certificate. Please change the endpoint 
domain name accordingly in the global configuration setting “endpoint.url” and 
ensure the CKS nodes or network is able to resolve and connect to it.

Thanks,
Jayanth

From: Bharat Bhushan Saini 
Date: Wednesday, 28 February 2024 at 10:19
To: users@cloudstack.apache.org 
Subject: Re: CKS Storage Provisioner Info
Hi Jayanth,

I shows below

Error syncing load balancer: failed to ensure load balancer: error retrieving 
load balancer rules: Get 
https://checkpoint.url-protection.com/v1/url?o=https%3A//10.x.x.2%3A8443/client/api%3FapiKey%3Dk83H56KFdhFqpv7cXPU11nkwxPt8f2rXnm1WWVIRdeErqZr72Pzp7ySmricPWs7FQQuMmClznDhMz7uqnRD2wA%26amp%3Bcommand%3DlistLoadBalancerRules%26amp%3Bkeyword%3Da85de8a8ca0f543cca49e06fc3f30791%26amp%3Blistall%3Dtrue%26amp%3Bresponse%3Djson%26amp%3Bsignature%3DHVQNyOboMkqp4rwQYY6wLJ1NBzY%253D%3A=ZDM3OWY0MmUwMWVmMGVlMA===YTJhNGFiMWNiNzY1YWE1YWYzOTdhMzk0ZjlkNDkwYTgyMDNjOGQ5ZDU0ODM4MDcxMjAyNjQzOGM4MGI3NTFhZg===Y3AxZTpueHRnZW5pbmZpbml0ZWRhdGFjZW50ZXI6YzpvOjNiNDk1M2JiNmRjNDE0OGZlYmU4NTY0YmUzYjA4ODU4OnYxOnQ6VA==
 x509: cannot validate certificate for 10.x.x.2 because it doesn't contain any 
IP SANs

Can I put API URL as management URL?

Thanks and Regards,
Bharat Saini

[signature_1763564491]

From: Jayanth Babu A 
Date: Wednesday, 28 February 2024 at 10:15 AM
To: users@cloudstack.apache.org 
Subject: Re: CKS Storage Provisioner Info
EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.


Hello Bharat,
What does “# kubectl describe svc/traefik” say?

Thanks,
Jayanth

From: Bharat Bhushan Saini 
Date: Wednesday, 28 February 2024 at 10:11
To: users@cloudstack.apache.org 
Subject: Re: CKS Storage Provisioner Info
Hi All,

I had some queries regarding CKS service

Why external IP is not shown in SVC. Do we have any resolvent for this and 
traefik service is in pending state as I have 1 control and 1 worker node.

kubectl get svc

NAME TYPE   CLUSTER-IP   EXTERNAL-IP   PORT(S)  
AGE

kubernetes   ClusterIP  10.96.0.1443/TCP  
39h

nginx-nodeport   NodePort   10.110.79.87 80:30918/TCP 
15h

nginx-serviceNodePort   10.110.244.170   80:32180/TCP 
17h

traefik  LoadBalancer   10.107.145.95 
80:32289/TCP,443:32426/TCP   17h

Inside the cluster the CLUSTER IP was continuous change by the 
SVC, I just login again and I saw that the CLUSTER IP is different from 
yesterday.

Thanks and Regards,
Bharat Saini

[signature_3834506047]

From: Jayanth Babu A 
Date: Tuesday, 27 February 2024 at 11:26 AM
To: users@cloudstack.apache.org 
Subject: Re: CKS Storage Provisioner Info
EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.


Hello Bharat,
You’ve some well-known options as below:
https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner<https://checkpoint.url-protection.com/v1/url?o=https%3A//github.com/kubernetes-sigs/nfs-subdir-external-provisioner=MjVhNGRiMTM5ZmE4NDM5NQ===ZDFhZDE3YWFiZDhiOGYyOThhZjI2MDdhNDJjNjE4MmU0NDQ3ZDNlZDQ3MTMxYjYxYjEwOTM2OWE4NTc1OTVlNQ===Y3AxZTpueHRnZW5pbmZpbml0ZWRhdGFjZW50ZXI6YzpvOjg2NDk3YWEwMzU5NmQ5NWE3NmFlNGUxMmNkMmEzZmE5OnYxOmg6VA==><https://checkpoint.url-protection.com/v1/url?o=https%3A//github.com/kubernetes-sigs/nfs-subdir-external-provisioner%253chttps%3A/checkpoint.url-protection.com/v1/url%3Fo%3Dhttps%253A//github.com/kubernetes-sigs/nfs-subdir-external-provisioner%26amp%3Bg%3DMjVhNGRiMTM5ZmE4NDM5NQ%3D%3D%26amp%3Bh%3DZDFhZDE3YWFiZDhiOGYyOThhZjI2MDdhNDJjNjE4MmU0NDQ3ZDNlZDQ3MTMxYjYxYjEwOTM2OWE4NTc1OTVlNQ%3D%3D%26amp%3Bp%3DY3AxZTpueHRnZW5pbmZpbml0ZWRhdGFjZW50ZXI6YzpvOjg2NDk3YWEwMzU5NmQ5NWE3NmFlNGUxMmNkMmEzZmE5OnYxOmg6VA%3D%3D%253e=Y2I2ODNlM2RiZmMzOTdiNg===OGM4YmE0YTZiMzRiNjA3MzJlYjRhZThhMjVlMzNlNmMxYTBiZjlmMjdhODg2Y2I2OGFiOTViYjUzMGExMWUyMg===Y3AxZTpueHRnZW5pbmZpbml0ZWRhdGFjZW50ZXI6YzpvOjNiNDk1M2JiNmRjNDE0OGZlYmU4NTY0YmUzYjA4ODU4OnYxOmg6VA==>
https://github.com/rook/rook<https://checkpoint.url-protection.com/v1/url?o=https%3A//github.com/rook/rook=ZWQ0NWJlZDEyYjM0ODE3Nw===MjQzMTQ4ZDczMjQ3OTRkMzI4MjdlNmQ4ZTc4NzQ4OTY1ZjM4ZDlmZDEyODc0OTE3OTNkZGRhZGRlMjZhOTdhMQ===Y3AxZTpueHRnZW5pbmZpbml0ZWRhdGFjZW50ZXI6YzpvOjg2NDk3YWEwMzU5NmQ5NWE3NmFlNGUxMmNkMmEzZmE5OnYxOmg6VA==><https://checkpoint.url-protection.com/v1/url?o=https%3A//github.com/rook/rook%253chttps%3A/checkpoint.url-protection.com/v1/url%3Fo%3Dhttps%253A//githu

Re: CKS Storage Provisioner Info

[Jayanth Babu A]

Hello Bharat,
What does “# kubectl describe svc/traefik” say?

Thanks,
Jayanth

From: Bharat Bhushan Saini 
Date: Wednesday, 28 February 2024 at 10:11
To: users@cloudstack.apache.org 
Subject: Re: CKS Storage Provisioner Info
Hi All,

I had some queries regarding CKS service

Why external IP is not shown in SVC. Do we have any resolvent for this and 
traefik service is in pending state as I have 1 control and 1 worker node.

kubectl get svc

NAME TYPE   CLUSTER-IP   EXTERNAL-IP   PORT(S)  
AGE

kubernetes   ClusterIP  10.96.0.1443/TCP  
39h

nginx-nodeport   NodePort   10.110.79.87 80:30918/TCP 
15h

nginx-serviceNodePort   10.110.244.170   80:32180/TCP 
17h

traefik  LoadBalancer   10.107.145.95 
80:32289/TCP,443:32426/TCP   17h

Inside the cluster the CLUSTER IP was continuous change by the 
SVC, I just login again and I saw that the CLUSTER IP is different from 
yesterday.

Thanks and Regards,
Bharat Saini

[signature_3834506047]

From: Jayanth Babu A 
Date: Tuesday, 27 February 2024 at 11:26 AM
To: users@cloudstack.apache.org 
Subject: Re: CKS Storage Provisioner Info
EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.


Hello Bharat,
You’ve some well-known options as below:
https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner<https://checkpoint.url-protection.com/v1/url?o=https%3A//github.com/kubernetes-sigs/nfs-subdir-external-provisioner=MjVhNGRiMTM5ZmE4NDM5NQ===ZDFhZDE3YWFiZDhiOGYyOThhZjI2MDdhNDJjNjE4MmU0NDQ3ZDNlZDQ3MTMxYjYxYjEwOTM2OWE4NTc1OTVlNQ===Y3AxZTpueHRnZW5pbmZpbml0ZWRhdGFjZW50ZXI6YzpvOjg2NDk3YWEwMzU5NmQ5NWE3NmFlNGUxMmNkMmEzZmE5OnYxOmg6VA==>
https://github.com/rook/rook<https://checkpoint.url-protection.com/v1/url?o=https%3A//github.com/rook/rook=ZWQ0NWJlZDEyYjM0ODE3Nw===MjQzMTQ4ZDczMjQ3OTRkMzI4MjdlNmQ4ZTc4NzQ4OTY1ZjM4ZDlmZDEyODc0OTE3OTNkZGRhZGRlMjZhOTdhMQ===Y3AxZTpueHRnZW5pbmZpbml0ZWRhdGFjZW50ZXI6YzpvOjg2NDk3YWEwMzU5NmQ5NWE3NmFlNGUxMmNkMmEzZmE5OnYxOmg6VA==>
 - CephFS & NFS can fit

Thanks,
Jayanth Reddy

From: Bharat Bhushan Saini 
Date: Tuesday, 27 February 2024 at 11:01
To: users@cloudstack.apache.org 
Subject: Re: CKS Storage Provisioner Info
Hi All,

Thanks for helping out for the storage provisioner.

In CKS service I am able to bound PVC as ReadWriteOnce with Leaseweb CloudStack 
CSI Driver.
Is there any opportunity in the cloudstack with other driver that I can bound 
storage as ReadWriteMany.

I tried with Leaseweb and got below warning
Warning  ProvisioningFailed6s (x5 over 21s)  
csi.cloudstack.apache.org_cloudstack-csi-controller-7f89c8cd47-ztllw_c6112933-3587-4445-8702-74b255b1e56f
  failed to provision volume with StorageClass "cloudstack-custom": rpc error: 
code = InvalidArgument desc = Volume capabilities not supported. Only 
SINGLE_NODE_WRITER supported.

Thanks and Regards,
Bharat Saini

[signature_636195584]

From: Kiran Chavala 
Date: Monday, 26 February 2024 at 5:54 PM
To: users@cloudstack.apache.org 
Subject: Re: CKS Storage Provisioner Info
EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.


Hi Bharath

Note the CKS provisioner works on KVM based cloudstack environment

Regards
Kiran

From: Kiran Chavala 
Date: Monday, 26 February 2024 at 5:45 PM
To: users@cloudstack.apache.org 
Subject: Re: CKS Storage Provisioner Info
Hi Bharat Bhusan

Please follow these steps


1. Deploy a Kubernetes cluster on cluster


NAME STATUS   ROLES   AGE VERSION
ty-control-18de52c04f7   Readycontrol-plane   5m11s   v1.28.4
ty-node-18de52c4185  Ready  4m55s   v1.28.4

kubectl get secrets -A
NAMESPACE  NAME  TYPE   
 DATA   AGE
kube-systemcloudstack-secret Opaque 
 1  10m



2. Check the deployment, it should  be in pending

~ kubectl get deployments -A
NAMESPACE  NAMEREADY   UP-TO-DATE   
AVAILABLE   AGE
kube-systemcloudstack-csi-controller   0/1 10   
46s


3. Edit the deployment and remove the nodeSelector part

~kubectl edit deployment/cloudstack-csi-controller -n kube-system


  nodeSelector:
kubernetes.io/os: linux
node-role.kubernetes.io/master: ""

4. Check the deployment again  and it should be running state

~kubectl get deployments -A
NAMESPACE  NAMEREADY   UP-TO-DATE   
AVAILABLE   AGE
kube-systemcloudstack-csi-controller   1/1 11   
2m39s

5. Replace the disk offering in the storage class yaml

Provide the custom disk offering UUID (service offe

Re: CKS Storage Provisioner Info

[Jayanth Babu A]

Hello Bharat,
You’ve some well-known options as below:
https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner
https://github.com/rook/rook - CephFS & NFS can fit

Thanks,
Jayanth Reddy

From: Bharat Bhushan Saini 
Date: Tuesday, 27 February 2024 at 11:01
To: users@cloudstack.apache.org 
Subject: Re: CKS Storage Provisioner Info
Hi All,

Thanks for helping out for the storage provisioner.

In CKS service I am able to bound PVC as ReadWriteOnce with Leaseweb CloudStack 
CSI Driver.
Is there any opportunity in the cloudstack with other driver that I can bound 
storage as ReadWriteMany.

I tried with Leaseweb and got below warning
Warning  ProvisioningFailed6s (x5 over 21s)  
csi.cloudstack.apache.org_cloudstack-csi-controller-7f89c8cd47-ztllw_c6112933-3587-4445-8702-74b255b1e56f
  failed to provision volume with StorageClass "cloudstack-custom": rpc error: 
code = InvalidArgument desc = Volume capabilities not supported. Only 
SINGLE_NODE_WRITER supported.

Thanks and Regards,
Bharat Saini

[signature_636195584]

From: Kiran Chavala 
Date: Monday, 26 February 2024 at 5:54 PM
To: users@cloudstack.apache.org 
Subject: Re: CKS Storage Provisioner Info
EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.


Hi Bharath

Note the CKS provisioner works on KVM based cloudstack environment

Regards
Kiran

From: Kiran Chavala 
Date: Monday, 26 February 2024 at 5:45 PM
To: users@cloudstack.apache.org 
Subject: Re: CKS Storage Provisioner Info
Hi Bharat Bhusan

Please follow these steps


1. Deploy a Kubernetes cluster on cluster


NAME STATUS   ROLES   AGE VERSION
ty-control-18de52c04f7   Readycontrol-plane   5m11s   v1.28.4
ty-node-18de52c4185  Ready  4m55s   v1.28.4

kubectl get secrets -A
NAMESPACE  NAME  TYPE   
 DATA   AGE
kube-systemcloudstack-secret Opaque 
 1  10m



2. Check the deployment, it should  be in pending

~ kubectl get deployments -A
NAMESPACE  NAMEREADY   UP-TO-DATE   
AVAILABLE   AGE
kube-systemcloudstack-csi-controller   0/1 10   
46s


3. Edit the deployment and remove the nodeSelector part

~kubectl edit deployment/cloudstack-csi-controller -n kube-system


  nodeSelector:
kubernetes.io/os: linux
node-role.kubernetes.io/master: ""

4. Check the deployment again  and it should be running state

~kubectl get deployments -A
NAMESPACE  NAMEREADY   UP-TO-DATE   
AVAILABLE   AGE
kube-systemcloudstack-csi-controller   1/1 11   
2m39s

5. Replace the disk offering in the storage class yaml

Provide the custom disk offering UUID (service offerings > disk offering > 
custom disk offering

4c518474-5d7b-4285-a07c-c57e214abb3b


vi 0-storageclass.yaml

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: cloudstack-custom
provisioner: csi.cloudstack.apache.org
reclaimPolicy: Delete
volumeBindingMode: WaitForFirstConsumer
allowVolumeExpansion: false
parameters:
  csi.cloudstack.apache.org/disk-offering-id: 
4c518474-5d7b-4285-a07c-c57e214abb3b


kubectl apply -f 0-storageclass.yaml

k8s git:(master) ✗ kubectl get sc
NAMEPROVISIONER RECLAIMPOLICY   
VOLUMEBINDINGMODE  ALLOWVOLUMEEXPANSION   AGE
cloudstack-custom   csi.cloudstack.apache.org   Delete  
WaitForFirstConsumer   false  72s



6. Apply the pvc yaml

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: example-pvc-block
spec:
  storageClassName: cloudstack-custom
  volumeMode: Block
  accessModes:
- ReadWriteOnce
  resources:
requests:
  storage: 1Gi


kubectl apply -f pvc-block.yaml

k8s git:(master) ✗ kubectl get pvc
NAMESTATUSVOLUME   CAPACITY   ACCESS MODES   STORAGECLASS   
 AGE
example-pvc-block   Pending  
cloudstack-custom   31s
7.  Apply the pod block yaml

apiVersion: v1
kind: Pod
metadata:
  name: example-pod-block
spec:
  containers:
- name: example
  image: ubuntu
  volumeDevices:
- devicePath: "/dev/example-block"
  name: example-volume
  stdin: true
  stdinOnce: true
  tty: true
  volumes:
- name: example-volume
  persistentVolumeClaim:
claimName: example-pvc-block


kubectl apply -f pod-block.yaml


➜  k8s git:(master) ✗ k get pods -A
NAMESPACE  NAME READY   
STATUSRESTARTS  AGE
defaultexample-pod-block1/1 
Running   0 107s

Events:
  TypeReason

Re: CKS Storage Provisioner Info

[Bharat Bhushan Saini]

Hi All,

Thanks for helping out for the storage provisioner.

In CKS service I am able to bound PVC as ReadWriteOnce with Leaseweb CloudStack 
CSI Driver.
Is there any opportunity in the cloudstack with other driver that I can bound 
storage as ReadWriteMany.

I tried with Leaseweb and got below warning
Warning  ProvisioningFailed6s (x5 over 21s)  
csi.cloudstack.apache.org_cloudstack-csi-controller-7f89c8cd47-ztllw_c6112933-3587-4445-8702-74b255b1e56f
  failed to provision volume with StorageClass "cloudstack-custom": rpc error: 
code = InvalidArgument desc = Volume capabilities not supported. Only 
SINGLE_NODE_WRITER supported.

Thanks and Regards,
Bharat Saini

[signature_636195584]

From: Kiran Chavala 
Date: Monday, 26 February 2024 at 5:54 PM
To: users@cloudstack.apache.org 
Subject: Re: CKS Storage Provisioner Info
EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.


Hi Bharath

Note the CKS provisioner works on KVM based cloudstack environment

Regards
Kiran

From: Kiran Chavala 
Date: Monday, 26 February 2024 at 5:45 PM
To: users@cloudstack.apache.org 
Subject: Re: CKS Storage Provisioner Info
Hi Bharat Bhusan

Please follow these steps


1. Deploy a Kubernetes cluster on cluster


NAME STATUS   ROLES   AGE VERSION
ty-control-18de52c04f7   Readycontrol-plane   5m11s   v1.28.4
ty-node-18de52c4185  Ready  4m55s   v1.28.4

kubectl get secrets -A
NAMESPACE  NAME  TYPE   
 DATA   AGE
kube-systemcloudstack-secret Opaque 
 1  10m



2. Check the deployment, it should  be in pending

~ kubectl get deployments -A
NAMESPACE  NAMEREADY   UP-TO-DATE   
AVAILABLE   AGE
kube-systemcloudstack-csi-controller   0/1 10   
46s


3. Edit the deployment and remove the nodeSelector part

~kubectl edit deployment/cloudstack-csi-controller -n kube-system


  nodeSelector:
kubernetes.io/os: linux
node-role.kubernetes.io/master: ""

4. Check the deployment again  and it should be running state

~kubectl get deployments -A
NAMESPACE  NAMEREADY   UP-TO-DATE   
AVAILABLE   AGE
kube-systemcloudstack-csi-controller   1/1 11   
2m39s

5. Replace the disk offering in the storage class yaml

Provide the custom disk offering UUID (service offerings > disk offering > 
custom disk offering

4c518474-5d7b-4285-a07c-c57e214abb3b


vi 0-storageclass.yaml

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: cloudstack-custom
provisioner: csi.cloudstack.apache.org
reclaimPolicy: Delete
volumeBindingMode: WaitForFirstConsumer
allowVolumeExpansion: false
parameters:
  csi.cloudstack.apache.org/disk-offering-id: 
4c518474-5d7b-4285-a07c-c57e214abb3b


kubectl apply -f 0-storageclass.yaml

k8s git:(master) ✗ kubectl get sc
NAMEPROVISIONER RECLAIMPOLICY   
VOLUMEBINDINGMODE  ALLOWVOLUMEEXPANSION   AGE
cloudstack-custom   csi.cloudstack.apache.org   Delete  
WaitForFirstConsumer   false  72s



6. Apply the pvc yaml

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: example-pvc-block
spec:
  storageClassName: cloudstack-custom
  volumeMode: Block
  accessModes:
- ReadWriteOnce
  resources:
requests:
  storage: 1Gi


kubectl apply -f pvc-block.yaml

k8s git:(master) ✗ kubectl get pvc
NAMESTATUSVOLUME   CAPACITY   ACCESS MODES   STORAGECLASS   
 AGE
example-pvc-block   Pending  
cloudstack-custom   31s
7.  Apply the pod block yaml

apiVersion: v1
kind: Pod
metadata:
  name: example-pod-block
spec:
  containers:
- name: example
  image: ubuntu
  volumeDevices:
- devicePath: "/dev/example-block"
  name: example-volume
  stdin: true
  stdinOnce: true
  tty: true
  volumes:
- name: example-volume
  persistentVolumeClaim:
claimName: example-pvc-block


kubectl apply -f pod-block.yaml


➜  k8s git:(master) ✗ k get pods -A
NAMESPACE  NAME READY   
STATUSRESTARTS  AGE
defaultexample-pod-block1/1 
Running   0 107s

Events:
  TypeReason  Age   From Message
  --     ---
  Normal  Scheduled   9sdefault-schedulerSuccessfully 
assigned default/example-pod-block to ty-node-18de52c4185
  Normal  SuccessfulAttachVolume  6sattachdetach-controller  
AttachVolume.Attach succeeded for volume 
"pvc-02999f04-dd0a-407c-8805-125c7c56d51b"
 

Re: CKS Storage Provisioner Info

[Kiran Chavala]

Hi Bharath

Note the CKS provisioner works on KVM based cloudstack environment

Regards
Kiran

From: Kiran Chavala 
Date: Monday, 26 February 2024 at 5:45 PM
To: users@cloudstack.apache.org 
Subject: Re: CKS Storage Provisioner Info
Hi Bharat Bhusan

Please follow these steps


1. Deploy a Kubernetes cluster on cluster


NAME STATUS   ROLES   AGE VERSION
ty-control-18de52c04f7   Readycontrol-plane   5m11s   v1.28.4
ty-node-18de52c4185  Ready  4m55s   v1.28.4

kubectl get secrets -A
NAMESPACE  NAME  TYPE   
 DATA   AGE
kube-systemcloudstack-secret Opaque 
 1  10m



2. Check the deployment, it should  be in pending

~ kubectl get deployments -A
NAMESPACE  NAMEREADY   UP-TO-DATE   
AVAILABLE   AGE
kube-systemcloudstack-csi-controller   0/1 10   
46s


3. Edit the deployment and remove the nodeSelector part

~kubectl edit deployment/cloudstack-csi-controller -n kube-system


  nodeSelector:
kubernetes.io/os: linux
node-role.kubernetes.io/master: ""

4. Check the deployment again  and it should be running state

~kubectl get deployments -A
NAMESPACE  NAMEREADY   UP-TO-DATE   
AVAILABLE   AGE
kube-systemcloudstack-csi-controller   1/1 11   
2m39s

5. Replace the disk offering in the storage class yaml

Provide the custom disk offering UUID (service offerings > disk offering > 
custom disk offering

4c518474-5d7b-4285-a07c-c57e214abb3b


vi 0-storageclass.yaml

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: cloudstack-custom
provisioner: csi.cloudstack.apache.org
reclaimPolicy: Delete
volumeBindingMode: WaitForFirstConsumer
allowVolumeExpansion: false
parameters:
  csi.cloudstack.apache.org/disk-offering-id: 
4c518474-5d7b-4285-a07c-c57e214abb3b


kubectl apply -f 0-storageclass.yaml

k8s git:(master) ✗ kubectl get sc
NAMEPROVISIONER RECLAIMPOLICY   
VOLUMEBINDINGMODE  ALLOWVOLUMEEXPANSION   AGE
cloudstack-custom   csi.cloudstack.apache.org   Delete  
WaitForFirstConsumer   false  72s



6. Apply the pvc yaml

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: example-pvc-block
spec:
  storageClassName: cloudstack-custom
  volumeMode: Block
  accessModes:
- ReadWriteOnce
  resources:
requests:
  storage: 1Gi


kubectl apply -f pvc-block.yaml

k8s git:(master) ✗ kubectl get pvc
NAMESTATUSVOLUME   CAPACITY   ACCESS MODES   STORAGECLASS   
 AGE
example-pvc-block   Pending  
cloudstack-custom   31s
7.  Apply the pod block yaml

apiVersion: v1
kind: Pod
metadata:
  name: example-pod-block
spec:
  containers:
- name: example
  image: ubuntu
  volumeDevices:
- devicePath: "/dev/example-block"
  name: example-volume
  stdin: true
  stdinOnce: true
  tty: true
  volumes:
- name: example-volume
  persistentVolumeClaim:
claimName: example-pvc-block


kubectl apply -f pod-block.yaml


➜  k8s git:(master) ✗ k get pods -A
NAMESPACE  NAME READY   
STATUSRESTARTS  AGE
defaultexample-pod-block1/1 
Running   0 107s

Events:
  TypeReason  Age   From Message
  --     ---
  Normal  Scheduled   9sdefault-schedulerSuccessfully 
assigned default/example-pod-block to ty-node-18de52c4185
  Normal  SuccessfulAttachVolume  6sattachdetach-controller  
AttachVolume.Attach succeeded for volume 
"pvc-02999f04-dd0a-407c-8805-125c7c56d51b"
  Normal  SuccessfulMountVolume   4skubelet  
MapVolume.MapPodDevice succeeded for volume 
"pvc-02999f04-dd0a-407c-8805-125c7c56d51b" globalMapPath 
"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/pvc-02999f04-dd0a-407c-8805-125c7c56d51b/dev"
  Normal  SuccessfulMountVolume   4skubelet  
MapVolume.MapPodDevice succeeded for volume 
"pvc-02999f04-dd0a-407c-8805-125c7c56d51b" volumeMapPath 
"/var/lib/kubelet/pods/076bd828-7130-4f72-a0ee-29f93043bbb1/volumeDevices/kubernetes.io~csi"
  Normal  Pulling 3skubelet  Pulling image 
"ubuntu"

Regards
Kiran





From: Jayanth Reddy 
Date: Monday, 26 February 2024 at 4:35 PM
To: users@cloudstack.apache.org 
Subject: Re: CKS Storage Provisioner Info
Hello Bharat,
If that is the case, please update your "api-url" variable for the cloud-config.

FWIW, please also visit "endpoint.url" in 

Re: CKS Storage Provisioner Info

[Kiran Chavala]

Hi Bharat Bhusan

Please follow these steps


1. Deploy a Kubernetes cluster on cluster


NAME STATUS   ROLES   AGE VERSION
ty-control-18de52c04f7   Readycontrol-plane   5m11s   v1.28.4
ty-node-18de52c4185  Ready  4m55s   v1.28.4

kubectl get secrets -A
NAMESPACE  NAME  TYPE   
 DATA   AGE
kube-systemcloudstack-secret Opaque 
 1  10m



2. Check the deployment, it should  be in pending

~ kubectl get deployments -A
NAMESPACE  NAMEREADY   UP-TO-DATE   
AVAILABLE   AGE
kube-systemcloudstack-csi-controller   0/1 10   
46s


3. Edit the deployment and remove the nodeSelector part

~kubectl edit deployment/cloudstack-csi-controller -n kube-system


  nodeSelector:
kubernetes.io/os: linux
node-role.kubernetes.io/master: ""

4. Check the deployment again  and it should be running state

~kubectl get deployments -A
NAMESPACE  NAMEREADY   UP-TO-DATE   
AVAILABLE   AGE
kube-systemcloudstack-csi-controller   1/1 11   
2m39s


5. Replace the disk offering in the storage class yaml

Provide the custom disk offering UUID (service offerings > disk offering > 
custom disk offering

4c518474-5d7b-4285-a07c-c57e214abb3b


vi 0-storageclass.yaml

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: cloudstack-custom
provisioner: csi.cloudstack.apache.org
reclaimPolicy: Delete
volumeBindingMode: WaitForFirstConsumer
allowVolumeExpansion: false
parameters:
  csi.cloudstack.apache.org/disk-offering-id: 
4c518474-5d7b-4285-a07c-c57e214abb3b


kubectl apply -f 0-storageclass.yaml

k8s git:(master) ✗ kubectl get sc
NAMEPROVISIONER RECLAIMPOLICY   
VOLUMEBINDINGMODE  ALLOWVOLUMEEXPANSION   AGE
cloudstack-custom   csi.cloudstack.apache.org   Delete  
WaitForFirstConsumer   false  72s



6. Apply the pvc yaml

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: example-pvc-block
spec:
  storageClassName: cloudstack-custom
  volumeMode: Block
  accessModes:
- ReadWriteOnce
  resources:
requests:
  storage: 1Gi


kubectl apply -f pvc-block.yaml

k8s git:(master) ✗ kubectl get pvc
NAMESTATUSVOLUME   CAPACITY   ACCESS MODES   STORAGECLASS   
 AGE
example-pvc-block   Pending  
cloudstack-custom   31s

7.  Apply the pod block yaml

apiVersion: v1
kind: Pod
metadata:
  name: example-pod-block
spec:
  containers:
- name: example
  image: ubuntu
  volumeDevices:
- devicePath: "/dev/example-block"
  name: example-volume
  stdin: true
  stdinOnce: true
  tty: true
  volumes:
- name: example-volume
  persistentVolumeClaim:
claimName: example-pvc-block


kubectl apply -f pod-block.yaml


➜  k8s git:(master) ✗ k get pods -A
NAMESPACE  NAME READY   
STATUSRESTARTS  AGE
defaultexample-pod-block1/1 
Running   0 107s

Events:
  TypeReason  Age   From Message
  --     ---
  Normal  Scheduled   9sdefault-schedulerSuccessfully 
assigned default/example-pod-block to ty-node-18de52c4185
  Normal  SuccessfulAttachVolume  6sattachdetach-controller  
AttachVolume.Attach succeeded for volume 
"pvc-02999f04-dd0a-407c-8805-125c7c56d51b"
  Normal  SuccessfulMountVolume   4skubelet  
MapVolume.MapPodDevice succeeded for volume 
"pvc-02999f04-dd0a-407c-8805-125c7c56d51b" globalMapPath 
"/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/pvc-02999f04-dd0a-407c-8805-125c7c56d51b/dev"
  Normal  SuccessfulMountVolume   4skubelet  
MapVolume.MapPodDevice succeeded for volume 
"pvc-02999f04-dd0a-407c-8805-125c7c56d51b" volumeMapPath 
"/var/lib/kubelet/pods/076bd828-7130-4f72-a0ee-29f93043bbb1/volumeDevices/kubernetes.io~csi"
  Normal  Pulling 3skubelet  Pulling image 
"ubuntu"

Regards
Kiran


From: Jayanth Reddy 
Date: Monday, 26 February 2024 at 4:35 PM
To: users@cloudstack.apache.org 
Subject: Re: CKS Storage Provisioner Info
Hello Bharat,
If that is the case, please update your "api-url" variable for the cloud-config.

FWIW, please also visit "endpoint.url" in global configuration to include the 
HTTPS endpoint.

Thanks,
Jayanth

Sent from Outlook for Android<https://aka.ms/AAb9ysg>

 



From: Bharat Bhushan Saini 
Sent: Monday, February 26, 2024 4

Re: CKS Storage Provisioner Info

[Jayanth Reddy]

Hello Bharat,
If that is the case, please update your "api-url" variable for the cloud-config.

FWIW, please also visit "endpoint.url" in global configuration to include the 
HTTPS endpoint.

Thanks,
Jayanth

Sent from Outlook for Android<https://aka.ms/AAb9ysg>


From: Bharat Bhushan Saini 
Sent: Monday, February 26, 2024 4:29:22 pm
To: users@cloudstack.apache.org 
Subject: Re: CKS Storage Provisioner Info

Hi Jayanth,

For to secure communication, I already enabled the https over the management 
server and turned off the http.
The API URL only listen over http?

Thanks and Regards,
Bharat Saini

[signature_3317674547]

From: Jayanth Reddy 
Date: Monday, 26 February 2024 at 4:19 PM
To: users@cloudstack.apache.org 
Subject: Re: CKS Storage Provisioner Info
EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.


Are you able to access the CloudStack WebUI in the URL
http://10.1.10.2:8080/client ? As long as k8s nodes have connectivity on
the path /client/api on your management, this should work fine. Perhaps a
host-level firewall in your management server?

Thanks

On Mon, Feb 26, 2024 at 4:08 PM Bharat Bhushan Saini
 wrote:

> Hi Vivek,
>
>
>
> Please check the findings
>
>
>
> ping 10.1.x.2
>
> PING 10.1.x.2 (10.1.x.2): 56 data bytes
>
> 64 bytes from 10.1.x.2: icmp_seq=0 ttl=64 time=0.616 ms
>
> 64 bytes from 10.1.x.2: icmp_seq=1 ttl=64 time=0.716 ms
>
> ^C--- 10.1.10.2 ping statistics ---
>
> 2 packets transmitted, 2 packets received, 0% packet loss
>
> round-trip min/avg/max/stddev = 0.616/0.666/0.716/0.050 ms
>
>
>
> ping cloudstack.internal.com
>
> PING cloudstack.internal.com (10.1.x.2): 56 data bytes
>
> 64 bytes from 10.1.x.2: icmp_seq=0 ttl=64 time=0.555 ms
>
> 64 bytes from 10.1.x.2: icmp_seq=1 ttl=64 time=0.620 ms
>
> 64 bytes from 10.1.x.2: icmp_seq=2 ttl=64 time=0.664 ms
>
> ^C--- cloudstack.internal.kloudspot.com ping statistics ---
>
> 3 packets transmitted, 3 packets received, 0% packet loss
>
> round-trip min/avg/max/stddev = 0.555/0.613/0.664/0.045 ms
>
>
>
> telnet 10.1.x.2 8080
>
> Trying 10.1.x.2...
>
> telnet: Unable to connect to remote host: Connection refused
>
>
>
>
>
> I am able to ping the management IP and URL but not able to get access
> from the port as it is not open in the cluster.
> NOTE: I use the management IP in the API URL.
>
>
>
> Thanks and Regards,
>
> Bharat Saini
>
>
>
> [image: signature_4099962424]
>
>
>
> *From: *Vivek Kumar 
> *Date: *Monday, 26 February 2024 at 3:49 PM
> *To: *users@cloudstack.apache.org 
> *Subject: *Re: CKS Storage Provisioner Info
>
> EXTERNAL EMAIL: Please verify the sender email address before taking any
> action, replying, clicking any link or opening any attachment.
>
>
> Hello Bharat,
>
> Is the cloudstack URL is reachable from your cluster, can you manually
> check i.e ping, telnet on that port ?
>
>
>
>
> > On 26-Feb-2024, at 3:43 PM, Bharat Bhushan Saini
>  wrote:
> >
> > Hi Wei/Jayanth,
> >
> > Thanks for sharing the details. I am able to fetch out the api and keys
> and deployed the driver as suggested by @vivek and GH page.
> >
> > Now I encountered with one more issue that the cloudstack csi node goes
> in CrashLoopBackOff Error. I am trying to get some more info regarding this
> which is as below
> >
> >
> {"level":"error","ts":1708932622.5365772,"caller":"zap/options.go:212","msg":"finished
> unary call with code
> Internal","grpc.start_time":"2024-02-26T07:30:22Z","grpc.request.deadline":"2024-02-26T07:32:22Z","system":"grpc","span.kind":"server","grpc.service":"csi.v1.Node","grpc.method":"NodeGetInfo","error":"rpc
> error: code = Internal desc = Get \"
> http://10.1.10.2:8080/client/api?apiKey=k83H56KFdhFqpv7cXPU11nkwxPt8f2rXnm1WWVIRdeErqZr72Pzp7ySmricPWs7FQQuMmClznDhMz7uqnRD2wA=listVirtualMachines=cf4940eb-52a4-4205-b056-1575926cb488=json=t4jdPVL7jqhGt5pWC0kjx%2Bxzr3o%3D\
> <http://10.1.10.2:8080/client/api?apiKey=k83H56KFdhFqpv7cXPU11nkwxPt8f2rXnm1WWVIRdeErqZr72Pzp7ySmricPWs7FQQuMmClznDhMz7uqnRD2wA=listVirtualMachines=cf4940eb-52a4-4205-b056-1575926cb488=json=t4jdPVL7jqhGt5pWC0kjx%2Bxzr3o%3D%5C>":
> <
> http://10.1.10.2:8080/client/api?apiKey=k83H56KFdhFqpv7cXPU11nkwxPt8f2rXnm1WWVIRdeErqZr72Pzp7ySmricPWs7FQQuMmClznDhMz7uqnRD2wA=listVirtualMachines=cf4940eb-52a4-4205-b056-1575926cb488=json=t4jdPVL7jqhGt5pWC0kjx%2Bxzr3o%3D\%

Re: CKS Storage Provisioner Info

[Bharat Bhushan Saini]

Hi Jayanth,

For to secure communication, I already enabled the https over the management 
server and turned off the http.
The API URL only listen over http?

Thanks and Regards,
Bharat Saini

[signature_3317674547]

From: Jayanth Reddy 
Date: Monday, 26 February 2024 at 4:19 PM
To: users@cloudstack.apache.org 
Subject: Re: CKS Storage Provisioner Info
EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.


Are you able to access the CloudStack WebUI in the URL
http://10.1.10.2:8080/client ? As long as k8s nodes have connectivity on
the path /client/api on your management, this should work fine. Perhaps a
host-level firewall in your management server?

Thanks

On Mon, Feb 26, 2024 at 4:08 PM Bharat Bhushan Saini
 wrote:

> Hi Vivek,
>
>
>
> Please check the findings
>
>
>
> ping 10.1.x.2
>
> PING 10.1.x.2 (10.1.x.2): 56 data bytes
>
> 64 bytes from 10.1.x.2: icmp_seq=0 ttl=64 time=0.616 ms
>
> 64 bytes from 10.1.x.2: icmp_seq=1 ttl=64 time=0.716 ms
>
> ^C--- 10.1.10.2 ping statistics ---
>
> 2 packets transmitted, 2 packets received, 0% packet loss
>
> round-trip min/avg/max/stddev = 0.616/0.666/0.716/0.050 ms
>
>
>
> ping cloudstack.internal.com
>
> PING cloudstack.internal.com (10.1.x.2): 56 data bytes
>
> 64 bytes from 10.1.x.2: icmp_seq=0 ttl=64 time=0.555 ms
>
> 64 bytes from 10.1.x.2: icmp_seq=1 ttl=64 time=0.620 ms
>
> 64 bytes from 10.1.x.2: icmp_seq=2 ttl=64 time=0.664 ms
>
> ^C--- cloudstack.internal.kloudspot.com ping statistics ---
>
> 3 packets transmitted, 3 packets received, 0% packet loss
>
> round-trip min/avg/max/stddev = 0.555/0.613/0.664/0.045 ms
>
>
>
> telnet 10.1.x.2 8080
>
> Trying 10.1.x.2...
>
> telnet: Unable to connect to remote host: Connection refused
>
>
>
>
>
> I am able to ping the management IP and URL but not able to get access
> from the port as it is not open in the cluster.
> NOTE: I use the management IP in the API URL.
>
>
>
> Thanks and Regards,
>
> Bharat Saini
>
>
>
> [image: signature_4099962424]
>
>
>
> *From: *Vivek Kumar 
> *Date: *Monday, 26 February 2024 at 3:49 PM
> *To: *users@cloudstack.apache.org 
> *Subject: *Re: CKS Storage Provisioner Info
>
> EXTERNAL EMAIL: Please verify the sender email address before taking any
> action, replying, clicking any link or opening any attachment.
>
>
> Hello Bharat,
>
> Is the cloudstack URL is reachable from your cluster, can you manually
> check i.e ping, telnet on that port ?
>
>
>
>
> > On 26-Feb-2024, at 3:43 PM, Bharat Bhushan Saini
>  wrote:
> >
> > Hi Wei/Jayanth,
> >
> > Thanks for sharing the details. I am able to fetch out the api and keys
> and deployed the driver as suggested by @vivek and GH page.
> >
> > Now I encountered with one more issue that the cloudstack csi node goes
> in CrashLoopBackOff Error. I am trying to get some more info regarding this
> which is as below
> >
> >
> {"level":"error","ts":1708932622.5365772,"caller":"zap/options.go:212","msg":"finished
> unary call with code
> Internal","grpc.start_time":"2024-02-26T07:30:22Z","grpc.request.deadline":"2024-02-26T07:32:22Z","system":"grpc","span.kind":"server","grpc.service":"csi.v1.Node","grpc.method":"NodeGetInfo","error":"rpc
> error: code = Internal desc = Get \"
> http://10.1.10.2:8080/client/api?apiKey=k83H56KFdhFqpv7cXPU11nkwxPt8f2rXnm1WWVIRdeErqZr72Pzp7ySmricPWs7FQQuMmClznDhMz7uqnRD2wA=listVirtualMachines=cf4940eb-52a4-4205-b056-1575926cb488=json=t4jdPVL7jqhGt5pWC0kjx%2Bxzr3o%3D\
> <http://10.1.10.2:8080/client/api?apiKey=k83H56KFdhFqpv7cXPU11nkwxPt8f2rXnm1WWVIRdeErqZr72Pzp7ySmricPWs7FQQuMmClznDhMz7uqnRD2wA=listVirtualMachines=cf4940eb-52a4-4205-b056-1575926cb488=json=t4jdPVL7jqhGt5pWC0kjx%2Bxzr3o%3D%5C>":
> <
> http://10.1.10.2:8080/client/api?apiKey=k83H56KFdhFqpv7cXPU11nkwxPt8f2rXnm1WWVIRdeErqZr72Pzp7ySmricPWs7FQQuMmClznDhMz7uqnRD2wA=listVirtualMachines=cf4940eb-52a4-4205-b056-1575926cb488=json=t4jdPVL7jqhGt5pWC0kjx%2Bxzr3o%3D\%22:
> <http://10.1.10.2:8080/client/api?apiKey=k83H56KFdhFqpv7cXPU11nkwxPt8f2rXnm1WWVIRdeErqZr72Pzp7ySmricPWs7FQQuMmClznDhMz7uqnRD2wA=listVirtualMachines=cf4940eb-52a4-4205-b056-1575926cb488=json=t4jdPVL7jqhGt5pWC0kjx%2Bxzr3o%3D%5C%22:>>
> dial tcp 10.1.10.2:8080: connect: connection
> refused","grpc.code":"Internal","grpc.time_ms":1.138,"stacktrace":"
> github.com/grpc-ecosystem/go-grpc-middle

Re: CKS Storage Provisioner Info

[Jayanth Reddy]

Are you able to access the CloudStack WebUI in the URL
http://10.1.10.2:8080/client ? As long as k8s nodes have connectivity on
the path /client/api on your management, this should work fine. Perhaps a
host-level firewall in your management server?

Thanks

On Mon, Feb 26, 2024 at 4:08 PM Bharat Bhushan Saini
 wrote:

> Hi Vivek,
>
>
>
> Please check the findings
>
>
>
> ping 10.1.x.2
>
> PING 10.1.x.2 (10.1.x.2): 56 data bytes
>
> 64 bytes from 10.1.x.2: icmp_seq=0 ttl=64 time=0.616 ms
>
> 64 bytes from 10.1.x.2: icmp_seq=1 ttl=64 time=0.716 ms
>
> ^C--- 10.1.10.2 ping statistics ---
>
> 2 packets transmitted, 2 packets received, 0% packet loss
>
> round-trip min/avg/max/stddev = 0.616/0.666/0.716/0.050 ms
>
>
>
> ping cloudstack.internal.com
>
> PING cloudstack.internal.com (10.1.x.2): 56 data bytes
>
> 64 bytes from 10.1.x.2: icmp_seq=0 ttl=64 time=0.555 ms
>
> 64 bytes from 10.1.x.2: icmp_seq=1 ttl=64 time=0.620 ms
>
> 64 bytes from 10.1.x.2: icmp_seq=2 ttl=64 time=0.664 ms
>
> ^C--- cloudstack.internal.kloudspot.com ping statistics ---
>
> 3 packets transmitted, 3 packets received, 0% packet loss
>
> round-trip min/avg/max/stddev = 0.555/0.613/0.664/0.045 ms
>
>
>
> telnet 10.1.x.2 8080
>
> Trying 10.1.x.2...
>
> telnet: Unable to connect to remote host: Connection refused
>
>
>
>
>
> I am able to ping the management IP and URL but not able to get access
> from the port as it is not open in the cluster.
> NOTE: I use the management IP in the API URL.
>
>
>
> Thanks and Regards,
>
> Bharat Saini
>
>
>
> [image: signature_4099962424]
>
>
>
> *From: *Vivek Kumar 
> *Date: *Monday, 26 February 2024 at 3:49 PM
> *To: *users@cloudstack.apache.org 
> *Subject: *Re: CKS Storage Provisioner Info
>
> EXTERNAL EMAIL: Please verify the sender email address before taking any
> action, replying, clicking any link or opening any attachment.
>
>
> Hello Bharat,
>
> Is the cloudstack URL is reachable from your cluster, can you manually
> check i.e ping, telnet on that port ?
>
>
>
>
> > On 26-Feb-2024, at 3:43 PM, Bharat Bhushan Saini
>  wrote:
> >
> > Hi Wei/Jayanth,
> >
> > Thanks for sharing the details. I am able to fetch out the api and keys
> and deployed the driver as suggested by @vivek and GH page.
> >
> > Now I encountered with one more issue that the cloudstack csi node goes
> in CrashLoopBackOff Error. I am trying to get some more info regarding this
> which is as below
> >
> >
> {"level":"error","ts":1708932622.5365772,"caller":"zap/options.go:212","msg":"finished
> unary call with code
> Internal","grpc.start_time":"2024-02-26T07:30:22Z","grpc.request.deadline":"2024-02-26T07:32:22Z","system":"grpc","span.kind":"server","grpc.service":"csi.v1.Node","grpc.method":"NodeGetInfo","error":"rpc
> error: code = Internal desc = Get \"
> http://10.1.10.2:8080/client/api?apiKey=k83H56KFdhFqpv7cXPU11nkwxPt8f2rXnm1WWVIRdeErqZr72Pzp7ySmricPWs7FQQuMmClznDhMz7uqnRD2wA=listVirtualMachines=cf4940eb-52a4-4205-b056-1575926cb488=json=t4jdPVL7jqhGt5pWC0kjx%2Bxzr3o%3D\
> <http://10.1.10.2:8080/client/api?apiKey=k83H56KFdhFqpv7cXPU11nkwxPt8f2rXnm1WWVIRdeErqZr72Pzp7ySmricPWs7FQQuMmClznDhMz7uqnRD2wA=listVirtualMachines=cf4940eb-52a4-4205-b056-1575926cb488=json=t4jdPVL7jqhGt5pWC0kjx%2Bxzr3o%3D%5C>":
> <
> http://10.1.10.2:8080/client/api?apiKey=k83H56KFdhFqpv7cXPU11nkwxPt8f2rXnm1WWVIRdeErqZr72Pzp7ySmricPWs7FQQuMmClznDhMz7uqnRD2wA=listVirtualMachines=cf4940eb-52a4-4205-b056-1575926cb488=json=t4jdPVL7jqhGt5pWC0kjx%2Bxzr3o%3D\%22:
> <http://10.1.10.2:8080/client/api?apiKey=k83H56KFdhFqpv7cXPU11nkwxPt8f2rXnm1WWVIRdeErqZr72Pzp7ySmricPWs7FQQuMmClznDhMz7uqnRD2wA=listVirtualMachines=cf4940eb-52a4-4205-b056-1575926cb488=json=t4jdPVL7jqhGt5pWC0kjx%2Bxzr3o%3D%5C%22:>>
> dial tcp 10.1.10.2:8080: connect: connection
> refused","grpc.code":"Internal","grpc.time_ms":1.138,"stacktrace":"
> github.com/grpc-ecosystem/go-grpc-middleware/logging/zap.DefaultMessageProducer\n\t/home/runner/go/pkg/mod/github.com/grpc-ecosystem/go-grpc-middleware@v1.4.0/logging/zap/options.go:212\ngithub.com/grpc-ecosystem
> <http://github.com/grpc-ecosystem/go-grpc-middleware/logging/zap.DefaultMessageProducer%5Cn%5Ct/home/runner/go/pkg/mod/github.com/grpc-ecosystem/go-grpc-middleware@v1.4.0/logging/zap/options.go:212%5Cngithub.com/grpc-ecosystem>
> <
> http://github.com/grpc-ecosystem/go-grpc-middlew

Re: CKS Storage Provisioner Info

[Bharat Bhushan Saini]

Hi Vivek,

Please check the findings


ping 10.1.x.2

PING 10.1.x.2 (10.1.x.2): 56 data bytes

64 bytes from 10.1.x.2: icmp_seq=0 ttl=64 time=0.616 ms

64 bytes from 10.1.x.2: icmp_seq=1 ttl=64 time=0.716 ms

^C--- 10.1.10.2 ping statistics ---

2 packets transmitted, 2 packets received, 0% packet loss

round-trip min/avg/max/stddev = 0.616/0.666/0.716/0.050 ms


ping cloudstack.internal.com

PING cloudstack.internal.com (10.1.x.2): 56 data bytes

64 bytes from 10.1.x.2: icmp_seq=0 ttl=64 time=0.555 ms

64 bytes from 10.1.x.2: icmp_seq=1 ttl=64 time=0.620 ms

64 bytes from 10.1.x.2: icmp_seq=2 ttl=64 time=0.664 ms

^C--- cloudstack.internal.kloudspot.com ping statistics ---

3 packets transmitted, 3 packets received, 0% packet loss

round-trip min/avg/max/stddev = 0.555/0.613/0.664/0.045 ms


telnet 10.1.x.2 8080

Trying 10.1.x.2...

telnet: Unable to connect to remote host: Connection refused


I am able to ping the management IP and URL but not able to get access from the 
port as it is not open in the cluster.
NOTE: I use the management IP in the API URL.

Thanks and Regards,
Bharat Saini

[signature_4099962424]

From: Vivek Kumar 
Date: Monday, 26 February 2024 at 3:49 PM
To: users@cloudstack.apache.org 
Subject: Re: CKS Storage Provisioner Info
EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.


Hello Bharat,

Is the cloudstack URL is reachable from your cluster, can you manually check 
i.e ping, telnet on that port ?




> On 26-Feb-2024, at 3:43 PM, Bharat Bhushan Saini 
>  wrote:
>
> Hi Wei/Jayanth,
>
> Thanks for sharing the details. I am able to fetch out the api and keys and 
> deployed the driver as suggested by @vivek and GH page.
>
> Now I encountered with one more issue that the cloudstack csi node goes in 
> CrashLoopBackOff Error. I am trying to get some more info regarding this 
> which is as below
>
> {"level":"error","ts":1708932622.5365772,"caller":"zap/options.go:212","msg":"finished
>  unary call with code 
> Internal","grpc.start_time":"2024-02-26T07:30:22Z","grpc.request.deadline":"2024-02-26T07:32:22Z","system":"grpc","span.kind":"server","grpc.service":"csi.v1.Node","grpc.method":"NodeGetInfo","error":"rpc
>  error: code = Internal desc = Get 
> \"http://10.1.10.2:8080/client/api?apiKey=k83H56KFdhFqpv7cXPU11nkwxPt8f2rXnm1WWVIRdeErqZr72Pzp7ySmricPWs7FQQuMmClznDhMz7uqnRD2wA=listVirtualMachines=cf4940eb-52a4-4205-b056-1575926cb488=json=t4jdPVL7jqhGt5pWC0kjx%2Bxzr3o%3D\":
>  
> <http://10.1.10.2:8080/client/api?apiKey=k83H56KFdhFqpv7cXPU11nkwxPt8f2rXnm1WWVIRdeErqZr72Pzp7ySmricPWs7FQQuMmClznDhMz7uqnRD2wA=listVirtualMachines=cf4940eb-52a4-4205-b056-1575926cb488=json=t4jdPVL7jqhGt5pWC0kjx%2Bxzr3o%3D\%22:>
>  dial tcp 10.1.10.2:8080: connect: connection 
> refused","grpc.code":"Internal","grpc.time_ms":1.138,"stacktrace":"github.com/grpc-ecosystem/go-grpc-middleware/logging/zap.DefaultMessageProducer\n\t/home/runner/go/pkg/mod/github.com/grpc-ecosystem/go-grpc-middleware@v1.4.0/logging/zap/options.go:212\ngithub.com/grpc-ecosystem
>  
> <http://github.com/grpc-ecosystem/go-grpc-middleware/logging/zap.DefaultMessageProducer/n/t/home/runner/go/pkg/mod/github.com/grpc-ecosystem/go-grpc-middleware@v1.4.0/logging/zap/options.go:212/ngithub.com/grpc-ecosystem>/go-grpc-middleware/logging/zap.UnaryServerInterceptor.func1\n\t/home/runner/go/pkg/mod/github.com/grpc-ecosystem/go-grpc-middleware@v1.4.0/logging/zap/server_interceptors.go:39\ngoogle.golang.org/grpc.chainUnaryInterceptors.func1\n\t/home/runner/go/pkg/mod/google.golang.org/grpc@v1.60.1/server.go:1183\ngithub.com/container-storage-interface/spec/lib/go/csi
>  
> <http://ngoogle.golang.org/grpc.chainUnaryInterceptors.func1/n/t/home/runner/go/pkg/mod/google.golang.org/grpc@v1.60.1/server.go:1183/ngithub.com/container-storage-interface/spec/lib/go/csi>._Node_NodeGetInfo_Handler\n\t/home/runner/go/pkg/mod/github.com/container-storage-interface/spec@v1.9.0/lib/go/csi/csi.pb.go:7351\ngoogle.golang.org/grpc
>  
> <http://github.com/container-storage-interface/spec@v1.9.0/lib/go/csi/csi.pb.go:7351/ngoogle.golang.org/grpc>.(*Server<http://github.com/container-storage-interface/spec@v1.9.0/lib/go/csi/csi.pb.go:7351/ngoogle.golang.org/grpc%3e.(*Server>).processUnaryRPC\n\t/home/runner/go/pkg/mod/google.golang.org/grpc@v1.60.1/server.go:1372\ngoogle.golang.org/grpc
>  
> <http://google.golang.org/grpc@v1.60.1/server.go:1372/ngoogle.golang.org/grpc>.(*Server<http://google.golang.org/grpc@v1.60.1/server.go:1372/ngoogle.golang.org/grpc%3e.(*Server>).handleStream\n\t/home/runner

Re: CKS Storage Provisioner Info

[Vivek Kumar]

7m
> kube-systemcoredns-5dd5756b68-mbpwt   
>  1/1 Running0   4h17m
> kube-systemetcd-kspot-app-control-18de3ee6b6f 
>  1/1 Running0   4h17m
> kube-systemkube-apiserver-kspot-app-control-18de3ee6b6f   
>  1/1 Running0   4h17m
> kube-systemkube-controller-manager-kspot-app-control-18de3ee6b6f  
>  1/1 Running0   4h17m
> kube-systemkube-proxy-56r4l   
>  1/1 Running0   4h17m
> kube-systemkube-proxy-mf6cc   
>  1/1 Running0   4h17m
> kube-systemkube-scheduler-kspot-app-control-18de3ee6b6f   
>  1/1 Running0   4h17m
> kube-systemweave-net-59t9z
>  2/2 Running1 (4h17m ago)   4h17m
> kube-systemweave-net-7xvpp
>  2/2 Running0   4h17m
> kubernetes-dashboard   dashboard-metrics-scraper-5657497c4c-g89lq 
>  1/1 Running0   4h17m
> kubernetes-dashboard   kubernetes-dashboard-5b749d9495-fqplb  
>  1/1 Running0   4h17m
>  
> kubectl get csinode
> NAMEDRIVERS   AGE
> kspot-app-control-18de3ee6b6f   0 4h23m
> kspot-app-node-18de3eeb7b7  0 4h23m
>  
> kubectl describe csinode
> Name:   kspot-app-control-18de3ee6b6f
> Labels: 
> Annotations:storage.alpha.kubernetes.io/migrated-plugins: 
> <http://storage.alpha.kubernetes.io/migrated-plugins:>
>   
> kubernetes.io/aws-ebs,kubernetes.io/azure-disk,kubernetes.io/azure-file,kubernetes.io/cinder,kubernetes.io/gce-pd,kubernetes.io/vsphere-vo
>  
> <http://kubernetes.io/aws-ebs,kubernetes.io/azure-disk,kubernetes.io/azure-file,kubernetes.io/cinder,kubernetes.io/gce-pd,kubernetes.io/vsphere-vo>...
> CreationTimestamp:  Mon, 26 Feb 2024 05:42:57 +
> Spec:
> Events:  
> Name:   kspot-app-node-18de3eeb7b7
> Labels: 
> Annotations:storage.alpha.kubernetes.io/migrated-plugins: 
> <http://storage.alpha.kubernetes.io/migrated-plugins:>
>   
> kubernetes.io/aws-ebs,kubernetes.io/azure-disk,kubernetes.io/azure-file,kubernetes.io/cinder,kubernetes.io/gce-pd,kubernetes.io/vsphere-vo
>  
> <http://kubernetes.io/aws-ebs,kubernetes.io/azure-disk,kubernetes.io/azure-file,kubernetes.io/cinder,kubernetes.io/gce-pd,kubernetes.io/vsphere-vo>...
> CreationTimestamp:  Mon, 26 Feb 2024 05:43:12 +
> Spec:
> Events:  
>  
>  
> Thanks and Regards,
> Bharat Saini
>  
> 
>  
> From: Wei ZHOU mailto:ustcweiz...@gmail.com>>
> Date: Monday, 26 February 2024 at 1:52 AM
> To: users@cloudstack.apache.org <mailto:users@cloudstack.apache.org> 
> mailto:users@cloudstack.apache.org>>
> Subject: Re: CKS Storage Provisioner Info
> 
> EXTERNAL EMAIL: Please verify the sender email address before taking any 
> action, replying, clicking any link or opening any attachment.
> 
> 
> +1
> 
> Or  use the api key of "admin" user.
> 
> -Wei
> 
> On Sun, Feb 25, 2024 at 7:57 PM Jayanth Reddy  <mailto:jayanthreddy5...@gmail.com>>
> wrote:
> 
> > Hello Bharat,
> > With your login as "admin" user, you should be able to generate keys for
> > any user. Please do the below
> >
> > 1. Go to "Accounts"
> > 2. Select the account named "admin"
> > 3. Scroll down and click "users"
> > 4. Select the "admin-kubeadmin" user
> > 5. Then select the button for generation of keys.
> >
> > Please let me know if that helps.
> >
> > Thanks,
> > Jayanth
> >
> > Sent from Outlook for Android<https://aka.ms/AAb9ysg>
> >
> >
> >
> --- Disclaimer: -- 
> This message and its contents are intended solely for the designated 
> addressee and are proprietary to Kloudspot. The information in this email is 
> meant exclusively for Kloudspot business use. Any use by individuals other 
> than the addressee constitutes misuse and an infringement of Kloudspot's 
> proprietary rights. If you are not the intended recipient, please return this 
> email to the sender. Kloudspot cannot guarantee the security or error-free 
> transmission of e-mail

Re: CKS Storage Provisioner Info

[Bharat Bhushan Saini]

 
1/1 Running0   4h17m
kubernetes-dashboard   kubernetes-dashboard-5b749d9495-fqplb   
1/1 Running0   4h17m

kubectl get csinode
NAMEDRIVERS   AGE
kspot-app-control-18de3ee6b6f   0 4h23m
kspot-app-node-18de3eeb7b7  0 4h23m

kubectl describe csinode
Name:   kspot-app-control-18de3ee6b6f
Labels: 
Annotations:storage.alpha.kubernetes.io/migrated-plugins:
  
kubernetes.io/aws-ebs,kubernetes.io/azure-disk,kubernetes.io/azure-file,kubernetes.io/cinder,kubernetes.io/gce-pd,kubernetes.io/vsphere-vo...
CreationTimestamp:  Mon, 26 Feb 2024 05:42:57 +
Spec:
Events:  
Name:   kspot-app-node-18de3eeb7b7
Labels: 
Annotations:storage.alpha.kubernetes.io/migrated-plugins:
  
kubernetes.io/aws-ebs,kubernetes.io/azure-disk,kubernetes.io/azure-file,kubernetes.io/cinder,kubernetes.io/gce-pd,kubernetes.io/vsphere-vo...
CreationTimestamp:  Mon, 26 Feb 2024 05:43:12 +
Spec:
Events:  


Thanks and Regards,
Bharat Saini

[signature_1647819183]

From: Wei ZHOU 
Date: Monday, 26 February 2024 at 1:52 AM
To: users@cloudstack.apache.org 
Subject: Re: CKS Storage Provisioner Info
EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.


+1

Or  use the api key of "admin" user.

-Wei

On Sun, Feb 25, 2024 at 7:57 PM Jayanth Reddy 
wrote:

> Hello Bharat,
> With your login as "admin" user, you should be able to generate keys for
> any user. Please do the below
>
> 1. Go to "Accounts"
> 2. Select the account named "admin"
> 3. Scroll down and click "users"
> 4. Select the "admin-kubeadmin" user
> 5. Then select the button for generation of keys.
>
> Please let me know if that helps.
>
> Thanks,
> Jayanth
>
> Sent from Outlook for Android<https://aka.ms/AAb9ysg>
>
>
>

--- Disclaimer: --
This message and its contents are intended solely for the designated addressee 
and are proprietary to Kloudspot. The information in this email is meant 
exclusively for Kloudspot business use. Any use by individuals other than the 
addressee constitutes misuse and an infringement of Kloudspot's proprietary 
rights. If you are not the intended recipient, please return this email to the 
sender. Kloudspot cannot guarantee the security or error-free transmission of 
e-mail communications. Information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or contain viruses. Therefore, Kloudspot 
shall not be liable for any issues arising from the transmission of this email.

Re: CKS Storage Provisioner Info

[Wei ZHOU]

+1

Or  use the api key of "admin" user.

-Wei

On Sun, Feb 25, 2024 at 7:57 PM Jayanth Reddy 
wrote:

> Hello Bharat,
> With your login as "admin" user, you should be able to generate keys for
> any user. Please do the below
>
> 1. Go to "Accounts"
> 2. Select the account named "admin"
> 3. Scroll down and click "users"
> 4. Select the "admin-kubeadmin" user
> 5. Then select the button for generation of keys.
>
> Please let me know if that helps.
>
> Thanks,
> Jayanth
>
> Sent from Outlook for Android
>
>
>

Re: CKS Storage Provisioner Info

[Jayanth Reddy]

Hello Bharat,
With your login as "admin" user, you should be able to generate keys for any 
user. Please do the below

1. Go to "Accounts"
2. Select the account named "admin"
3. Scroll down and click "users"
4. Select the "admin-kubeadmin" user
5. Then select the button for generation of keys.

Please let me know if that helps.

Thanks,
Jayanth

Sent from Outlook for Android<https://aka.ms/AAb9ysg>


From: Bharat Bhushan Saini 
Sent: Monday, February 26, 2024 12:19:53 am
To: users@cloudstack.apache.org 
Subject: Re: CKS Storage Provisioner Info

Hi Jayanth,

Have to check with the github issue no. you shared.

But just fyi, the cluster is made in root domain with admin account. The 
regeneration of API from UI is not there with admin account and can’t able to 
login in admin-kubeadmin account with random UUID (fetched from database). Also 
I like to let you know that the N/w is untagged with satisfied all requirement 
as it is already use in normal vm installation.

Thanks and Regards,
Bharat Saini

[signature_1671206932]

From: Jayanth Reddy 
Date: Sunday, 25 February 2024 at 11:47 PM
To: users@cloudstack.apache.org 
Subject: Re: CKS Storage Provisioner Info
EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.


Hello Bharath,
Sorry, I missed that. Have you tried
https://github.com/apache/cloudstack/issues/8695#issuecomment-1961277784
already? The UI should also have a button on the top-right as "Generate new
API / Secret Keys".
Regenerating API keys might break some functionalities of existing k8s
clusters (devs can shed some light here). In your case, if these are not
created, please generate or if they are created, please copy to create k8s
secret "cloudstack-secret".
Are your k8s clusters in "running" state (I see that it is in "running"
state on GH image)? I hope network requirements are satisfied as well for
CKS to work, please refer
https://github.com/apache/cloudstack/issues/6437#issuecomment-1150218961
and of-course should be valid as you got the clusters to "running" state.

And for your information, I've not encountered issues like these with my
4.18.x and now on 4.19.0.0.

Thanks,
Jayanth

On Sun, Feb 25, 2024 at 11:33 PM Bharat Bhushan Saini
 wrote:

> Hi Jayanth,
>
> The issue was already raised on the github
> https://github.com/apache/cloudstack/issues/8695
>
>
>
> I don’t have the API and Keys to create the secret manually by which I can
> configure CSI driver for storage provisioner for persistent storage with
> CKS.
>
> The wasn’t generated by cloudstack and I am not able to find any way to
> generate them.
>
>
>
> Note: I also want to raise one more issue like when the cluster is created
> 6 secret is created by default but after some time 2 secret was vanished, I
> didn’t find the RCA of that, so didn’t share till now and that secret is
> belongs from kube-system ns.
>
>
>
> Thanks and Regards,
>
> Bharat Saini
>
>
>
> [image: signature_2891567627]
>
>
>
> *From: *Jayanth Reddy 
> *Date: *Sunday, 25 February 2024 at 11:25 PM
> *To: *users@cloudstack.apache.org 
> *Subject: *Re: CKS Storage Provisioner Info
>
> EXTERNAL EMAIL: Please verify the sender email address before taking any
> action, replying, clicking any link or opening any attachment.
>
>
> Hello Bharat,
> It's strange that the cloudstack-secret wasn't created. Please consider
> raising an issue on Github.
>
> May I know what you're going to do with the password of the
> admin-kubeadmin user?
>
> https://github.com/apalia/cloudstack-csi-driver?tab=readme-ov-file#configuration
> should accept the API Keys instead. Have the keys been generated already by
> you or CKS?
>
> Thanks,
> Jayanth
>
> On Sun, Feb 25, 2024 at 11:14 PM Bharat Bhushan Saini
>  wrote:
>
> > Hi Wei,
> >
> >
> >
> > I got that it is used to access API’s and I want that as I need to
> install
> > CSI driver for the CKS storage provisioner and didn’t get the API’s as
> the
> > cloudstack-secret was not spawn when I start a cluster.
> >
> >
> >
> > I checked in mysql database for UUID and put as a password but not able
> to
> > login and the admin-kubeadmin only shown in mysql database not in the UI.
> >
> >
> >
> > Thanks and Regards,
> >
> > Bharat Saini
> >
> >
> >
> > [image: signature_4059312007]
> >
> >
> >
> > *From: *Wei ZHOU 
> > *Date: *Sunday, 25 February 2024 at 9:18 PM
> > *To: *users@cloudstack.apache.org 
> > *Subject: *Re: CKS Storage Provisioner Info
> >
&g

Re: CKS Storage Provisioner Info

[Bharat Bhushan Saini]

Hi Jayanth,

Have to check with the github issue no. you shared.

But just fyi, the cluster is made in root domain with admin account. The 
regeneration of API from UI is not there with admin account and can’t able to 
login in admin-kubeadmin account with random UUID (fetched from database). Also 
I like to let you know that the N/w is untagged with satisfied all requirement 
as it is already use in normal vm installation.

Thanks and Regards,
Bharat Saini

[signature_1671206932]

From: Jayanth Reddy 
Date: Sunday, 25 February 2024 at 11:47 PM
To: users@cloudstack.apache.org 
Subject: Re: CKS Storage Provisioner Info
EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.


Hello Bharath,
Sorry, I missed that. Have you tried
https://github.com/apache/cloudstack/issues/8695#issuecomment-1961277784
already? The UI should also have a button on the top-right as "Generate new
API / Secret Keys".
Regenerating API keys might break some functionalities of existing k8s
clusters (devs can shed some light here). In your case, if these are not
created, please generate or if they are created, please copy to create k8s
secret "cloudstack-secret".
Are your k8s clusters in "running" state (I see that it is in "running"
state on GH image)? I hope network requirements are satisfied as well for
CKS to work, please refer
https://github.com/apache/cloudstack/issues/6437#issuecomment-1150218961
and of-course should be valid as you got the clusters to "running" state.

And for your information, I've not encountered issues like these with my
4.18.x and now on 4.19.0.0.

Thanks,
Jayanth

On Sun, Feb 25, 2024 at 11:33 PM Bharat Bhushan Saini
 wrote:

> Hi Jayanth,
>
> The issue was already raised on the github
> https://github.com/apache/cloudstack/issues/8695
>
>
>
> I don’t have the API and Keys to create the secret manually by which I can
> configure CSI driver for storage provisioner for persistent storage with
> CKS.
>
> The wasn’t generated by cloudstack and I am not able to find any way to
> generate them.
>
>
>
> Note: I also want to raise one more issue like when the cluster is created
> 6 secret is created by default but after some time 2 secret was vanished, I
> didn’t find the RCA of that, so didn’t share till now and that secret is
> belongs from kube-system ns.
>
>
>
> Thanks and Regards,
>
> Bharat Saini
>
>
>
> [image: signature_2891567627]
>
>
>
> *From: *Jayanth Reddy 
> *Date: *Sunday, 25 February 2024 at 11:25 PM
> *To: *users@cloudstack.apache.org 
> *Subject: *Re: CKS Storage Provisioner Info
>
> EXTERNAL EMAIL: Please verify the sender email address before taking any
> action, replying, clicking any link or opening any attachment.
>
>
> Hello Bharat,
> It's strange that the cloudstack-secret wasn't created. Please consider
> raising an issue on Github.
>
> May I know what you're going to do with the password of the
> admin-kubeadmin user?
>
> https://github.com/apalia/cloudstack-csi-driver?tab=readme-ov-file#configuration
> should accept the API Keys instead. Have the keys been generated already by
> you or CKS?
>
> Thanks,
> Jayanth
>
> On Sun, Feb 25, 2024 at 11:14 PM Bharat Bhushan Saini
>  wrote:
>
> > Hi Wei,
> >
> >
> >
> > I got that it is used to access API’s and I want that as I need to
> install
> > CSI driver for the CKS storage provisioner and didn’t get the API’s as
> the
> > cloudstack-secret was not spawn when I start a cluster.
> >
> >
> >
> > I checked in mysql database for UUID and put as a password but not able
> to
> > login and the admin-kubeadmin only shown in mysql database not in the UI.
> >
> >
> >
> > Thanks and Regards,
> >
> > Bharat Saini
> >
> >
> >
> > [image: signature_4059312007]
> >
> >
> >
> > *From: *Wei ZHOU 
> > *Date: *Sunday, 25 February 2024 at 9:18 PM
> > *To: *users@cloudstack.apache.org 
> > *Subject: *Re: CKS Storage Provisioner Info
> >
> > EXTERNAL EMAIL: Please verify the sender email address before taking any
> > action, replying, clicking any link or opening any attachment.
> >
> >
> > It is just used to access cloudstack API via api key and secret key.
> > Its password is a random UUID.
> >
> > -Wei
> >
> >
> >
> > On Sun, Feb 25, 2024 at 3:29 PM Bharat Bhushan Saini
> >  wrote:
> >
> > > Hi All,
> > >
> > >
> > >
> > > Somebody Please share the default credentials for the admin-kubeadmin
> > user.
> > >
> > >
> >

Re: CKS Storage Provisioner Info

[Jayanth Reddy]

Hello Bharath,
Sorry, I missed that. Have you tried
https://github.com/apache/cloudstack/issues/8695#issuecomment-1961277784
already? The UI should also have a button on the top-right as "Generate new
API / Secret Keys".
Regenerating API keys might break some functionalities of existing k8s
clusters (devs can shed some light here). In your case, if these are not
created, please generate or if they are created, please copy to create k8s
secret "cloudstack-secret".
Are your k8s clusters in "running" state (I see that it is in "running"
state on GH image)? I hope network requirements are satisfied as well for
CKS to work, please refer
https://github.com/apache/cloudstack/issues/6437#issuecomment-1150218961
and of-course should be valid as you got the clusters to "running" state.

And for your information, I've not encountered issues like these with my
4.18.x and now on 4.19.0.0.

Thanks,
Jayanth

On Sun, Feb 25, 2024 at 11:33 PM Bharat Bhushan Saini
 wrote:

> Hi Jayanth,
>
> The issue was already raised on the github
> https://github.com/apache/cloudstack/issues/8695
>
>
>
> I don’t have the API and Keys to create the secret manually by which I can
> configure CSI driver for storage provisioner for persistent storage with
> CKS.
>
> The wasn’t generated by cloudstack and I am not able to find any way to
> generate them.
>
>
>
> Note: I also want to raise one more issue like when the cluster is created
> 6 secret is created by default but after some time 2 secret was vanished, I
> didn’t find the RCA of that, so didn’t share till now and that secret is
> belongs from kube-system ns.
>
>
>
> Thanks and Regards,
>
> Bharat Saini
>
>
>
> [image: signature_2891567627]
>
>
>
> *From: *Jayanth Reddy 
> *Date: *Sunday, 25 February 2024 at 11:25 PM
> *To: *users@cloudstack.apache.org 
> *Subject: *Re: CKS Storage Provisioner Info
>
> EXTERNAL EMAIL: Please verify the sender email address before taking any
> action, replying, clicking any link or opening any attachment.
>
>
> Hello Bharat,
> It's strange that the cloudstack-secret wasn't created. Please consider
> raising an issue on Github.
>
> May I know what you're going to do with the password of the
> admin-kubeadmin user?
>
> https://github.com/apalia/cloudstack-csi-driver?tab=readme-ov-file#configuration
> should accept the API Keys instead. Have the keys been generated already by
> you or CKS?
>
> Thanks,
> Jayanth
>
> On Sun, Feb 25, 2024 at 11:14 PM Bharat Bhushan Saini
>  wrote:
>
> > Hi Wei,
> >
> >
> >
> > I got that it is used to access API’s and I want that as I need to
> install
> > CSI driver for the CKS storage provisioner and didn’t get the API’s as
> the
> > cloudstack-secret was not spawn when I start a cluster.
> >
> >
> >
> > I checked in mysql database for UUID and put as a password but not able
> to
> > login and the admin-kubeadmin only shown in mysql database not in the UI.
> >
> >
> >
> > Thanks and Regards,
> >
> > Bharat Saini
> >
> >
> >
> > [image: signature_4059312007]
> >
> >
> >
> > *From: *Wei ZHOU 
> > *Date: *Sunday, 25 February 2024 at 9:18 PM
> > *To: *users@cloudstack.apache.org 
> > *Subject: *Re: CKS Storage Provisioner Info
> >
> > EXTERNAL EMAIL: Please verify the sender email address before taking any
> > action, replying, clicking any link or opening any attachment.
> >
> >
> > It is just used to access cloudstack API via api key and secret key.
> > Its password is a random UUID.
> >
> > -Wei
> >
> >
> >
> > On Sun, Feb 25, 2024 at 3:29 PM Bharat Bhushan Saini
> >  wrote:
> >
> > > Hi All,
> > >
> > >
> > >
> > > Somebody Please share the default credentials for the admin-kubeadmin
> > user.
> > >
> > >
> > >
> > > Thanks and Regards,
> > >
> > > Bharat Saini
> > >
> > >
> > >
> > > [image: signature_2022216497]
> > >
> > >
> > >
> > > *From: *Bharat Bhushan Saini 
> > > *Date: *Friday, 23 February 2024 at 3:14 PM
> > > *To: *users@cloudstack.apache.org 
> > > *Subject: *Re: CKS Storage Provisioner Info
> > >
> > > EXTERNAL EMAIL: Please verify the sender email address before taking
> any
> > > action, replying, clicking any link or opening any attachment.
> > >
> > >
> > >
> > > Hi Community/Vivek,
> > >
> > >
> > >
> > >

Re: CKS Storage Provisioner Info

[Bharat Bhushan Saini]

Hi Jayanth,

The issue was already raised on the github 
https://github.com/apache/cloudstack/issues/8695

I don’t have the API and Keys to create the secret manually by which I can 
configure CSI driver for storage provisioner for persistent storage with CKS.
The wasn’t generated by cloudstack and I am not able to find any way to 
generate them.

Note: I also want to raise one more issue like when the cluster is created 6 
secret is created by default but after some time 2 secret was vanished, I 
didn’t find the RCA of that, so didn’t share till now and that secret is 
belongs from kube-system ns.

Thanks and Regards,
Bharat Saini

[signature_2891567627]

From: Jayanth Reddy 
Date: Sunday, 25 February 2024 at 11:25 PM
To: users@cloudstack.apache.org 
Subject: Re: CKS Storage Provisioner Info
EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.


Hello Bharat,
It's strange that the cloudstack-secret wasn't created. Please consider
raising an issue on Github.

May I know what you're going to do with the password of the
admin-kubeadmin user?
https://github.com/apalia/cloudstack-csi-driver?tab=readme-ov-file#configuration
should accept the API Keys instead. Have the keys been generated already by
you or CKS?

Thanks,
Jayanth

On Sun, Feb 25, 2024 at 11:14 PM Bharat Bhushan Saini
 wrote:

> Hi Wei,
>
>
>
> I got that it is used to access API’s and I want that as I need to install
> CSI driver for the CKS storage provisioner and didn’t get the API’s as the
> cloudstack-secret was not spawn when I start a cluster.
>
>
>
> I checked in mysql database for UUID and put as a password but not able to
> login and the admin-kubeadmin only shown in mysql database not in the UI.
>
>
>
> Thanks and Regards,
>
> Bharat Saini
>
>
>
> [image: signature_4059312007]
>
>
>
> *From: *Wei ZHOU 
> *Date: *Sunday, 25 February 2024 at 9:18 PM
> *To: *users@cloudstack.apache.org 
> *Subject: *Re: CKS Storage Provisioner Info
>
> EXTERNAL EMAIL: Please verify the sender email address before taking any
> action, replying, clicking any link or opening any attachment.
>
>
> It is just used to access cloudstack API via api key and secret key.
> Its password is a random UUID.
>
> -Wei
>
>
>
> On Sun, Feb 25, 2024 at 3:29 PM Bharat Bhushan Saini
>  wrote:
>
> > Hi All,
> >
> >
> >
> > Somebody Please share the default credentials for the admin-kubeadmin
> user.
> >
> >
> >
> > Thanks and Regards,
> >
> > Bharat Saini
> >
> >
> >
> > [image: signature_2022216497]
> >
> >
> >
> > *From: *Bharat Bhushan Saini 
> > *Date: *Friday, 23 February 2024 at 3:14 PM
> > *To: *users@cloudstack.apache.org 
> > *Subject: *Re: CKS Storage Provisioner Info
> >
> > EXTERNAL EMAIL: Please verify the sender email address before taking any
> > action, replying, clicking any link or opening any attachment.
> >
> >
> >
> > Hi Community/Vivek,
> >
> >
> >
> > I created a discussion form on github discussion.
> >
> >
> >
> > Kindly check the information at
> > https://github.com/apache/cloudstack/issues/8695
> >
> >
> >
> > Thanks and Regards,
> >
> > Bharat Saini
> >
> >
> >
> > [image: signature_2677501444]
> >
> >
> >
> > *From: *Vivek Kumar 
> > *Date: *Friday, 23 February 2024 at 12:50 PM
> > *To: *users@cloudstack.apache.org 
> > *Subject: *Re: CKS Storage Provisioner Info
> >
> > EXTERNAL EMAIL: Please verify the sender email address before taking any
> > action, replying, clicking any link or opening any attachment.
> >
> >
> > Hello Bharat,
> >
> > Can you try to install plugin manually and see if that works or not.
> >
> >
> > Vivek Kumar
> > Sr. Manager - Cloud & DevOps
> > TechOps | Indiqus Technologies
> >
> > vivek.ku...@indiqus.com <mailto:vivek.ku...@indiqus.com
> > >
> > www.indiqus.com<http://www.indiqus.com> <https://www.indiqus.com/>
> >
> >
> >
> >
> > > On 23-Feb-2024, at 11:16 AM, Bharat Bhushan Saini
> >  wrote:
> > >
> > > Hi Wei/Vivek/Kiran,
> > >
> > > Kindly lookout in this.
> > >
> > > Thanks and Regards,
> > > Bharat Saini
> > >
> > >
> > >
> > > From: Bharat Bhushan Saini  > mailto:bharat.sa...@kloudspot.com.INVALID
> 
> > >>
> > > Date: Friday, 23 February 2024 at 12:56 AM
> > > T

Re: CKS Storage Provisioner Info

[Jayanth Reddy]

Hello Bharat,
It's strange that the cloudstack-secret wasn't created. Please consider
raising an issue on Github.

May I know what you're going to do with the password of the
admin-kubeadmin user?
https://github.com/apalia/cloudstack-csi-driver?tab=readme-ov-file#configuration
should accept the API Keys instead. Have the keys been generated already by
you or CKS?

Thanks,
Jayanth

On Sun, Feb 25, 2024 at 11:14 PM Bharat Bhushan Saini
 wrote:

> Hi Wei,
>
>
>
> I got that it is used to access API’s and I want that as I need to install
> CSI driver for the CKS storage provisioner and didn’t get the API’s as the
> cloudstack-secret was not spawn when I start a cluster.
>
>
>
> I checked in mysql database for UUID and put as a password but not able to
> login and the admin-kubeadmin only shown in mysql database not in the UI.
>
>
>
> Thanks and Regards,
>
> Bharat Saini
>
>
>
> [image: signature_4059312007]
>
>
>
> *From: *Wei ZHOU 
> *Date: *Sunday, 25 February 2024 at 9:18 PM
> *To: *users@cloudstack.apache.org 
> *Subject: *Re: CKS Storage Provisioner Info
>
> EXTERNAL EMAIL: Please verify the sender email address before taking any
> action, replying, clicking any link or opening any attachment.
>
>
> It is just used to access cloudstack API via api key and secret key.
> Its password is a random UUID.
>
> -Wei
>
>
>
> On Sun, Feb 25, 2024 at 3:29 PM Bharat Bhushan Saini
>  wrote:
>
> > Hi All,
> >
> >
> >
> > Somebody Please share the default credentials for the admin-kubeadmin
> user.
> >
> >
> >
> > Thanks and Regards,
> >
> > Bharat Saini
> >
> >
> >
> > [image: signature_2022216497]
> >
> >
> >
> > *From: *Bharat Bhushan Saini 
> > *Date: *Friday, 23 February 2024 at 3:14 PM
> > *To: *users@cloudstack.apache.org 
> > *Subject: *Re: CKS Storage Provisioner Info
> >
> > EXTERNAL EMAIL: Please verify the sender email address before taking any
> > action, replying, clicking any link or opening any attachment.
> >
> >
> >
> > Hi Community/Vivek,
> >
> >
> >
> > I created a discussion form on github discussion.
> >
> >
> >
> > Kindly check the information at
> > https://github.com/apache/cloudstack/issues/8695
> >
> >
> >
> > Thanks and Regards,
> >
> > Bharat Saini
> >
> >
> >
> > [image: signature_2677501444]
> >
> >
> >
> > *From: *Vivek Kumar 
> > *Date: *Friday, 23 February 2024 at 12:50 PM
> > *To: *users@cloudstack.apache.org 
> > *Subject: *Re: CKS Storage Provisioner Info
> >
> > EXTERNAL EMAIL: Please verify the sender email address before taking any
> > action, replying, clicking any link or opening any attachment.
> >
> >
> > Hello Bharat,
> >
> > Can you try to install plugin manually and see if that works or not.
> >
> >
> > Vivek Kumar
> > Sr. Manager - Cloud & DevOps
> > TechOps | Indiqus Technologies
> >
> > vivek.ku...@indiqus.com <mailto:vivek.ku...@indiqus.com
> > >
> >     www.indiqus.com <https://www.indiqus.com/>
> >
> >
> >
> >
> > > On 23-Feb-2024, at 11:16 AM, Bharat Bhushan Saini
> >  wrote:
> > >
> > > Hi Wei/Vivek/Kiran,
> > >
> > > Kindly lookout in this.
> > >
> > > Thanks and Regards,
> > > Bharat Saini
> > >
> > >
> > >
> > > From: Bharat Bhushan Saini  > mailto:bharat.sa...@kloudspot.com.INVALID
> 
> > >>
> > > Date: Friday, 23 February 2024 at 12:56 AM
> > > To: users@cloudstack.apache.org <mailto:users@cloudstack.apache.org
> > >  > mailto:users@cloudstack.apache.org  <
> users@cloudstack.apache.org>>>
> > > Subject: Re: CKS Storage Provisioner Info
> > >
> > > EXTERNAL EMAIL: Please verify the sender email address before taking
> any
> > action, replying, clicking any link or opening any attachment.
> > >
> > > Hi Vivek,
> > >
> > > I deployed cloudstack with version 4.18.1.
> > > I think it should be present in this version.
> > >
> > > Thanks and Regards,
> > > Bharat Saini
> > >
> > >
> > >
> > > From: Vivek Kumar  > mailto:vivek.ku...@indiqus.com.INVALID 
> >>
> > > Date: Friday, 23 February 2024 at 12:48 AM
> > > To: users@cloudstack.apache.org <mailto:users@cloudstack.apache.org
> > >  > mailto:users@clou

Re: CKS Storage Provisioner Info

[Bharat Bhushan Saini]

Hi Wei,

I got that it is used to access API’s and I want that as I need to install CSI 
driver for the CKS storage provisioner and didn’t get the API’s as the 
cloudstack-secret was not spawn when I start a cluster.

I checked in mysql database for UUID and put as a password but not able to 
login and the admin-kubeadmin only shown in mysql database not in the UI.

Thanks and Regards,
Bharat Saini

[signature_4059312007]

From: Wei ZHOU 
Date: Sunday, 25 February 2024 at 9:18 PM
To: users@cloudstack.apache.org 
Subject: Re: CKS Storage Provisioner Info
EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.


It is just used to access cloudstack API via api key and secret key.
Its password is a random UUID.

-Wei



On Sun, Feb 25, 2024 at 3:29 PM Bharat Bhushan Saini
 wrote:

> Hi All,
>
>
>
> Somebody Please share the default credentials for the admin-kubeadmin user.
>
>
>
> Thanks and Regards,
>
> Bharat Saini
>
>
>
> [image: signature_2022216497]
>
>
>
> *From: *Bharat Bhushan Saini 
> *Date: *Friday, 23 February 2024 at 3:14 PM
> *To: *users@cloudstack.apache.org 
> *Subject: *Re: CKS Storage Provisioner Info
>
> EXTERNAL EMAIL: Please verify the sender email address before taking any
> action, replying, clicking any link or opening any attachment.
>
>
>
> Hi Community/Vivek,
>
>
>
> I created a discussion form on github discussion.
>
>
>
> Kindly check the information at
> https://github.com/apache/cloudstack/issues/8695
>
>
>
> Thanks and Regards,
>
> Bharat Saini
>
>
>
> [image: signature_2677501444]
>
>
>
> *From: *Vivek Kumar 
> *Date: *Friday, 23 February 2024 at 12:50 PM
> *To: *users@cloudstack.apache.org 
> *Subject: *Re: CKS Storage Provisioner Info
>
> EXTERNAL EMAIL: Please verify the sender email address before taking any
> action, replying, clicking any link or opening any attachment.
>
>
> Hello Bharat,
>
> Can you try to install plugin manually and see if that works or not.
>
>
> Vivek Kumar
> Sr. Manager - Cloud & DevOps
> TechOps | Indiqus Technologies
>
> vivek.ku...@indiqus.com <mailto:vivek.ku...@indiqus.com
> >
> www.indiqus.com<http://www.indiqus.com> <https://www.indiqus.com/>
>
>
>
>
> > On 23-Feb-2024, at 11:16 AM, Bharat Bhushan Saini
>  wrote:
> >
> > Hi Wei/Vivek/Kiran,
> >
> > Kindly lookout in this.
> >
> > Thanks and Regards,
> > Bharat Saini
> >
> >
> >
> > From: Bharat Bhushan Saini  mailto:bharat.sa...@kloudspot.com.INVALID
> >>
> > Date: Friday, 23 February 2024 at 12:56 AM
> > To: users@cloudstack.apache.org <mailto:users@cloudstack.apache.org
> >  mailto:users@cloudstack.apache.org >>
> > Subject: Re: CKS Storage Provisioner Info
> >
> > EXTERNAL EMAIL: Please verify the sender email address before taking any
> action, replying, clicking any link or opening any attachment.
> >
> > Hi Vivek,
> >
> > I deployed cloudstack with version 4.18.1.
> > I think it should be present in this version.
> >
> > Thanks and Regards,
> > Bharat Saini
> >
> >
> >
> > From: Vivek Kumar  mailto:vivek.ku...@indiqus.com.INVALID >>
> > Date: Friday, 23 February 2024 at 12:48 AM
> > To: users@cloudstack.apache.org <mailto:users@cloudstack.apache.org
> >  mailto:users@cloudstack.apache.org >>
> > Subject: Re: CKS Storage Provisioner Info
> >
> > EXTERNAL EMAIL: Please verify the sender email address before taking any
> action, replying, clicking any link or opening any attachment.
> >
> >
> > Hello Bharat,
> >
> > Then you will have to deploy the cloudstack-kubernetes-provider, however
> after 4.16, it’s automatically deployed, Follow the instruction in the link
> -https://github.com/apache/cloudstack-kubernetes-provider
> >
> >
> > 1- Create a file called - cloud-config and put the below information - (
> you can create an user under your account and provide it’s apikey and
> secret key )
> >
> >
> > [Global]
> > api-url = 
> > api-key = 
> > secret-key = 
> >
> >
> > 2- kubectl -n kube-system create secret generic cloudstack-secret
> --from-file=cloud-config
> > 3- then deploy the controller -
> >
> > You can then use the provided example deployment.yaml <
> https://github.com/apache/cloudstack-kubernetes-provider/blob/main/deployment.yaml><https://github.com/apache/cloudstack-kubernetes-provider/blob/main/deployment.yaml%3e>
> to dep

Re: CKS Storage Provisioner Info

[Wei ZHOU]

It is just used to access cloudstack API via api key and secret key.
Its password is a random UUID.

-Wei



On Sun, Feb 25, 2024 at 3:29 PM Bharat Bhushan Saini
 wrote:

> Hi All,
>
>
>
> Somebody Please share the default credentials for the admin-kubeadmin user.
>
>
>
> Thanks and Regards,
>
> Bharat Saini
>
>
>
> [image: signature_2022216497]
>
>
>
> *From: *Bharat Bhushan Saini 
> *Date: *Friday, 23 February 2024 at 3:14 PM
> *To: *users@cloudstack.apache.org 
> *Subject: *Re: CKS Storage Provisioner Info
>
> EXTERNAL EMAIL: Please verify the sender email address before taking any
> action, replying, clicking any link or opening any attachment.
>
>
>
> Hi Community/Vivek,
>
>
>
> I created a discussion form on github discussion.
>
>
>
> Kindly check the information at
> https://github.com/apache/cloudstack/issues/8695
>
>
>
> Thanks and Regards,
>
> Bharat Saini
>
>
>
> [image: signature_2677501444]
>
>
>
> *From: *Vivek Kumar 
> *Date: *Friday, 23 February 2024 at 12:50 PM
> *To: *users@cloudstack.apache.org 
> *Subject: *Re: CKS Storage Provisioner Info
>
> EXTERNAL EMAIL: Please verify the sender email address before taking any
> action, replying, clicking any link or opening any attachment.
>
>
> Hello Bharat,
>
> Can you try to install plugin manually and see if that works or not.
>
>
> Vivek Kumar
> Sr. Manager - Cloud & DevOps
> TechOps | Indiqus Technologies
>
> vivek.ku...@indiqus.com <mailto:vivek.ku...@indiqus.com
> >
> www.indiqus.com <https://www.indiqus.com/>
>
>
>
>
> > On 23-Feb-2024, at 11:16 AM, Bharat Bhushan Saini
>  wrote:
> >
> > Hi Wei/Vivek/Kiran,
> >
> > Kindly lookout in this.
> >
> > Thanks and Regards,
> > Bharat Saini
> >
> >
> >
> > From: Bharat Bhushan Saini  mailto:bharat.sa...@kloudspot.com.INVALID
> >>
> > Date: Friday, 23 February 2024 at 12:56 AM
> > To: users@cloudstack.apache.org <mailto:users@cloudstack.apache.org
> >  mailto:users@cloudstack.apache.org >>
> > Subject: Re: CKS Storage Provisioner Info
> >
> > EXTERNAL EMAIL: Please verify the sender email address before taking any
> action, replying, clicking any link or opening any attachment.
> >
> > Hi Vivek,
> >
> > I deployed cloudstack with version 4.18.1.
> > I think it should be present in this version.
> >
> > Thanks and Regards,
> > Bharat Saini
> >
> >
> >
> > From: Vivek Kumar  mailto:vivek.ku...@indiqus.com.INVALID >>
> > Date: Friday, 23 February 2024 at 12:48 AM
> > To: users@cloudstack.apache.org <mailto:users@cloudstack.apache.org
> >  mailto:users@cloudstack.apache.org >>
> > Subject: Re: CKS Storage Provisioner Info
> >
> > EXTERNAL EMAIL: Please verify the sender email address before taking any
> action, replying, clicking any link or opening any attachment.
> >
> >
> > Hello Bharat,
> >
> > Then you will have to deploy the cloudstack-kubernetes-provider, however
> after 4.16, it’s automatically deployed, Follow the instruction in the link
> -https://github.com/apache/cloudstack-kubernetes-provider
> >
> >
> > 1- Create a file called - cloud-config and put the below information - (
> you can create an user under your account and provide it’s apikey and
> secret key )
> >
> >
> > [Global]
> > api-url = 
> > api-key = 
> > secret-key = 
> >
> >
> > 2- kubectl -n kube-system create secret generic cloudstack-secret
> --from-file=cloud-config
> > 3- then deploy the controller -
> >
> > You can then use the provided example deployment.yaml <
> https://github.com/apache/cloudstack-kubernetes-provider/blob/main/deployment.yaml>
> to deploy the controller:
> >
> > kubectl apply -f deployment.yaml
> >
> >
> >
> >
> > Vivek Kumar
> > Sr. Manager - Cloud & DevOps
> > TechOps | Indiqus Technologies
> >
> > vivek.ku...@indiqus.com <mailto:vivek.ku...@indiqus.com
> > <mailto:vivek.ku...@indiqus.com
> >
> > www.indiqus.com <http://www.indiqus.com/> <
> https://www.indiqus.com/>
> >
> >
> >
> >
> > > On 23-Feb-2024, at 12:08 AM, Bharat Bhushan Saini
>  mailto:bharat.sa...@kloudspot.com.INVALID
> >> wrote:
> > >
> > > Hi Vivek,
> > >
> > > I am glad and thankful to you for sharing the information, for the
> configuration of CSI driver.
> > >
> > 

Re: CKS Storage Provisioner Info

[Bharat Bhushan Saini]

Hi All,

Somebody Please share the default credentials for the admin-kubeadmin user.

Thanks and Regards,
Bharat Saini

[signature_2022216497]

From: Bharat Bhushan Saini 
Date: Friday, 23 February 2024 at 3:14 PM
To: users@cloudstack.apache.org 
Subject: Re: CKS Storage Provisioner Info
EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.

Hi Community/Vivek,

I created a discussion form on github discussion.

Kindly check the information at https://github.com/apache/cloudstack/issues/8695

Thanks and Regards,
Bharat Saini

[signature_2677501444]

From: Vivek Kumar 
Date: Friday, 23 February 2024 at 12:50 PM
To: users@cloudstack.apache.org 
Subject: Re: CKS Storage Provisioner Info
EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.


Hello Bharat,

Can you try to install plugin manually and see if that works or not.


Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies

vivek.ku...@indiqus.com <mailto:vivek.ku...@indiqus.com>
www.indiqus.com<http://www.indiqus.com> <https://www.indiqus.com/>




> On 23-Feb-2024, at 11:16 AM, Bharat Bhushan Saini 
>  wrote:
>
> Hi Wei/Vivek/Kiran,
>
> Kindly lookout in this.
>
> Thanks and Regards,
> Bharat Saini
>
>
>
> From: Bharat Bhushan Saini  <mailto:bharat.sa...@kloudspot.com.INVALID>>
> Date: Friday, 23 February 2024 at 12:56 AM
> To: users@cloudstack.apache.org <mailto:users@cloudstack.apache.org> 
> mailto:users@cloudstack.apache.org>>
> Subject: Re: CKS Storage Provisioner Info
>
> EXTERNAL EMAIL: Please verify the sender email address before taking any 
> action, replying, clicking any link or opening any attachment.
>
> Hi Vivek,
>
> I deployed cloudstack with version 4.18.1.
> I think it should be present in this version.
>
> Thanks and Regards,
> Bharat Saini
>
>
>
> From: Vivek Kumar  <mailto:vivek.ku...@indiqus.com.INVALID>>
> Date: Friday, 23 February 2024 at 12:48 AM
> To: users@cloudstack.apache.org <mailto:users@cloudstack.apache.org> 
> mailto:users@cloudstack.apache.org>>
> Subject: Re: CKS Storage Provisioner Info
>
> EXTERNAL EMAIL: Please verify the sender email address before taking any 
> action, replying, clicking any link or opening any attachment.
>
>
> Hello Bharat,
>
> Then you will have to deploy the cloudstack-kubernetes-provider, however 
> after 4.16, it’s automatically deployed, Follow the instruction in the link 
> -https://github.com/apache/cloudstack-kubernetes-provider
>
>
> 1- Create a file called - cloud-config and put the below information - ( you 
> can create an user under your account and provide it’s apikey and secret key )
>
>
> [Global]
> api-url = 
> api-key = 
> secret-key = 
>
>
> 2- kubectl -n kube-system create secret generic cloudstack-secret 
> --from-file=cloud-config
> 3- then deploy the controller -
>
> You can then use the provided example deployment.yaml 
> <https://github.com/apache/cloudstack-kubernetes-provider/blob/main/deployment.yaml>
>  to deploy the controller:
>
> kubectl apply -f deployment.yaml
>
>
>
>
> Vivek Kumar
> Sr. Manager - Cloud & DevOps
> TechOps | Indiqus Technologies
>
> vivek.ku...@indiqus.com <mailto:vivek.ku...@indiqus.com> 
> <mailto:vivek.ku...@indiqus.com>
> www.indiqus.com<http://www.indiqus.com> <http://www.indiqus.com/> 
> <https://www.indiqus.com/>
>
>
>
>
> > On 23-Feb-2024, at 12:08 AM, Bharat Bhushan Saini 
> >  > <mailto:bharat.sa...@kloudspot.com.INVALID>> wrote:
> >
> > Hi Vivek,
> >
> > I am glad and thankful to you for sharing the information, for the 
> > configuration of CSI driver.
> >
> > But I didn’t have cloudstack-secret in my cluster, sharing the details below
> >
> > cloud@Kspot-App-control-18dd041902a:~$ kubectl get secret cloudstack-secret 
> > -n kube-system
> > Error from server (NotFound): secrets "cloudstack-secret" not found
> > cloud@Kspot-App-control-18dd041902a:~$ kubectl get secret -A -n kube-system
> > NAMESPACE  NAME  TYPE   
> >DATA   AGE
> > kloudspot  dockerregistrykey 
> > kubernetes.io/dockerconfigjson 
> > <http://kubernetes.io/dockerconfigjson><http://kubernetes.io/dockerconfigjson<http://kubernetes.io/dockerconfigjson%3e%3chttp:/kubernetes.io/dockerconfigjson>>
> > 1  8h
> > kube-systembootstrap-token-cb0b

Re: CKS Storage Provisioner Info

[Bharat Bhushan Saini]

Hi Community/Vivek,

I created a discussion form on github discussion.

Kindly check the information at https://github.com/apache/cloudstack/issues/8695

Thanks and Regards,
Bharat Saini

[signature_2677501444]

From: Vivek Kumar 
Date: Friday, 23 February 2024 at 12:50 PM
To: users@cloudstack.apache.org 
Subject: Re: CKS Storage Provisioner Info
EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.


Hello Bharat,

Can you try to install plugin manually and see if that works or not.


Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies

vivek.ku...@indiqus.com <mailto:vivek.ku...@indiqus.com>
www.indiqus.com<http://www.indiqus.com> <https://www.indiqus.com/>




> On 23-Feb-2024, at 11:16 AM, Bharat Bhushan Saini 
>  wrote:
>
> Hi Wei/Vivek/Kiran,
>
> Kindly lookout in this.
>
> Thanks and Regards,
> Bharat Saini
>
>
>
> From: Bharat Bhushan Saini  <mailto:bharat.sa...@kloudspot.com.INVALID>>
> Date: Friday, 23 February 2024 at 12:56 AM
> To: users@cloudstack.apache.org <mailto:users@cloudstack.apache.org> 
> mailto:users@cloudstack.apache.org>>
> Subject: Re: CKS Storage Provisioner Info
>
> EXTERNAL EMAIL: Please verify the sender email address before taking any 
> action, replying, clicking any link or opening any attachment.
>
> Hi Vivek,
>
> I deployed cloudstack with version 4.18.1.
> I think it should be present in this version.
>
> Thanks and Regards,
> Bharat Saini
>
>
>
> From: Vivek Kumar  <mailto:vivek.ku...@indiqus.com.INVALID>>
> Date: Friday, 23 February 2024 at 12:48 AM
> To: users@cloudstack.apache.org <mailto:users@cloudstack.apache.org> 
> mailto:users@cloudstack.apache.org>>
> Subject: Re: CKS Storage Provisioner Info
>
> EXTERNAL EMAIL: Please verify the sender email address before taking any 
> action, replying, clicking any link or opening any attachment.
>
>
> Hello Bharat,
>
> Then you will have to deploy the cloudstack-kubernetes-provider, however 
> after 4.16, it’s automatically deployed, Follow the instruction in the link 
> -https://github.com/apache/cloudstack-kubernetes-provider
>
>
> 1- Create a file called - cloud-config and put the below information - ( you 
> can create an user under your account and provide it’s apikey and secret key )
>
>
> [Global]
> api-url = 
> api-key = 
> secret-key = 
>
>
> 2- kubectl -n kube-system create secret generic cloudstack-secret 
> --from-file=cloud-config
> 3- then deploy the controller -
>
> You can then use the provided example deployment.yaml 
> <https://github.com/apache/cloudstack-kubernetes-provider/blob/main/deployment.yaml>
>  to deploy the controller:
>
> kubectl apply -f deployment.yaml
>
>
>
>
> Vivek Kumar
> Sr. Manager - Cloud & DevOps
> TechOps | Indiqus Technologies
>
> vivek.ku...@indiqus.com <mailto:vivek.ku...@indiqus.com> 
> <mailto:vivek.ku...@indiqus.com>
> www.indiqus.com<http://www.indiqus.com> <http://www.indiqus.com/> 
> <https://www.indiqus.com/>
>
>
>
>
> > On 23-Feb-2024, at 12:08 AM, Bharat Bhushan Saini 
> >  > <mailto:bharat.sa...@kloudspot.com.INVALID>> wrote:
> >
> > Hi Vivek,
> >
> > I am glad and thankful to you for sharing the information, for the 
> > configuration of CSI driver.
> >
> > But I didn’t have cloudstack-secret in my cluster, sharing the details below
> >
> > cloud@Kspot-App-control-18dd041902a:~$ kubectl get secret cloudstack-secret 
> > -n kube-system
> > Error from server (NotFound): secrets "cloudstack-secret" not found
> > cloud@Kspot-App-control-18dd041902a:~$ kubectl get secret -A -n kube-system
> > NAMESPACE  NAME  TYPE   
> >DATA   AGE
> > kloudspot  dockerregistrykey 
> > kubernetes.io/dockerconfigjson 
> > <http://kubernetes.io/dockerconfigjson><http://kubernetes.io/dockerconfigjson<http://kubernetes.io/dockerconfigjson%3e%3chttp:/kubernetes.io/dockerconfigjson>>
> > 1  8h
> > kube-systembootstrap-token-cb0b7f
> > bootstrap.kubernetes.io/token 
> > <http://bootstrap.kubernetes.io/token><http://bootstrap.kubernetes.io/token<http://bootstrap.kubernetes.io/token%3e%3chttp:/bootstrap.kubernetes.io/token>>
> >  6  8h
> > kubernetes-dashboard   kubernetes-dashboard-certsOpaque 
> >0  8h
> > kubernetes-dashboa

Re: CKS Storage Provisioner Info

[Vivek Kumar]

Hello Bharat,

Can you try to install plugin manually and see if that works or not. 


Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies

vivek.ku...@indiqus.com <mailto:vivek.ku...@indiqus.com>
www.indiqus.com <https://www.indiqus.com/>




> On 23-Feb-2024, at 11:16 AM, Bharat Bhushan Saini 
>  wrote:
> 
> Hi Wei/Vivek/Kiran,
>  
> Kindly lookout in this.
>  
> Thanks and Regards,
> Bharat Saini
>  
> 
>  
> From: Bharat Bhushan Saini  <mailto:bharat.sa...@kloudspot.com.INVALID>>
> Date: Friday, 23 February 2024 at 12:56 AM
> To: users@cloudstack.apache.org <mailto:users@cloudstack.apache.org> 
> mailto:users@cloudstack.apache.org>>
> Subject: Re: CKS Storage Provisioner Info
> 
> EXTERNAL EMAIL: Please verify the sender email address before taking any 
> action, replying, clicking any link or opening any attachment.
>  
> Hi Vivek, 
>  
> I deployed cloudstack with version 4.18.1.
> I think it should be present in this version.
>  
> Thanks and Regards,
> Bharat Saini
>  
> 
>  
> From: Vivek Kumar  <mailto:vivek.ku...@indiqus.com.INVALID>>
> Date: Friday, 23 February 2024 at 12:48 AM
> To: users@cloudstack.apache.org <mailto:users@cloudstack.apache.org> 
> mailto:users@cloudstack.apache.org>>
> Subject: Re: CKS Storage Provisioner Info
> 
> EXTERNAL EMAIL: Please verify the sender email address before taking any 
> action, replying, clicking any link or opening any attachment.
> 
> 
> Hello Bharat,
> 
> Then you will have to deploy the cloudstack-kubernetes-provider, however 
> after 4.16, it’s automatically deployed, Follow the instruction in the link 
> -https://github.com/apache/cloudstack-kubernetes-provider
> 
> 
> 1- Create a file called - cloud-config and put the below information - ( you 
> can create an user under your account and provide it’s apikey and secret key )
> 
> 
> [Global]
> api-url = 
> api-key = 
> secret-key = 
> 
> 
> 2- kubectl -n kube-system create secret generic cloudstack-secret 
> --from-file=cloud-config
> 3- then deploy the controller -
> 
> You can then use the provided example deployment.yaml 
> <https://github.com/apache/cloudstack-kubernetes-provider/blob/main/deployment.yaml>
>  to deploy the controller:
> 
> kubectl apply -f deployment.yaml
> 
> 
> 
> 
> Vivek Kumar
> Sr. Manager - Cloud & DevOps
> TechOps | Indiqus Technologies
> 
> vivek.ku...@indiqus.com <mailto:vivek.ku...@indiqus.com> 
> <mailto:vivek.ku...@indiqus.com>
> www.indiqus.com <http://www.indiqus.com/> <https://www.indiqus.com/>
> 
> 
> 
> 
> > On 23-Feb-2024, at 12:08 AM, Bharat Bhushan Saini 
> >  > <mailto:bharat.sa...@kloudspot.com.INVALID>> wrote:
> >
> > Hi Vivek,
> >
> > I am glad and thankful to you for sharing the information, for the 
> > configuration of CSI driver.
> >
> > But I didn’t have cloudstack-secret in my cluster, sharing the details below
> >
> > cloud@Kspot-App-control-18dd041902a:~$ kubectl get secret cloudstack-secret 
> > -n kube-system
> > Error from server (NotFound): secrets "cloudstack-secret" not found
> > cloud@Kspot-App-control-18dd041902a:~$ kubectl get secret -A -n kube-system
> > NAMESPACE  NAME  TYPE   
> >DATA   AGE
> > kloudspot  dockerregistrykey 
> > kubernetes.io/dockerconfigjson 
> > <http://kubernetes.io/dockerconfigjson><http://kubernetes.io/dockerconfigjson>
> > 1  8h
> > kube-systembootstrap-token-cb0b7f
> > bootstrap.kubernetes.io/token 
> > <http://bootstrap.kubernetes.io/token><http://bootstrap.kubernetes.io/token>
> >  6  8h
> > kubernetes-dashboard   kubernetes-dashboard-certsOpaque 
> >0  8h
> > kubernetes-dashboard   kubernetes-dashboard-csrf Opaque 
> >1  8h
> > kubernetes-dashboard   kubernetes-dashboard-key-holder   Opaque 
> >2  8h
> > kubernetes-dashboard   kubernetes-dashboard-token
> > kubernetes.io/service-account-token 
> > <http://kubernetes.io/service-account-token> 
> > <http://kubernetes.io/service-account-token>  3  8h
> > cloud@Kspot-App-control-18dd041902a:~$
> >
> > I am using v1.28.4 k8s version ISO for the cluster, storage offering and 
> > network is in shared mode and using 1 node cluster withou

Re: CKS Storage Provisioner Info

[Bharat Bhushan Saini]

Hi Wei/Vivek/Kiran,

Kindly lookout in this.

Thanks and Regards,
Bharat Saini

[signature_550033876]

From: Bharat Bhushan Saini 
Date: Friday, 23 February 2024 at 12:56 AM
To: users@cloudstack.apache.org 
Subject: Re: CKS Storage Provisioner Info
EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.

Hi Vivek,

I deployed cloudstack with version 4.18.1.
I think it should be present in this version.

Thanks and Regards,
Bharat Saini

[signature_3238255740]

From: Vivek Kumar 
Date: Friday, 23 February 2024 at 12:48 AM
To: users@cloudstack.apache.org 
Subject: Re: CKS Storage Provisioner Info
EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.


Hello Bharat,

Then you will have to deploy the cloudstack-kubernetes-provider, however after 
4.16, it’s automatically deployed, Follow the instruction in the link - 
https://github.com/apache/cloudstack-kubernetes-provider


1- Create a file called - cloud-config and put the below information - ( you 
can create an user under your account and provide it’s apikey and secret key )


[Global]
api-url = 
api-key = 
secret-key = 


2- kubectl -n kube-system create secret generic cloudstack-secret 
--from-file=cloud-config
3- then deploy the controller -

You can then use the provided example deployment.yaml 
<https://github.com/apache/cloudstack-kubernetes-provider/blob/main/deployment.yaml>
 to deploy the controller:

kubectl apply -f deployment.yaml




Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies

vivek.ku...@indiqus.com <mailto:vivek.ku...@indiqus.com>
www.indiqus.com<http://www.indiqus.com> <https://www.indiqus.com/>




> On 23-Feb-2024, at 12:08 AM, Bharat Bhushan Saini 
>  wrote:
>
> Hi Vivek,
>
> I am glad and thankful to you for sharing the information, for the 
> configuration of CSI driver.
>
> But I didn’t have cloudstack-secret in my cluster, sharing the details below
>
> cloud@Kspot-App-control-18dd041902a:~$ kubectl get secret cloudstack-secret 
> -n kube-system
> Error from server (NotFound): secrets "cloudstack-secret" not found
> cloud@Kspot-App-control-18dd041902a:~$ kubectl get secret -A -n kube-system
> NAMESPACE  NAME  TYPE 
>  DATA   AGE
> kloudspot  dockerregistrykey 
> kubernetes.io/dockerconfigjson <http://kubernetes.io/dockerconfigjson>
> 1  8h
> kube-systembootstrap-token-cb0b7f
> bootstrap.kubernetes.io/token <http://bootstrap.kubernetes.io/token> 
> 6  8h
> kubernetes-dashboard   kubernetes-dashboard-certsOpaque   
>  0  8h
> kubernetes-dashboard   kubernetes-dashboard-csrf Opaque   
>  1  8h
> kubernetes-dashboard   kubernetes-dashboard-key-holder   Opaque   
>  2  8h
> kubernetes-dashboard   kubernetes-dashboard-token
> kubernetes.io/service-account-token 
> <http://kubernetes.io/service-account-token>  3  8h
> cloud@Kspot-App-control-18dd041902a:~$
>
> I am using v1.28.4 k8s version ISO for the cluster, storage offering and 
> network is in shared mode and using 1 node cluster without HA.
>
> Thanks and Regards,
> Bharat Saini
>
>
>
> From: Vivek Kumar  <mailto:vivek.ku...@indiqus.com.INVALID>>
> Date: Thursday, 22 February 2024 at 11:39 PM
> To: users@cloudstack.apache.org <mailto:users@cloudstack.apache.org> 
> mailto:users@cloudstack.apache.org>>
> Subject: Re: CKS Storage Provisioner Info
>
> EXTERNAL EMAIL: Please verify the sender email address before taking any 
> action, replying, clicking any link or opening any attachment.
>
>
> Hello Bharat,
>
> 1- When you deploy a cluster, an additional user is created under your 
> cloudstack account - i.e -kubeadmin,  and apikey and secret key 
> of this kubeadmin user is pushed to the cluster.
>
> This you can find -
>
> root@18dc14302a2:~# kubectl get secret cloudstack-secret -n kube-system
> NAMETYPE DATA   AGE
> cloudstack-secret   Opaque   1  3d5h
>
> To check the more details for this secret -
>
> root@18dc14302a2:~# kubectl get secret cloudstack-secret -n kube-system -o 
> jsonpath='{.data.*}' | base64 -d
> [Global]
> api-url = http://172.27.2.53:8080/client/api
> api-key = 
> ex0HfJJt7YQES4n5dsD3AEL-gr0n__JbfRvfK6cyUi5dbdPx7hyOckJ_enInYOyRewI0IR772KyNY8Sjh0TOdg
> secret-key = 
> IEHR45EK8GHkNo1G5t7eZSw5MARfZcYUvYXR1mR_vn2vv3b_-nQYFt_A_xZWRc4udtPQPKWjWW8kvTnSccAglA
>
>
> Now, you can se

Re: CKS Storage Provisioner Info

[Bharat Bhushan Saini]

Hi Vivek,

I deployed cloudstack with version 4.18.1.
I think it should be present in this version.

Thanks and Regards,
Bharat Saini

[signature_3238255740]

From: Vivek Kumar 
Date: Friday, 23 February 2024 at 12:48 AM
To: users@cloudstack.apache.org 
Subject: Re: CKS Storage Provisioner Info
EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.


Hello Bharat,

Then you will have to deploy the cloudstack-kubernetes-provider, however after 
4.16, it’s automatically deployed, Follow the instruction in the link - 
https://github.com/apache/cloudstack-kubernetes-provider


1- Create a file called - cloud-config and put the below information - ( you 
can create an user under your account and provide it’s apikey and secret key )


[Global]
api-url = 
api-key = 
secret-key = 


2- kubectl -n kube-system create secret generic cloudstack-secret 
--from-file=cloud-config
3- then deploy the controller -

You can then use the provided example deployment.yaml 
<https://github.com/apache/cloudstack-kubernetes-provider/blob/main/deployment.yaml>
 to deploy the controller:

kubectl apply -f deployment.yaml




Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies

vivek.ku...@indiqus.com <mailto:vivek.ku...@indiqus.com>
www.indiqus.com<http://www.indiqus.com> <https://www.indiqus.com/>




> On 23-Feb-2024, at 12:08 AM, Bharat Bhushan Saini 
>  wrote:
>
> Hi Vivek,
>
> I am glad and thankful to you for sharing the information, for the 
> configuration of CSI driver.
>
> But I didn’t have cloudstack-secret in my cluster, sharing the details below
>
> cloud@Kspot-App-control-18dd041902a:~$ kubectl get secret cloudstack-secret 
> -n kube-system
> Error from server (NotFound): secrets "cloudstack-secret" not found
> cloud@Kspot-App-control-18dd041902a:~$ kubectl get secret -A -n kube-system
> NAMESPACE  NAME  TYPE 
>  DATA   AGE
> kloudspot  dockerregistrykey 
> kubernetes.io/dockerconfigjson <http://kubernetes.io/dockerconfigjson>
> 1  8h
> kube-systembootstrap-token-cb0b7f
> bootstrap.kubernetes.io/token <http://bootstrap.kubernetes.io/token> 
> 6  8h
> kubernetes-dashboard   kubernetes-dashboard-certsOpaque   
>  0  8h
> kubernetes-dashboard   kubernetes-dashboard-csrf Opaque   
>  1  8h
> kubernetes-dashboard   kubernetes-dashboard-key-holder   Opaque   
>  2  8h
> kubernetes-dashboard   kubernetes-dashboard-token
> kubernetes.io/service-account-token 
> <http://kubernetes.io/service-account-token>  3  8h
> cloud@Kspot-App-control-18dd041902a:~$
>
> I am using v1.28.4 k8s version ISO for the cluster, storage offering and 
> network is in shared mode and using 1 node cluster without HA.
>
> Thanks and Regards,
> Bharat Saini
>
>
>
> From: Vivek Kumar  <mailto:vivek.ku...@indiqus.com.INVALID>>
> Date: Thursday, 22 February 2024 at 11:39 PM
> To: users@cloudstack.apache.org <mailto:users@cloudstack.apache.org> 
> mailto:users@cloudstack.apache.org>>
> Subject: Re: CKS Storage Provisioner Info
>
> EXTERNAL EMAIL: Please verify the sender email address before taking any 
> action, replying, clicking any link or opening any attachment.
>
>
> Hello Bharat,
>
> 1- When you deploy a cluster, an additional user is created under your 
> cloudstack account - i.e -kubeadmin,  and apikey and secret key 
> of this kubeadmin user is pushed to the cluster.
>
> This you can find -
>
> root@18dc14302a2:~# kubectl get secret cloudstack-secret -n kube-system
> NAMETYPE DATA   AGE
> cloudstack-secret   Opaque   1  3d5h
>
> To check the more details for this secret -
>
> root@18dc14302a2:~# kubectl get secret cloudstack-secret -n kube-system -o 
> jsonpath='{.data.*}' | base64 -d
> [Global]
> api-url = http://172.27.2.53:8080/client/api
> api-key = 
> ex0HfJJt7YQES4n5dsD3AEL-gr0n__JbfRvfK6cyUi5dbdPx7hyOckJ_enInYOyRewI0IR772KyNY8Sjh0TOdg
> secret-key = 
> IEHR45EK8GHkNo1G5t7eZSw5MARfZcYUvYXR1mR_vn2vv3b_-nQYFt_A_xZWRc4udtPQPKWjWW8kvTnSccAglA
>
>
> Now, you can see the API URL, so this URL endpoint must be reachable from 
> your cluster in order to provision PVC. This URL you can put in the global 
> setting - (endpoint.url)
>
> So I am assuming this endpoint URL is reachable from your cluster -  you 
> don’t need to define anything in the cloud-config and secret - because secret 
> is already created and pushed from cloudstack  

Re: CKS Storage Provisioner Info

[Vivek Kumar]

Hello Bharat, 

Then you will have to deploy the cloudstack-kubernetes-provider, however after 
4.16, it’s automatically deployed, Follow the instruction in the link - 
https://github.com/apache/cloudstack-kubernetes-provider


1- Create a file called - cloud-config and put the below information - ( you 
can create an user under your account and provide it’s apikey and secret key )


[Global]
api-url = 
api-key = 
secret-key = 


2- kubectl -n kube-system create secret generic cloudstack-secret 
--from-file=cloud-config
3- then deploy the controller - 

You can then use the provided example deployment.yaml 
<https://github.com/apache/cloudstack-kubernetes-provider/blob/main/deployment.yaml>
 to deploy the controller:

kubectl apply -f deployment.yaml




Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies

vivek.ku...@indiqus.com <mailto:vivek.ku...@indiqus.com>
www.indiqus.com <https://www.indiqus.com/>




> On 23-Feb-2024, at 12:08 AM, Bharat Bhushan Saini 
>  wrote:
> 
> Hi Vivek,
>  
> I am glad and thankful to you for sharing the information, for the 
> configuration of CSI driver.
>  
> But I didn’t have cloudstack-secret in my cluster, sharing the details below
>  
> cloud@Kspot-App-control-18dd041902a:~$ kubectl get secret cloudstack-secret 
> -n kube-system
> Error from server (NotFound): secrets "cloudstack-secret" not found
> cloud@Kspot-App-control-18dd041902a:~$ kubectl get secret -A -n kube-system
> NAMESPACE  NAME  TYPE 
>  DATA   AGE
> kloudspot  dockerregistrykey 
> kubernetes.io/dockerconfigjson <http://kubernetes.io/dockerconfigjson>
> 1  8h
> kube-systembootstrap-token-cb0b7f
> bootstrap.kubernetes.io/token <http://bootstrap.kubernetes.io/token> 
> 6  8h
> kubernetes-dashboard   kubernetes-dashboard-certsOpaque   
>  0  8h
> kubernetes-dashboard   kubernetes-dashboard-csrf Opaque   
>  1  8h
> kubernetes-dashboard   kubernetes-dashboard-key-holder   Opaque   
>  2  8h
> kubernetes-dashboard   kubernetes-dashboard-token
> kubernetes.io/service-account-token 
> <http://kubernetes.io/service-account-token>  3  8h
> cloud@Kspot-App-control-18dd041902a:~$ 
>  
> I am using v1.28.4 k8s version ISO for the cluster, storage offering and 
> network is in shared mode and using 1 node cluster without HA.
>  
> Thanks and Regards,
> Bharat Saini
>  
> 
>  
> From: Vivek Kumar  <mailto:vivek.ku...@indiqus.com.INVALID>>
> Date: Thursday, 22 February 2024 at 11:39 PM
> To: users@cloudstack.apache.org <mailto:users@cloudstack.apache.org> 
> mailto:users@cloudstack.apache.org>>
> Subject: Re: CKS Storage Provisioner Info
> 
> EXTERNAL EMAIL: Please verify the sender email address before taking any 
> action, replying, clicking any link or opening any attachment.
> 
> 
> Hello Bharat,
> 
> 1- When you deploy a cluster, an additional user is created under your 
> cloudstack account - i.e -kubeadmin,  and apikey and secret key 
> of this kubeadmin user is pushed to the cluster.
> 
> This you can find -
> 
> root@18dc14302a2:~# kubectl get secret cloudstack-secret -n kube-system
> NAMETYPE DATA   AGE
> cloudstack-secret   Opaque   1  3d5h
> 
> To check the more details for this secret -
> 
> root@18dc14302a2:~# kubectl get secret cloudstack-secret -n kube-system -o 
> jsonpath='{.data.*}' | base64 -d
> [Global]
> api-url = http://172.27.2.53:8080/client/api
> api-key = 
> ex0HfJJt7YQES4n5dsD3AEL-gr0n__JbfRvfK6cyUi5dbdPx7hyOckJ_enInYOyRewI0IR772KyNY8Sjh0TOdg
> secret-key = 
> IEHR45EK8GHkNo1G5t7eZSw5MARfZcYUvYXR1mR_vn2vv3b_-nQYFt_A_xZWRc4udtPQPKWjWW8kvTnSccAglA
> 
> 
> Now, you can see the API URL, so this URL endpoint must be reachable from 
> your cluster in order to provision PVC. This URL you can put in the global 
> setting - (endpoint.url)
> 
> So I am assuming this endpoint URL is reachable from your cluster -  you 
> don’t need to define anything in the cloud-config and secret - because secret 
> is already created and pushed from cloudstack  once you deploy the cluster. ( 
> From above steps you can verify ).
> 
> 2- Deploy the CSI driver - as mentioned in the Link -
> 
> kubectl apply -f 
> https://github.com/apalia/cloudstack-csi-driver/releases/latest/download/manifest.yaml
> 
> 
> 3- Now create the storage class - as mentioned in the Link as example 
> <https://github.com/apalia/cloudstack-csi-driver/blob/

Re: CKS Storage Provisioner Info

[Bharat Bhushan Saini]

Hi Vivek,

I am glad and thankful to you for sharing the information, for the 
configuration of CSI driver.


But I didn’t have cloudstack-secret in my cluster, sharing the details below


cloud@Kspot-App-control-18dd041902a:~$ kubectl get secret cloudstack-secret -n 
kube-system
Error from server (NotFound): secrets "cloudstack-secret" not found
cloud@Kspot-App-control-18dd041902a:~$ kubectl get secret -A -n kube-system
NAMESPACE  NAME  TYPE   
   DATA   AGE
kloudspot  dockerregistrykey 
kubernetes.io/dockerconfigjson1  8h
kube-systembootstrap-token-cb0b7f
bootstrap.kubernetes.io/token 6  8h
kubernetes-dashboard   kubernetes-dashboard-certsOpaque 
   0  8h
kubernetes-dashboard   kubernetes-dashboard-csrf Opaque 
   1  8h
kubernetes-dashboard   kubernetes-dashboard-key-holder   Opaque 
   2  8h
kubernetes-dashboard   kubernetes-dashboard-token
kubernetes.io/service-account-token   3  8h
cloud@Kspot-App-control-18dd041902a:~$



I am using v1.28.4 k8s version ISO for the cluster, storage offering and 
network is in shared mode and using 1 node cluster without HA.

Thanks and Regards,
Bharat Saini

[signature_1415706869]

From: Vivek Kumar 
Date: Thursday, 22 February 2024 at 11:39 PM
To: users@cloudstack.apache.org 
Subject: Re: CKS Storage Provisioner Info
EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.


Hello Bharat,

1- When you deploy a cluster, an additional user is created under your 
cloudstack account - i.e -kubeadmin,  and apikey and secret key 
of this kubeadmin user is pushed to the cluster.

This you can find -

root@18dc14302a2:~# kubectl get secret cloudstack-secret -n kube-system
NAMETYPE DATA   AGE
cloudstack-secret   Opaque   1  3d5h

To check the more details for this secret -

root@18dc14302a2:~# kubectl get secret cloudstack-secret -n kube-system -o 
jsonpath='{.data.*}' | base64 -d
[Global]
api-url = http://172.27.2.53:8080/client/api
api-key = 
ex0HfJJt7YQES4n5dsD3AEL-gr0n__JbfRvfK6cyUi5dbdPx7hyOckJ_enInYOyRewI0IR772KyNY8Sjh0TOdg
secret-key = 
IEHR45EK8GHkNo1G5t7eZSw5MARfZcYUvYXR1mR_vn2vv3b_-nQYFt_A_xZWRc4udtPQPKWjWW8kvTnSccAglA


Now, you can see the API URL, so this URL endpoint must be reachable from your 
cluster in order to provision PVC. This URL you can put in the global setting - 
(endpoint.url)

So I am assuming this endpoint URL is reachable from your cluster -  you don’t 
need to define anything in the cloud-config and secret - because secret is 
already created and pushed from cloudstack  once you deploy the cluster. ( From 
above steps you can verify ).

2- Deploy the CSI driver - as mentioned in the Link -

kubectl apply -f 
https://github.com/apalia/cloudstack-csi-driver/releases/latest/download/manifest.yaml


3- Now create the storage class - as mentioned in the Link as example 
<https://github.com/apalia/cloudstack-csi-driver/blob/master/examples/k8s/0-storageclass.yaml>


Create a file i.e storage-class.yml and paste below information - ( Please 
mention the disk offering ID, it has to be a CUSTOM )

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: cloudstack-custom
provisioner: csi.cloudstack.apache.org
reclaimPolicy: Delete
volumeBindingMode: WaitForFirstConsumer
allowVolumeExpansion: false
parameters:
  csi.cloudstack.apache.org/disk-offering-id: 


kubectl apply -f storage-class.yml

root@18dc14302a2:~# kubectl get storageclass
NAMEPROVISIONER RECLAIMPOLICY   
VOLUMEBINDINGMODE  ALLOWVOLUMEEXPANSION   AGE
cloudstack-custom   csi.cloudstack.apache.org   Delete  
WaitForFirstConsumer   false  3d5h


4- Now you can test by creating a PVC and POD - ( Examples are already there in 
the link - 
https://github.com/apalia/cloudstack-csi-driver/tree/master/examples/k8s )



Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies

vivek.ku...@indiqus.com <mailto:vivek.ku...@indiqus.com>
www.indiqus.com<http://www.indiqus.com> <https://www.indiqus.com/>




> On 22-Feb-2024, at 8:11 PM, Bharat Bhushan Saini 
>  wrote:
>
> Hi Vivek/Kiran,
>
> The cluster is deployed in the Root domain. But I am unable to locate 
> cloud-config file configuration after creating a domain user and pls correct 
> me that the cloud-config file have to be configured in controller node.
>
> Thanks and Regards,
> Bharat Saini
>
>
>
> From: Vivek Kumar  <mailto:vivek.ku...@indiqus.com.INVALID>>
> Date: Thursday, 22 February 2024 at 5:51 PM
> To: users@cloudstack.apache.org <mailto:users@cloudstack.apache.org> 
> mailto:

Re: CKS Storage Provisioner Info

[Vivek Kumar]

Hello Bharat,

1- When you deploy a cluster, an additional user is created under your 
cloudstack account - i.e -kubeadmin,  and apikey and secret key 
of this kubeadmin user is pushed to the cluster.

This you can find -

root@18dc14302a2:~# kubectl get secret cloudstack-secret -n kube-system 
NAMETYPE DATA   AGE
cloudstack-secret   Opaque   1  3d5h

To check the more details for this secret - 

root@18dc14302a2:~# kubectl get secret cloudstack-secret -n kube-system -o 
jsonpath='{.data.*}' | base64 -d
[Global]
api-url = http://172.27.2.53:8080/client/api
api-key = 
ex0HfJJt7YQES4n5dsD3AEL-gr0n__JbfRvfK6cyUi5dbdPx7hyOckJ_enInYOyRewI0IR772KyNY8Sjh0TOdg
secret-key = 
IEHR45EK8GHkNo1G5t7eZSw5MARfZcYUvYXR1mR_vn2vv3b_-nQYFt_A_xZWRc4udtPQPKWjWW8kvTnSccAglA


Now, you can see the API URL, so this URL endpoint must be reachable from your 
cluster in order to provision PVC. This URL you can put in the global setting - 
(endpoint.url)

So I am assuming this endpoint URL is reachable from your cluster -  you don’t 
need to define anything in the cloud-config and secret - because secret is 
already created and pushed from cloudstack  once you deploy the cluster. ( From 
above steps you can verify ).

2- Deploy the CSI driver - as mentioned in the Link - 

kubectl apply -f 
https://github.com/apalia/cloudstack-csi-driver/releases/latest/download/manifest.yaml


3- Now create the storage class - as mentioned in the Link as example 
<https://github.com/apalia/cloudstack-csi-driver/blob/master/examples/k8s/0-storageclass.yaml>


Create a file i.e storage-class.yml and paste below information - ( Please 
mention the disk offering ID, it has to be a CUSTOM ) 

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: cloudstack-custom
provisioner: csi.cloudstack.apache.org
reclaimPolicy: Delete
volumeBindingMode: WaitForFirstConsumer
allowVolumeExpansion: false
parameters:
  csi.cloudstack.apache.org/disk-offering-id: 


kubectl apply -f storage-class.yml

root@18dc14302a2:~# kubectl get storageclass
NAMEPROVISIONER RECLAIMPOLICY   
VOLUMEBINDINGMODE  ALLOWVOLUMEEXPANSION   AGE
cloudstack-custom   csi.cloudstack.apache.org   Delete  
WaitForFirstConsumer   false  3d5h


4- Now you can test by creating a PVC and POD - ( Examples are already there in 
the link - 
https://github.com/apalia/cloudstack-csi-driver/tree/master/examples/k8s )



Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies

vivek.ku...@indiqus.com <mailto:vivek.ku...@indiqus.com>
www.indiqus.com <https://www.indiqus.com/>




> On 22-Feb-2024, at 8:11 PM, Bharat Bhushan Saini 
>  wrote:
> 
> Hi Vivek/Kiran,
>  
> The cluster is deployed in the Root domain. But I am unable to locate 
> cloud-config file configuration after creating a domain user and pls correct 
> me that the cloud-config file have to be configured in controller node.
>  
> Thanks and Regards,
> Bharat Saini
>  
> 
>  
> From: Vivek Kumar  <mailto:vivek.ku...@indiqus.com.INVALID>>
> Date: Thursday, 22 February 2024 at 5:51 PM
> To: users@cloudstack.apache.org <mailto:users@cloudstack.apache.org> 
> mailto:users@cloudstack.apache.org>>
> Subject: Re: CKS Storage Provisioner Info
> 
> EXTERNAL EMAIL: Please verify the sender email address before taking any 
> action, replying, clicking any link or opening any attachment.
> 
> 
> Hello Bharat,
> 
> Yes, the link provided by Kiran works well for PVC but only one caveat that 
> it only works if your cluster is deployed under ROOT domain.
> 
> 
> 
> Vivek Kumar
> Sr. Manager - Cloud & DevOps
> TechOps | Indiqus Technologies
> 
> vivek.ku...@indiqus.com <mailto:vivek.ku...@indiqus.com> 
> <mailto:vivek.ku...@indiqus.com>
> www.indiqus.com <http://www.indiqus.com/> <https://www.indiqus.com/>
> 
> 
> 
> 
> > On 22-Feb-2024, at 5:21 PM, Kiran Chavala  > <mailto:kiran.chav...@shapeblue.com>> wrote:
> >
> > Hi Bharat
> >
> > You can try the following CSI driver
> >
> > https://github.com/Leaseweb/cloudstack-csi-driver
> >
> >
> > Regards
> > Kiran
> >
> > From: Bharat Bhushan Saini  > <mailto:bharat.sa...@kloudspot.com.INVALID>>
> > Date: Thursday, 22 February 2024 at 5:14 PM
> > To: users@cloudstack.apache.org <mailto:users@cloudstack.apache.org> 
> > mailto:users@cloudstack.apache.org>>
> > Subject: CKS Storage Provisioner Info
> > Hi All,
> >
> > As working with the CKS service I had a query regarding with the K8s 
> > storage provisioner.
> > Which provisioner I can use for the shared and unshared PVC in the CKS 
> > service.
> > Please su

Re: CKS Storage Provisioner Info

[Bharat Bhushan Saini]

Hi Vivek/Kiran,

The cluster is deployed in the Root domain. But I am unable to locate 
cloud-config file configuration after creating a domain user and pls correct me 
that the cloud-config file have to be configured in controller node.

Thanks and Regards,
Bharat Saini

[signature_1127082807]

From: Vivek Kumar 
Date: Thursday, 22 February 2024 at 5:51 PM
To: users@cloudstack.apache.org 
Subject: Re: CKS Storage Provisioner Info
EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.


Hello Bharat,

Yes, the link provided by Kiran works well for PVC but only one caveat that it 
only works if your cluster is deployed under ROOT domain.



Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies

vivek.ku...@indiqus.com <mailto:vivek.ku...@indiqus.com>
www.indiqus.com<http://www.indiqus.com> <https://www.indiqus.com/>




> On 22-Feb-2024, at 5:21 PM, Kiran Chavala  wrote:
>
> Hi Bharat
>
> You can try the following CSI driver
>
> https://github.com/Leaseweb/cloudstack-csi-driver
> https://github.com/apalia/cloudstack-csi-driver
>
> Regards
> Kiran
>
> From: Bharat Bhushan Saini 
> Date: Thursday, 22 February 2024 at 5:14 PM
> To: users@cloudstack.apache.org 
> Subject: CKS Storage Provisioner Info
> Hi All,
>
> As working with the CKS service I had a query regarding with the K8s storage 
> provisioner.
> Which provisioner I can use for the shared and unshared PVC in the CKS 
> service.
> Please support in this, it will be great help for me.
>
> Thanks and Regards,
> Bharat Saini
>
> [signature_1218208545]
>
> --- Disclaimer: --
> This message and its contents are intended solely for the designated 
> addressee and are proprietary to Kloudspot. The information in this email is 
> meant exclusively for Kloudspot business use. Any use by individuals other 
> than the addressee constitutes misuse and an infringement of Kloudspot's 
> proprietary rights. If you are not the intended recipient, please return this 
> email to the sender. Kloudspot cannot guarantee the security or error-free 
> transmission of e-mail communications. Information could be intercepted, 
> corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. 
> Therefore, Kloudspot shall not be liable for any issues arising from the 
> transmission of this email.
>
>
>


--
This message is intended only for the use of the individual or entity to
which it is addressed and may contain confidential and/or privileged
information. If you are not the intended recipient, please delete the
original message and any copy of it from your computer system. You are
hereby notified that any dissemination, distribution or copying of this
communication is strictly prohibited unless proper authorization has been
obtained for such action. If you have received this communication in error,
please notify the sender immediately. Although IndiQus attempts to sweep
e-mail and attachments for viruses, it does not guarantee that both are
virus-free and accepts no liability for any damage sustained as a result of
viruses.

--- Disclaimer: --
This message and its contents are intended solely for the designated addressee 
and are proprietary to Kloudspot. The information in this email is meant 
exclusively for Kloudspot business use. Any use by individuals other than the 
addressee constitutes misuse and an infringement of Kloudspot's proprietary 
rights. If you are not the intended recipient, please return this email to the 
sender. Kloudspot cannot guarantee the security or error-free transmission of 
e-mail communications. Information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or contain viruses. Therefore, Kloudspot 
shall not be liable for any issues arising from the transmission of this email.

Re: CKS Storage Provisioner Info

[Vivek Kumar]

Hello Bharat,

Yes, the link provided by Kiran works well for PVC but only one caveat that it 
only works if your cluster is deployed under ROOT domain.



Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies

vivek.ku...@indiqus.com <mailto:vivek.ku...@indiqus.com>
www.indiqus.com <https://www.indiqus.com/>




> On 22-Feb-2024, at 5:21 PM, Kiran Chavala  wrote:
> 
> Hi Bharat
> 
> You can try the following CSI driver
> 
> https://github.com/Leaseweb/cloudstack-csi-driver
> https://github.com/apalia/cloudstack-csi-driver
> 
> Regards
> Kiran
> 
> From: Bharat Bhushan Saini 
> Date: Thursday, 22 February 2024 at 5:14 PM
> To: users@cloudstack.apache.org 
> Subject: CKS Storage Provisioner Info
> Hi All,
> 
> As working with the CKS service I had a query regarding with the K8s storage 
> provisioner.
> Which provisioner I can use for the shared and unshared PVC in the CKS 
> service.
> Please support in this, it will be great help for me.
> 
> Thanks and Regards,
> Bharat Saini
> 
> [signature_1218208545]
> 
> --- Disclaimer: --
> This message and its contents are intended solely for the designated 
> addressee and are proprietary to Kloudspot. The information in this email is 
> meant exclusively for Kloudspot business use. Any use by individuals other 
> than the addressee constitutes misuse and an infringement of Kloudspot's 
> proprietary rights. If you are not the intended recipient, please return this 
> email to the sender. Kloudspot cannot guarantee the security or error-free 
> transmission of e-mail communications. Information could be intercepted, 
> corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. 
> Therefore, Kloudspot shall not be liable for any issues arising from the 
> transmission of this email.
> 
> 
> 


-- 
This message is intended only for the use of the individual or entity to 
which it is addressed and may contain confidential and/or privileged 
information. If you are not the intended recipient, please delete the 
original message and any copy of it from your computer system. You are 
hereby notified that any dissemination, distribution or copying of this 
communication is strictly prohibited unless proper authorization has been 
obtained for such action. If you have received this communication in error, 
please notify the sender immediately. Although IndiQus attempts to sweep 
e-mail and attachments for viruses, it does not guarantee that both are 
virus-free and accepts no liability for any damage sustained as a result of 
viruses.

Re: CKS Storage Provisioner Info

[Kiran Chavala]

Hi Bharat

You can try the following CSI driver

https://github.com/Leaseweb/cloudstack-csi-driver
https://github.com/apalia/cloudstack-csi-driver

Regards
Kiran

From: Bharat Bhushan Saini 
Date: Thursday, 22 February 2024 at 5:14 PM
To: users@cloudstack.apache.org 
Subject: CKS Storage Provisioner Info
Hi All,

As working with the CKS service I had a query regarding with the K8s storage 
provisioner.
Which provisioner I can use for the shared and unshared PVC in the CKS service.
Please support in this, it will be great help for me.

Thanks and Regards,
Bharat Saini

[signature_1218208545]

--- Disclaimer: --
This message and its contents are intended solely for the designated addressee 
and are proprietary to Kloudspot. The information in this email is meant 
exclusively for Kloudspot business use. Any use by individuals other than the 
addressee constitutes misuse and an infringement of Kloudspot's proprietary 
rights. If you are not the intended recipient, please return this email to the 
sender. Kloudspot cannot guarantee the security or error-free transmission of 
e-mail communications. Information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or contain viruses. Therefore, Kloudspot 
shall not be liable for any issues arising from the transmission of this email.

 

CKS Storage Provisioner Info

[Bharat Bhushan Saini]

Hi All,

As working with the CKS service I had a query regarding with the K8s storage 
provisioner.
Which provisioner I can use for the shared and unshared PVC in the CKS service.
Please support in this, it will be great help for me.

Thanks and Regards,
Bharat Saini

[signature_1218208545]

--- Disclaimer: --
This message and its contents are intended solely for the designated addressee 
and are proprietary to Kloudspot. The information in this email is meant 
exclusively for Kloudspot business use. Any use by individuals other than the 
addressee constitutes misuse and an infringement of Kloudspot's proprietary 
rights. If you are not the intended recipient, please return this email to the 
sender. Kloudspot cannot guarantee the security or error-free transmission of 
e-mail communications. Information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or contain viruses. Therefore, Kloudspot 
shall not be liable for any issues arising from the transmission of this email.