release: v1.0.1 — enable kube and redis features for Linux builds#2
Merged
Conversation
Linux release binaries and OCI images now ship with kube + redis features built in, so ghcr.io/a3s-lab/gateway can be used directly as a Kubernetes Ingress Controller without rebuilding.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
--features kube,redisso ghcr.io images ship with Kubernetes Ingress Controller and Redis-backed rate limiting compiled in.Background
Deploying
ghcr.io/a3s-lab/gateway:1.0.0to a Kubernetes cluster with aproviders.kubernetesconfig block emits:Previously the release workflow ran
cargo build --releasewithout features, so the kube provider's optionalkubeandk8s-openapideps were never linked into the published binary.Changes
.github/workflows/release.yml: pass--features kube,redistocargo build/cross build/cargo zigbuildfor Linux targets only. macOS targets keep default features.CHANGELOG.md: add v1.0.1 section documenting the fix.Cargo.toml/Cargo.lock: bump version 1.0.0 → 1.0.1.Test plan
cargo check -p a3s-gateway --features kube,redispassesv1.0.1will trigger the release workflow once this is mergeddocker run --rm ghcr.io/a3s-lab/gateway:1.0.1-amd64 --versionand confirm no "kube feature not enabled" warning when given a kubernetes provider config🤖 Generated with Claude Code