Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: add link to example configmaps for pipelines to README of each #359

Merged
merged 1 commit into from
Apr 3, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions release/pipelines/windows-bios-installer/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -41,6 +41,7 @@ The Pipeline implements this by spinning up a new VirtualMachine which boots fro
## How to run

Before you create PipelineRuns, you must create ConfigMaps with an autounattend.xml in the same namespace in which the VirtualMachine will be created.
Examples of ConfigMaps can be found [here](https://github.com/kubevirt/kubevirt-tekton-tasks/tree/main/release/pipelines/windows-bios-installer/configmaps).

Pipeline run with resolver:
```yaml
Expand Down
1 change: 1 addition & 0 deletions release/pipelines/windows-customize/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,7 @@ The provided reference ConfigMap (`windows-sqlserver`) boots Windows 10, 11 or W
## How to run

Before you create PipelineRuns, you must create ConfigMaps with an autounattend.xml in the same namespace in which the VirtualMachine will be created.
Examples of ConfigMaps can be found [here](https://github.com/kubevirt/kubevirt-tekton-tasks/tree/main/release/pipelines/windows-customize/configmaps).

Pipeline runs with resolvers:
```yaml
Expand Down
1 change: 1 addition & 0 deletions release/pipelines/windows-efi-installer/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -57,6 +57,7 @@ After the ISO is modified it creates a new VirtualMachine which boots from the m
## How to run

Before you create PipelineRuns, you must create ConfigMaps with an autounattend.xml in the same namespace in which the VirtualMachine will be created.
Examples of ConfigMaps can be found [here](https://github.com/kubevirt/kubevirt-tekton-tasks/tree/main/release/pipelines/windows-efi-installer/configmaps).

Pipeline runs with resolvers:
```yaml
Expand Down
1 change: 1 addition & 0 deletions templates-pipelines/windows-bios-installer/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -41,6 +41,7 @@ The Pipeline implements this by spinning up a new VirtualMachine which boots fro
## How to run

Before you create PipelineRuns, you must create ConfigMaps with an autounattend.xml in the same namespace in which the VirtualMachine will be created.
Examples of ConfigMaps can be found [here](https://github.com/kubevirt/kubevirt-tekton-tasks/tree/main/release/pipelines/windows-bios-installer/configmaps).

Pipeline run with resolver:
{% for item in pipeline_runs_yaml %}
Expand Down
1 change: 1 addition & 0 deletions templates-pipelines/windows-customize/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,7 @@ The provided reference ConfigMap (`windows-sqlserver`) boots Windows 10, 11 or W
## How to run

Before you create PipelineRuns, you must create ConfigMaps with an autounattend.xml in the same namespace in which the VirtualMachine will be created.
Examples of ConfigMaps can be found [here](https://github.com/kubevirt/kubevirt-tekton-tasks/tree/main/release/pipelines/windows-customize/configmaps).

Pipeline runs with resolvers:
{% for item in pipeline_runs_yaml %}
Expand Down
1 change: 1 addition & 0 deletions templates-pipelines/windows-efi-installer/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -57,6 +57,7 @@ After the ISO is modified it creates a new VirtualMachine which boots from the m
## How to run

Before you create PipelineRuns, you must create ConfigMaps with an autounattend.xml in the same namespace in which the VirtualMachine will be created.
Examples of ConfigMaps can be found [here](https://github.com/kubevirt/kubevirt-tekton-tasks/tree/main/release/pipelines/windows-efi-installer/configmaps).

Pipeline runs with resolvers:
{% for item in pipeline_runs_yaml %}
Expand Down