fix: Kubernetes deployment failure #1876
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Kubernetes deployment manifest references an API that is no longer available. Change this to the equivalent that's available in current K8s implementations along with some updates to make deploying the Signal K Server on Kubernetes clusters easier.
Validation
Manual Testing
Screenshot
Copilot Description
Documentation updates:
README.md
: Added a section pointing to new Kubernetes Quickstart instructions.kubernetes/README.md
: Created a new README with detailed instructions for deploying Signal K Server on Kubernetes, including setup, accessing the server, and uninstalling.Kubernetes manifest files:
kubernetes/signalk-deployment.yaml
: Updated the deployment manifest to useapiVersion: apps/v1
and removed unnecessary metadata fields. [1] [2] [3] [4]kubernetes/signalk-ingress.yaml
: Added a new ingress manifest for routing HTTP traffic to the Signal K Server.Related Issues