Release v2.3.0: ARM64 support + configurable SSL enforcement #699
Conversation
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
Signed-off-by: Aaron Lippold <lippold@gmail.com>
…able ## Changes ### Production Configuration - Make config.force_ssl configurable via FORCE_SSL env var (defaults to true) - Make config.assume_ssl respect FORCE_SSL setting (DRY approach) - Both settings now controlled by single environment variable ### Documentation - Update ENVIRONMENT_VARIABLES.md with FORCE_SSL usage - Update .env.production.example with FORCE_SSL documentation - Update docs/getting-started/environment-variables.md with use cases ## Use Cases **Local/Dev Kubernetes (no ingress):** - Set FORCE_SSL=false - Allows HTTP access without SSL redirects - Suitable for Kind, Minikube, development clusters **Production (with ingress + TLS):** - Set FORCE_SSL=true (default) - Enforces HTTPS, secure cookies, HSTS headers - Ingress handles SSL termination ## Benefits - Helm chart compatibility for local development - Maintains security defaults for production - Single configuration point for SSL behavior - Backward compatible (defaults to true) Authored by: Aaron Lippold<lippold@gmail.com>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
This release adds ARM64/Apple Silicon support and makes SSL enforcement configurable for flexible Kubernetes deployments.
Changes
Multi-Platform Docker Builds
platforms: linux/amd64,linux/arm64in push-to-docker.ymlConfigurable SSL Enforcement
FORCE_SSLenvironment variable supportconfig.force_sslrespectFORCE_SSLsettingconfig.assume_sslrespectFORCE_SSLsetting (DRY approach)Use Cases
Local/Development Kubernetes:
Production (with Ingress + TLS):
FORCE_SSL=true # DefaultTesting
Compatibility
Documentation Updated
Authored by: Aaron Lippoldlippold@gmail.com