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.

Sign up for GitHub

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

Jump to bottom

Fix wrong link and typo #778

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fix wrong link and typo #778

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
6 changes: 3 additions & 3 deletions docs/virtual_machines/templates.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@ To install the templates:

```console
$ export VERSION=$(curl -s https://api.github.com/repos/kubevirt/common-templates/releases | grep tag_name | grep -v -- '-rc' | head -1 | awk -F': ' '{print $2}' | sed 's/,//' | xargs)
$ oc create -f https://github.com/kubevirt/common-templates/releases/download/$VERSION/common-templates-$VERSION.yaml
$ kubectl create -f https://github.com/kubevirt/common-templates/releases/download/$VERSION/common-templates.yaml
```

#### Editable fields
Expand Down Expand Up @@ -225,7 +225,7 @@ You can add the VM from the template to the cluster in one go

Please note that after the generation step VM and template objects have no relationship with each other besides the aforementioned label. Changes in templates do not automatically affect VMs or vice versa.

### common template customization
### Common template customization

The templates provided by the kubevirt project provide a set of
conventions and annotations that augment the basic feature of the
Expand All @@ -237,7 +237,7 @@ the kubevirt services.

Here's a description of the kubevirt annotations. Unless otherwise
specified, the following keys are meant to be top-level entries of the
template metadata, like
template metadata, like (for Openshift console to display)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
template metadata, like (for Openshift console to display)
template metadata. For OpenShift console to display:


```yaml
apiVersion: v1
Expand Down