Note that I am working on a new CPI and have ventured into Kubernetes via Kubo. I do not think this is explicitly related to the CPI, per se, but is likely related to the IaaS (Libvirt) it supports.
What you expected to happen:
MySQL to be installed and run successfully.
However, I see this instead:
$ kubectl describe pod kissing-elk-mysql-7d5cffc696-hbt5t
<snip>
Warning FailedScheduling 4m9s (x79 over 114m) default-scheduler pod has unbound immediate PersistentVolumeClaims (repeated 3 times)
How to reproduce it (as minimally and precisely as possible):
New CPI, new cloud provider/IaaS likely the culprit. But uncertain how to provide. Assuming this is NOT releated to Kubo, I would appreciate tips on how to proceed. It's possible a new storage provider for Kubernetes would need to be written. :man_shrugging:
Environment:
Deployment Info (bosh -d <deployment> deployment):
$ bosh -d cfcr deployment
Using environment '192.168.123.7' as client 'admin'
- Environment Info (`bosh -e <environment> environment`):
$ bosh environment
Using environment '192.168.123.7' as client 'admin'
Name libvirt
UUID 37f2c768-9218-482a-96b5-2321865ac1b8
Version 270.5.0 (00000000)
Director Stemcell ubuntu-xenial/456.12
CPI libvirt_cpi
Features compiled_package_cache: disabled
config_server: enabled
local_dns: enabled
power_dns: disabled
snapshots: disabled
User admin
What happened:
Tried installing
stable/mysqlviahelm.Note that I am working on a new CPI and have ventured into Kubernetes via Kubo. I do not think this is explicitly related to the CPI, per se, but is likely related to the IaaS (Libvirt) it supports.
What you expected to happen:
MySQL to be installed and run successfully.
However, I see this instead:
How to reproduce it (as minimally and precisely as possible):
Might be Libvirt-centric. My writeup is at: https://github.com/a2geek/libvirt-bosh-cpi/blob/master/docs/KUBO.md
Anything else we need to know?:
New CPI, new cloud provider/IaaS likely the culprit. But uncertain how to provide. Assuming this is NOT releated to Kubo, I would appreciate tips on how to proceed. It's possible a new storage provider for Kubernetes would need to be written. :man_shrugging:
Environment:
bosh -d <deployment> deployment):Name Release(s) Stemcell(s) Config(s) Team(s)
cfcr bosh-dns/1.12.0 bosh-openstack-kvm-ubuntu-xenial-go_agent/315.41 1 cloud/default -
bpm/1.0.4 2 runtime/dns
cfcr-etcd/1.11.1
docker/35.2.1
kubo/0.34.0
1 deployments
Succeeded
$ bosh environment Using environment '192.168.123.7' as client 'admin'
Name libvirt
UUID 37f2c768-9218-482a-96b5-2321865ac1b8
Version 270.5.0 (00000000)
Director Stemcell ubuntu-xenial/456.12
CPI libvirt_cpi
Features compiled_package_cache: disabled
config_server: enabled
local_dns: enabled
power_dns: disabled
snapshots: disabled
User admin
Succeeded
$ kubectl version Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.3", GitCommit:"2d3c76f9091b6bec110a5e63777c332469e0cba2", GitTreeState:"clean", BuildDate:"2019-08-21T15:34:43Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.1", GitCommit:"b7394102d6ef778017f2ca4046abbaa23b88c290", GitTreeState:"clean", BuildDate:"2019-04-08T17:02:58Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"linux/amd64"}
$ virsh version Compiled against library: libvirt 4.0.0 Using library: libvirt 4.0.0 Using API: QEMU 4.0.0 Running hypervisor: QEMU 2.11.1