Currently using the example manifests results in the following error:
DEBUG:root:ConfigMap 'zelt-locustfile' created.
INFO:root:Creating Deployment 'zelt-locust-controller'...
DEBUG:kubernetes.client.rest:response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"the server could not find the requested resource","reason":"NotFound","details":{},"code":404}
ERROR:root:Failed to create Deployment 'zelt-locust-controller': Not Found
ERROR:root:Kubernetes operation failed: Not Found
To Reproduce
Steps and input files to reproduce the behavior:
Describe the bug The example manifests use the
Deployment
from a deprecated version of the Kubernetes API, e.g. https://github.com/zalando-incubator/zelt/blob/d32d3d03b6b0a35b187cabaa9f3ba6890497f673/examples/manifests/combined/deployment.yaml#L1The deprecation was introduced in Kubernetes 1.16 and minikube uses this version by default since v1.4.0.
Currently using the example manifests results in the following error:
To Reproduce Steps and input files to reproduce the behavior:
Expected behavior All example manifests should work - they should be migrated to the new API version, as advised in the Kubernetes release notes.