K8s deployment failure: no matches for kind "Deployment"

[natpowning]

Problem

Deployment of Signal K server using the Kubernetes manifest fails.

The severity is minor as only K8s users are impacted and it's easy to workaround.

Steps to Reproduce

Environment:

• Ubuntu 22.04.5 LTS
• MicroK8s v1.31.5 revision 7672
• kubectl client v1.31.5

Apply manifest: kubectl apply -f kubernetes/signalk-deployment.yaml

Inspect deployments for signalk: kubctl get pods | grep signalk

Expected Result

Messages confirming resources were created including signalk deployment, and signalk present in deployments list.

Result:

The error resource mapping not found is returned by kubectl and no signalk deployment is present in the cluster.

service/signalk created
persistentvolumeclaim/signalkpvc created
error: resource mapping not found for name: "signalk" namespace: "default" from "kubernetes/signalk-deployment.yaml": no matches for kind "Deployment" in version "extensions/v1beta1"
ensure CRDs are installed first

Considerations

The Kubernetes manifest at kubernetes/signalk-deployment.yaml references the extensions/v1beta1 API which was deprecated in 1.16 and is no longer available. Applying this manifest against a modern cluster results in an error: no matches for kind "Deployment" in version "extensions/v1beta1"

[tkurki]

As you've probably noticed there has not been much K8s activity, but PRs are very welcome.