@@ -17,22 +17,22 @@ defines an associative array `CONFIGURATIONS` which defines each ignition file.
17
17
For example the configuration:
18
18
19
19
``` bash
20
- [" crio_cgroupv1 " ]=" root cgroupv1 "
20
+ [" crio_cgroupv2 " ]=" root env "
21
21
```
22
22
23
- Will generate the [ ` crio_cgroupv1 .ign` ] ( ./crio_cgroupv1 .ign ) configuration
23
+ Will generate the [ ` crio_cgroupv2 .ign` ] ( ./crio_cgroupv2 .ign ) configuration
24
24
containing the following base configurations in order:
25
25
26
26
1 . [ root.yaml] ( ./templates/base/root.yaml )
27
- 1 . [ cgroupv1 .yaml] ( ./templates/base/cgroupv1 .yaml )
27
+ 1 . [ env .yaml] ( ./templates/base/env .yaml )
28
28
29
29
When running ` make ` within this directory, an intermediate
30
- [ ` ./templates/crio_cgroupv1 .yaml ` ] ( ./templates/crio_cgroupv1 .yaml )
30
+ [ ` ./templates/crio_cgroupv2 .yaml ` ] ( ./templates/crio_cgroupv2 .yaml )
31
31
[ butane] ( https://coreos.github.io/butane ) configuration will be generated which
32
32
then gets transformed into the resulting ignition file
33
- [ ` crio_cgroupv1 .ign` ] ( ./crio_cgroupv1 .ign ) .
33
+ [ ` crio_cgroupv2 .ign` ] ( ./crio_cgroupv2 .ign ) .
34
34
The ignition file will be then referenced from image configurations like
35
- [ ` ./latest/image-config-cgroupv1 .yaml ` ] ( ./latest/image-config-cgroupv1 .yaml ) .
35
+ [ ` ./latest/image-config-cgroupv2 .yaml ` ] ( ./latest/image-config-cgroupv2 .yaml ) .
36
36
37
37
This means modifying, adding or removing jobs should always result in running
38
38
` make ` as well as committing all changes into this repository.
@@ -54,7 +54,7 @@ Then spawn the instance via:
54
54
` ` ` sh
55
55
gcloud compute instances create \
56
56
--zone europe-west1-b \
57
- --metadata-from-file user-data=/path/to/crio_cgroupv1 .ign \
57
+ --metadata-from-file user-data=/path/to/crio_cgroupv2 .ign \
58
58
--image-project fedora-coreos-cloud \
59
59
--image-family fedora-coreos-stable my-instance
60
60
```
0 commit comments