Set minimum version for specifying an AMI through an SSM parameter to 1.25.3

This commit is contained in:
Ciprian Hacman 2022-11-21 08:27:53 +02:00
parent cb0235d60d
commit 8b404ae6de
2 changed files with 2 additions and 2 deletions

View File

@ -8,7 +8,7 @@ For AWS, you should set the `image` field in one of the following formats:
* `ami-abcdef` - specifies an image by id directly (image id is precise, but ids vary by region)
* `<owner>/<name>` specifies an image by its owner's account ID and name properties
* `<alias>/<name>` specifies an image by its [owner's alias](#owner-aliases) and name properties
* `ssm:<ssm_parameter>` specifies an image through an SSM parameter (kOps 1.26+)
* `ssm:<ssm_parameter>` specifies an image through an SSM parameter (kOps 1.25.3+)
```yaml
image: ami-00579fbb15b954340

View File

@ -194,7 +194,7 @@ using preemptible/spot instances you might be waiting for a long time.
## Fetching images via AWS SSM (AWS Only)
{{ kops_feature_table(kops_added_default='1.26') }}
{{ kops_feature_table(kops_added_default='1.25.3') }}
If you are using AWS, you can dynamically fetch instance group images from an AWS SSM Parameter. kOps will automatically fetch SSM Parameter and lookup the AMI ID on every `kops update cluster` run. This is useful if you often update your images and don't want to update your instance group configuration every time. Your SSM Parameter must start with `ssm:` and contain the full path of the SSM Parameter.