I deployed charmed-openstack 2023.1 [1] with juju 3.1 and added further services like octavia and designate. This works fine, as far as I can evaluate.
On top of it, I try to deploy charmed-kubernetes with openstack-integrator [2] and juju 3.3. The deployment settles well and loadbalancing pod-service and api-service works fine, so deployment and exposure of the hello-world problem works.
$kubectl describe pvc testclaim
Name: testclaim
Namespace: default
StorageClass: cdk-cinder
Status: Pending
Volume:
Labels: <none>
Annotations: volume.beta.kubernetes.io/storage-provisioner: cinder.csi.openstack.org volume.kubernetes.io/storage-provisioner: cinder.csi.openstack.org
Finalizers: [kubernetes.io/pvc-protection]
Capacity:
Access Modes:
VolumeMode: Filesystem
Used By: <none>
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal ExternalProvisioning 5s (x8 over 90s) persistentvolume-controller Waiting for a volume to be created either by the external provisioner 'cinder.csi.openstack.org' or manually by the system administrator. If volume creation is delayed, please verify that the provisioner is running and correctly registered.
unit-kubernetes-control-plane-1: 18:13:32 ERROR unit.kubernetes-control-plane/1.juju-log Unable to find implementation for relation: requires of external_cloud_provider
From there I tested different scenarios. Different juju (2.9) or kubernetes (1.26,1.27) releases or added cinder-csi charm, but the pending state of PVC stayed consistent. I noticed that the command '$kubectl get csidriver' does not return a csidriver with cdk-charm, but does with cinder-csi charm.
Managing storage from juju storage-pool cinder and usage of other charms on the other hand works fine.
Hello,
I deployed charmed-openstack 2023.1 [1] with juju 3.1 and added further services like octavia and designate. This works fine, as far as I can evaluate.
On top of it, I try to deploy charmed-kubernetes with openstack- integrator [2] and juju 3.3. The deployment settles well and loadbalancing pod-service and api-service works fine, so deployment and exposure of the hello-world problem works.
------- ------- ------- ------- ------- ------- ------- -----
Not working is the creation of a persistentVolum eClaim.
$kubectl create -f - <<EOY eClaim
kind: PersistentVolum
apiVersion: v1
metadata:
name: testclaim
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 1Gi
storageClassName: cdk-cinder
EOY
$kubectl describe sc cdk-cinder workload- storage= true,kubectl. kubernetes. io/last- applied- configuration= {"apiVersion" :"storage. k8s.io/ v1","kind" :"StorageClass" ,"metadata" :{"annotations" :{"juju. io/workload- storage" :"true" },"labels" :{"cdk- addons" :"true" },"name" :"cdk-cinder" },"parameters" :{"availability ":"nova" },"provisioner" :"cinder. csi.openstack. org"}
Name: cdk-cinder
IsDefaultClass: No
Annotations: juju.io/
Provisioner: cinder. csi.openstack. org nsion: <unset>
Parameters: availability=nova
AllowVolumeExpa
MountOptions: <none>
ReclaimPolicy: Delete
VolumeBindingMode: Immediate
Events: <none>
------- ------- ------- ------- ------- ------- ------- -----
The creation of this testclaim stucks pending:
$kubectl describe pvc testclaim beta.kubernetes .io/storage- provisioner: cinder. csi.openstack. org
volume. kubernetes. io/storage- provisioner: cinder. csi.openstack. org io/pvc- protection] oning 5s (x8 over 90s) persistentvolum e-controller Waiting for a volume to be created either by the external provisioner 'cinder. csi.openstack. org' or manually by the system administrator. If volume creation is delayed, please verify that the provisioner is running and correctly registered.
Name: testclaim
Namespace: default
StorageClass: cdk-cinder
Status: Pending
Volume:
Labels: <none>
Annotations: volume.
Finalizers: [kubernetes.
Capacity:
Access Modes:
VolumeMode: Filesystem
Used By: <none>
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal ExternalProvisi
------- ------- ------- ------- ------- ------- ------- -----
An related Error in the debug-log seems to be:
unit-kubernetes -control- plane-1: 18:13:32 ERROR unit.kubernetes -control- plane/1. juju-log Unable to find implementation for relation: requires of external_ cloud_provider
------- ------- ------- ------- ------- ------- ------- -----
From there I tested different scenarios. Different juju (2.9) or kubernetes (1.26,1.27) releases or added cinder-csi charm, but the pending state of PVC stayed consistent. I noticed that the command '$kubectl get csidriver' does not return a csidriver with cdk-charm, but does with cinder-csi charm.
Managing storage from juju storage-pool cinder and usage of other charms on the other hand works fine.
Best D.
[1] https:/ /docs.openstack .org/project- deploy- guide/charm- deployment- guide/2023. 1/configure- openstack. html /ubuntu. com/kubernetes/ docs/openstack- integration
[2] https:/