sap-archive / bosh-kubernetes-cpi-release Goto Github PK

Steps to reporduce:

• deploy a release
• bosh -d <deployment> ssh -c 'cat /etc/hosts'

The entries in /etc/hosts are not valid.

Workaround:
bosh -d <deployment> <manifest> --recreate

Disk creation failed in Minikube environment. What could be the reason?

./deployment/minikube/scripts/create-env.sh
...
...
Started deploying
  Waiting for the agent on VM '54c7a391-5c97-4a16-60e3-3e7ada55e156'... Finished (00:00:00)
  Stopping jobs on instance 'unknown/0'... Finished (00:00:00)
  Deleting VM '54c7a391-5c97-4a16-60e3-3e7ada55e156'... Finished (00:00:01)
  Creating VM for instance 'bosh/0' from stemcell 'loewenstein/bosh-stemcell-kubernetes-ubuntu-trusty-go_agent:3445.11'... Finished (00:00:02)
  Waiting for the agent on VM 'a8579f87-2140-490b-66b4-22cf2fedb966' to be ready... Finished (00:00:12)
  Creating disk... Failed (00:05:36)
Failed deploying (00:05:52)

Stopping registry... Finished (00:00:00)
Cleaning up rendered CPI jobs... Finished (00:00:00)

Deploying:
  Creating instance 'bosh/0':
    Updating instance disks:
      Updating disks:
        Deploying disk:
          Creating disk with size 10000, cloudProperties property.Map{}, instanceID a8579f87-2140-490b-66b4-22cf2fedb966:
            CPI 'create_disk' method responded with error: CmdError{"type":"Bosh::Clouds::CloudError","message":"Unknown error: 'Timeout \"Waiting for PVC to be bound\"'","ok_to_retry":false}

Exit code 1

With recent versions of Kubernetes we should no longer rely on the default service account having the necessary permissions to run the director / CPI.

• figure out necessary permissions and document how to create a service account
• provide configuration option to set a service account name
  https://github.com/SAP/bosh-kubernetes-cpi-release/blob/150139fe456dd3bf00a5fa8a9271c3ffbf9ca781/src/bosh-kubernetes-cpi/src/CPI/Kubernetes/Config.hs#L42-L45
• specify the service account in create pod call
  https://github.com/SAP/bosh-kubernetes-cpi-release/blob/150139fe456dd3bf00a5fa8a9271c3ffbf9ca781/src/bosh-kubernetes-cpi/src/CPI/Kubernetes/Action/CreateVm.hs#L141-L145

I am able to create a BOSH environment but when I am trying to deploy the example zookeeper bosh release in to gce(the same happens with minikube as well) I am getting the below authentication error

-0483-4dd5-8815-3f9052b0a96d
Task 3 | 11:48:57 | Warning: IP address not available for the link provider instance: zookeeper/99cb6f79-bef0-4a97-98bb-bff9848fc389
Task 3 | 11:48:57 | Warning: IP address not available for the link provider instance: zookeeper/f5784778-793e-46c3-bd61-7b8912633ee8
Task 3 | 11:48:57 | Warning: IP address not available for the link provider instance: zookeeper/15cea6d1-54f7-4afc-aabe-4dabac127240
Task 3 | 11:48:57 | Preparing deployment: Preparing deployment (00:00:00)
Task 3 | 11:48:57 | Preparing package compilation: Finding packages to compile (00:00:00)
Task 3 | 11:48:57 | Compiling packages: golang-1.10-linux/48c842421b6f05acf88dc6ec17f7574dade28a86
Task 3 | 11:48:57 | Compiling packages: zookeeper/43ee655b89f8a05cc472ca997e8c8186457241c1
Task 3 | 11:48:57 | Compiling packages: openjdk-8/5e72bbc5151b0248ff5925636fdd7d328f7dea20 (00:00:01)
L Error: CPI error 'Bosh::Clouds::CloudError' with message 'Unknown error: 'FailureResponse {responseStatus = Status {statusCode = 403, statusMessage = "Forbidden"}, responseContentType = application/json, responseBody = "{"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"secrets is forbidden: User \"system:serviceaccount:default:default\" cannot create secrets in the namespace \"default\": Unknown user \"system:serviceaccount:default:default\"","reason":"Forbidden","details":{"kind":"secrets"},"code":403}\n"}'' in 'create_vm' CPI method
Task 3 | 11:48:58 | Compiling packages: golang-1.10-linux/48c842421b6f05acf88dc6ec17f7574dade28a86 (00:00:01)
L Error: CPI error 'Bosh::Clouds::CloudError' with message 'Unknown error: 'FailureResponse {responseStatus = Status {statusCode = 403, statusMessage = "Forbidden"}, responseContentType = application/json, responseBody = "{"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"secrets is forbidden: User \"system:serviceaccount:default:default\" cannot create secrets in the namespace \"default\": Unknown user \"system:serviceaccount:default:default\"","reason":"Forbidden","details":{"kind":"secrets"},"code":403}\n"}'' in 'create_vm' CPI method
Task 3 | 11:48:58 | Compiling packages: zookeeper/43ee655b89f8a05cc472ca997e8c8186457241c1 (00:00:01)
L Error: CPI error 'Bosh::Clouds::CloudError' with message 'Unknown error: 'FailureResponse {responseStatus = Status {statusCode = 403, statusMessage = "Forbidden"}, responseContentType = application/json, responseBody = "{"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"secrets is forbidden: User \"system:serviceaccount:default:default\" cannot create secrets in the namespace \"default\": Unknown user \"system:serviceaccount:default:default\"","reason":"Forbidden","details":{"kind":"secrets"},"code":403}\n"}'' in 'create_vm' CPI method
Task 3 | 11:48:58 | Error: CPI error 'Bosh::Clouds::CloudError' with message 'Unknown error: 'FailureResponse {responseStatus = Status {statusCode = 403, statusMessage = "Forbidden"}, responseContentType = application/json, responseBody = "{"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"secrets is forbidden: User \"system:serviceaccount:default:default\" cannot create secrets in the namespace \"default\": Unknown user \"system:serviceaccount:default:default\"","reason":"Forbidden","details":{"kind":"secrets"},"code":403}\n"}'' in 'create_vm' CPI method

Task 3 Started Wed Sep 19 11:48:57 UTC 2018
Task 3 Finished Wed Sep 19 11:48:58 UTC 2018
Task 3 Duration 00:00:01
Task 3 error

Updating deployment:
Expected task '3' to succeed but state is 'error'

Exit code 1

Any clue what could have gone wrong here

Hi,
currently the whole documentation references the installation of CPI via the creation of new bosh director. As it is possible to have a multi CPI setup in the meanwhile, I wanted to ask what would be the best way to deploy the Kubernetes CPI to an existing director?

Thanks!

Will this perform bare metal provisioning and how does this work with Ironic or any other bare metal provisioning layer?