k8s.io/test-infra@v0.0.0-20240520184403-27c6b4c223d8/jobs/e2e_node/crio/README.md (about)

     1  # CRI-O test infra jobs
     2  
     3  **For any modifications to this directory, please ping
     4  [@kubernetes/sig-node-cri-o-test-maintainers](https://github.com/orgs/kubernetes/teams/sig-node-cri-o-test-maintainers)
     5  on the related issue or pull request.**
     6  
     7  All jobs maintained within this directory are part of the `sig-node-cri-o`
     8  testgrid dashboard: https://testgrid.k8s.io/sig-node-cri-o
     9  
    10  ---
    11  
    12  This directory contains all CRI-O related test infra job ignition files. If you
    13  want to change, add or remove any of those `*.ign` files, then please modify the
    14  main configuration in [`./templates/generate`](./templates/generate), which
    15  defines an associative array `CONFIGURATIONS` which defines each ignition file.
    16  
    17  For example the configuration:
    18  
    19  ```bash
    20      ["crio_cgroupsv1"]="root cgroups-v1"
    21  ```
    22  
    23  Will generate the [`crio_cgroupsv1.ign`](./crio_cgroupsv1.ign) configuration
    24  containing the following base configurations in order:
    25  
    26  1. [root.yaml](./templates/base/root.yaml)
    27  1. [cgroups-v1.yaml](./templates/base/cgroups-v1.yaml)
    28  
    29  When running `make` within this directory, an intermediate
    30  [`./templates/crio_cgroupsv1.yaml`](./templates/crio_cgroupsv1.yaml)
    31  [butane](https://coreos.github.io/butane) configuration will be generated which
    32  then gets transformed into the resulting ignition file
    33  [`crio_cgroupsv1.ign`](./crio_cgroupsv1.ign).
    34  The ignition file will be then referenced from image configurations like
    35  [`./latest/image-config-cgrpv1.yaml`](./latest/image-config-cgrpv1.yaml).
    36  
    37  This means modifying, adding or removing jobs should always result in running
    38  `make` as well as committing all changes into this repository.
    39  
    40  If you want to test a ignition config in Google Cloud, ensure that you have
    41  access to the VM by providing the SSH key for the user `core`, for example by
    42  modifying `root.yaml`:
    43  
    44  ```yaml
    45  passwd:
    46    users:
    47      - name: core
    48        ssh_authorized_keys:
    49          - ssh-rsa AAA…
    50  ```
    51  
    52  Then spawn the instance via:
    53  
    54  ```sh
    55  gcloud compute instances create \
    56      --zone europe-west1-b \
    57      --metadata-from-file user-data=/path/to/crio_cgroupsv1.ign \
    58      --image-project fedora-coreos-cloud \
    59      --image-family fedora-coreos-stable my-instance
    60  ```
    61  
    62  Accessing the virtual machine should be now possible by using the external IP of
    63  the instance.