Skip to content

Commit 57b3a3d

Browse files
cjeradec2-bot
andauthored
🥑🤖 v1.19.0 release prep 🤖🥑 (#760)
Co-authored-by: ec2-bot 🤖 <[email protected]>
1 parent 345bb88 commit 57b3a3d

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

README.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -113,7 +113,7 @@ When using Kubernetes [Pod Security Admission](https://kubernetes.io/docs/concep
113113
You can use kubectl to directly add all of the above resources with the default configuration into your cluster.
114114

115115
```
116-
kubectl apply -f https://github.com/aws/aws-node-termination-handler/releases/download/v1.18.3/all-resources.yaml
116+
kubectl apply -f https://github.com/aws/aws-node-termination-handler/releases/download/v1.19.0/all-resources.yaml
117117
```
118118

119119
For a full list of releases and associated artifacts see our [releases page](https://github.com/aws/aws-node-termination-handler/releases).
@@ -440,7 +440,7 @@ Queue Processor needs an **SQS queue URL** to function; therefore, manifest chan
440440
Minimal Config:
441441

442442
```
443-
curl -L https://github.com/aws/aws-node-termination-handler/releases/download/v1.18.3/all-resources-queue-processor.yaml -o all-resources-queue-processor.yaml
443+
curl -L https://github.com/aws/aws-node-termination-handler/releases/download/v1.19.0/all-resources-queue-processor.yaml -o all-resources-queue-processor.yaml
444444
<open all-resources-queue-processor.yaml and update QUEUE_URL value>
445445
kubectl apply -f ./all-resources-queue-processor.yaml
446446
```

config/helm/aws-node-termination-handler/Chart.yaml

+2-2
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,8 @@ apiVersion: v2
22
name: aws-node-termination-handler
33
description: A Helm chart for the AWS Node Termination Handler.
44
type: application
5-
version: 0.20.3
6-
appVersion: 1.18.3
5+
version: 0.21.0
6+
appVersion: 1.19.0
77
kubeVersion: ">= 1.16-0"
88
keywords:
99
- aws

0 commit comments

Comments
 (0)