chore(deps): update dependency kubernetes-sigs/aws-alb-ingress-controller to v2.14.0 #1000
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
renovate
bot
added
dependencies
renovate
bot
force-pushed
the
renovate/kubernetes-sigs-aws-alb-ingress-controller-2.x
branch
from
4f645a7 to
b089381
Compare
🚀 Preview Deployment Ready!Your pull request has been built and is ready for preview deployment. Container Images Built
Quick Deploy with Helm# Add the wrongsecrets helm repository
helm repo add wrongsecrets https://owasp.org/wrongsecrets-ctf-party
helm repo update
# Deploy with preview images
helm install my-preview wrongsecrets/wrongsecrets-ctf-party \
--set balancer.repository=ghcr.io/OWASP/wrongsecrets-balancer \
--set balancer.tag=pr-1000 \
--set wrongsecretsCleanup.repository=ghcr.io/OWASP/cleaner \
--set wrongsecretsCleanup.tag=pr-1000 \
--set imagePullPolicy=Always
# Port forward to access locally
kubectl port-forward service/wrongsecrets-balancer 3000:3000Deploy with Custom ValuesClick to see preview-values.yamlbalancer:
repository: ghcr.io/OWASP/wrongsecrets-balancer
tag: pr-1000
wrongsecretsCleanup:
repository: ghcr.io/OWASP/cleaner
tag: pr-1000
# Preview configuration
ingress:
enabled: true
hosts:
- host: >-
preview-pr-1000.wrongsecrets.local
paths:
- "/"# Save the above values to preview-values.yaml, then:
helm install my-preview wrongsecrets/wrongsecrets-ctf-party \
-f preview-values.yamlDeploy with Local Build Scripts# Clone this PR
git fetch origin pull/1000/head:pr-1000
git checkout pr-1000
# Use the existing deployment script with custom images
./build-and-deploy.shTest the Changes
Container RegistryThe preview images are available at:
This preview was automatically generated for PR #1000 |
commjoen
deleted the
renovate/kubernetes-sigs-aws-alb-ingress-controller-2.x
branch
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.
This PR contains the following updates:
v2.13.4->v2.14.0Release Notes
kubernetes-sigs/aws-alb-ingress-controller (kubernetes-sigs/aws-alb-ingress-controller)
v2.14.0Compare Source
Beta Release: Gateway API Layer 7 (L7) Routing for AWS Load Balancer Controller
We are excited to announce the Beta release of Layer 7 (L7) routing support for the Kubernetes Gateway API within the AWS Load Balancer Controller (LBC)!🥳🥳🥳 This highly anticipated feature allows you to provision and manage AWS Application Load Balancers (ALBs) for HTTP, HTTPS, and GRPC traffic directly from your Kubernetes clusters using the extensible Gateway API. Please refer to L7 Gateway API Documentation to learn more.
This beta release focuses on Gateway API features with comprehensive status reporting, advanced authentication, and stability improvements. While we encourage you to test these features extensively in your development environments, please be aware that this is a Beta release and is not yet production-ready. We are actively gathering feedback to finalize stability for official production use. This Beta status applies only to the new Gateway API features. All existing controller functionality for standard Ingress, Service and TargetGroupBinding resources remains stable and is safe for production workflows. Please restrict use of the new Gateway API features to testing and development environments.
📚 Quick Links
v2.14.0 (requires Kubernetes 1.22+)
Image: public.ecr.aws/eks/aws-load-balancer-controller:v2.14.0
Documentation
Thanks to all our contributors!💜💜💜
EndpointSlices Now Default
--enable-endpoint-slices=falseif issues occurCRD Updates
kubectl apply -k "github.com/aws/eks-charts/stable/aws-load-balancer-controller/crds?ref=master"🚀 What's New in Ingress, Services and TargetGroupBinding
Enhanced Defaulting Flag
EnhancedDefaultBehaviorflag for better annotation lifecycle managementCRD Naming Fix
ingressclassparams→ingressclassparamConfiguration Improvements
🚀 What's New in Gateway API
Status Update & Observability
aws_target_group_infometric for CloudWatch integrationAdvanced Authentication
Enhanced Routing
Traffic Management
Infrastructure
🔧 Enhancements and Fixes
Performance & Reliability
Bug Fixes
Documentation & Testing
🌟 Complete Change Log
wafv2AclArnfield to IngressClassParams by @mikutas in kubernetes-sigs/aws-load-balancer-controller#3961🥳 New Contributors
Full Changelog: kubernetes-sigs/aws-load-balancer-controller@v2.13.4...v2.14.0
🎯 Provide Your Feedback!
As this is a beta release, your feedback is invaluable! We encourage you to:
Your active participation will help us refine this feature for its General Availability release.
Configuration
📅 Schedule: Branch creation - On day 1 and 15 of the month ( * * 1,15 * * ) (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.