Skip to content

Commit d555476

Browse files
authored
Document Ansible 2.11 base image usage (#5535)
Fixes #5437 Signed-off-by: austin <[email protected]>
1 parent 697a426 commit d555476

File tree

1 file changed

+33
-0
lines changed

1 file changed

+33
-0
lines changed
Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
---
2+
title: Ansible Operator Base Images
3+
linkTitle: Base Images
4+
weight: 20
5+
---
6+
7+
Ansible-based operators are built on top of base images built for use
8+
with the Operator-SDK.
9+
10+
11+
## Ansible Versions
12+
13+
There have been some major changes in the Ansible ecosystem, primarily
14+
the addition of `collections` and the removal of these libraries from
15+
Ansible core. Ansible 2.9 is the last release of the "old way", with
16+
forward compatibility for collections. This is the version officially
17+
supported by the Operator-SDK.
18+
19+
Ansible 2.10 was a transition release, and it is NOT recommended for use
20+
with operators.
21+
22+
Ansible 2.11 is the future, and Operator-SDK will eventually provide only 2.11 images. Currently, 2.11 base images are in tech-preview.
23+
See: [ansible-operator-2.11-preview](https://quay.io/repository/operator-framework/ansible-operator-2.11-preview).
24+
25+
## Changing Ansible Operator Base Images
26+
27+
Operators are scaffolded with the latest version of the base image
28+
(using Ansible 2.9) in the first line of the operator Dockerfile.
29+
30+
`FROM quay.io/operator-framework/ansible-operator:v1.16`
31+
32+
Operator authors who want to try out 2.11 can simply replace their FROM with:
33+
`FROM quay.io/operator-framework/ansible-operator-2.11-preview:v1.16`

0 commit comments

Comments
 (0)