cloud issueshttps://gitlab.mpcdf.mpg.de/groups/mpcdf/cloud/-/issues2023-08-04T08:46:45Zhttps://gitlab.mpcdf.mpg.de/mpcdf/cloud/kubernetes/-/issues/4Kubernetes installation fails2023-08-04T08:46:45ZAdam FeketeKubernetes installation failsAlthough the orchestration happens without any problem kubernetes will not be installed because of an unsigned certificate.
More info here: https://github.com/kubernetes/website/pull/41307Although the orchestration happens without any problem kubernetes will not be installed because of an unsigned certificate.
More info here: https://github.com/kubernetes/website/pull/41307https://gitlab.mpcdf.mpg.de/mpcdf/cloud/kubernetes/-/issues/3Getting error when using the ingress controller demo2023-05-26T12:17:28ZAdam FeketeGetting error when using the ingress controller demoGetting error while trying the example deployment:
```
kubectl apply -f examples/ingress-demo.yaml
```
```
deployment.apps/ingress-demo-deployment created
service/ingress-demo-service created
Error from server (InternalError): error whe...Getting error while trying the example deployment:
```
kubectl apply -f examples/ingress-demo.yaml
```
```
deployment.apps/ingress-demo-deployment created
service/ingress-demo-service created
Error from server (InternalError): error when creating "examples/ingress-demo.yaml": Internal error occurred: failed calling webhook "validate.nginx.ingress.kubernetes.io": failed to call webhook: Post "https://ingress-nginx-controller-admission.ingress-nginx.svc:443/networking/v1/ingresses?timeout=10s": context deadline exceeded
```
We managed to use a workaround to disable the webhook using:
```
helm upgrade --install ingress-nginx ingress-nginx \
--repo https://kubernetes.github.io/ingress-nginx \
--namespace ingress-nginx --create-namespace \
--set controller.admissionWebhooks.enabled=false
```
@brian Although it fixed our error I'm not sure that this is desired for the long run....https://gitlab.mpcdf.mpg.de/mpcdf/cloud/kubernetes/-/issues/2Failing to delete an existing kubernetes stack2023-05-25T13:56:12ZAdam FeketeFailing to delete an existing kubernetes stackWe had problem to delete deployed stack using openstack. The problem that the following port cannot be removed:
`octavia-lb-vrrp-bce093d4-174c-4108-af71-02427ab75f39`
If I understand right it was created by kubernetes but we do not heave...We had problem to delete deployed stack using openstack. The problem that the following port cannot be removed:
`octavia-lb-vrrp-bce093d4-174c-4108-af71-02427ab75f39`
If I understand right it was created by kubernetes but we do not heave permission to remove it by the openstack interface.
Events log:
```
| nomad | a372b8ae-abe4-4864-bef9-890e4f10117b | 20 minutes | Delete Failed | Resource DELETE failed: Conflict: resources.k8s-subnet: Unable to complete operation on subnet f3a21723-8522-40c8-aae7-2bcd92d731e9: One or more ports have an IP allocation from this subnet. Neutron server returns request_ids: ['req-8c86c770-1d82-49c8-a8b |
|------------|---------------------------------------|-------------|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| k8s-subnet | f3a21723-8522-40c8-aae7-2bcd92d731e9 | 20 minutes | Delete Failed | Conflict: resources.k8s-subnet: Unable to complete operation on subnet f3a21723-8522-40c8-aae7-2bcd92d731e9: One or more ports have an IP allocation from this subnet. Neutron server returns request_ids: ['req-8c86c770-1d82-49c8-a8b9-00c818d2b422'] |
```
Do you have any suggestion how to progress?