You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/microshift-adding-other-packages-to-blueprint.adoc
+7-5Lines changed: 7 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,26 +17,28 @@ Add the references for optional RPM packages to your OSTree blueprint to enable
17
17
. Edit your OSTree blueprint by running the following command:
18
18
+
19
19
[source,terminal]
20
+
[subs="+quotes"]
20
21
----
21
-
$ vi <microshift_blueprint.toml> <1>
22
+
$ vi __<microshift_blueprint.toml>__ <1>
22
23
----
23
-
<1> Replace _<microshift_blueprint.toml>_ with the name of the blueprint file used for the {microshift-short} service.
24
+
<1> Replace `_<microshift_blueprint.toml>_` with the name of the blueprint file used for the {microshift-short} service.
24
25
25
26
. Add the following example text to your blueprint:
26
27
+
27
28
[source,text]
29
+
[subs="+quotes"]
28
30
----
29
31
[[packages]] <1>
30
-
name = "<microshift-additional-package-name>" <2>
32
+
name = "__<microshift-additional-package-name>__" <2>
31
33
version = "*"
32
34
----
33
35
<1> Include one stanza for each additional service that you want to add.
34
-
<2> Replace _<microshift-additional-package-name>_ with the name the RPM for the service you want to include. For example, `microshift-olm`.
36
+
<2> Replace `_<microshift-additional-package-name>_` with the name the RPM for the service you want to include. For example, `microshift-olm`.
35
37
36
38
.Next steps
37
39
. Add custom certificate authorities to the blueprint as needed.
38
40
. After you are done adding to your blueprint, you can apply the manifests to an active cluster by building a new OSTree system and deploying it on the client:
Copy file name to clipboardExpand all lines: modules/microshift-nw-multus-add-pod.adoc
+19-15Lines changed: 19 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,18 +20,19 @@ If you want to attach additional networks to a pod that is already running, you
20
20
21
21
. Add an annotation to a `Pod` YAML file. Only one of the following annotation formats can be used:
22
22
23
-
.. To attach an additional network without any customization, add an annotation with the following format. Replace `<network>` with the name of the additional network to associate with the pod:
23
+
.. To attach an additional network without any customization, add an annotation with the following format. Replace `_<network>_` with the name of the additional network to associate with the pod:
<1> Replace `<network>` with the name of the additional network to associate with the pod. To specify more than one additional network, separate each network with a comma. Do not include whitespace between the comma. If you specify the same additional network multiple times, that pod will have multiple network interfaces attached to that network.
35
+
<1> Replace `_<network>_` with the name of the additional network to associate with the pod. To specify more than one additional network, separate each network with a comma. Do not include whitespace between the comma. If you specify the same additional network multiple times, that pod will have multiple network interfaces attached to that network.
35
36
+
36
37
.Example annotation for a bridge-type additional network
37
38
+
@@ -70,28 +71,29 @@ metadata:
70
71
. To create a `Pod` YAML file and add the `NetworkAttachmentDefinition` annotation for an additional network, run the following command and use the example YAML:
71
72
+
72
73
[source,terminal]
74
+
[subs="+quotes"]
73
75
----
74
-
$ oc apply -f ./<test-bridge>.yaml <1>
76
+
$ oc apply -f ./__<test_bridge>__.yaml <1>
75
77
----
76
-
<1> Replace _<test-bridge>_ with the pod name that you want to use.
78
+
<1> Replace `_<test_bridge>_` with the pod name that you want to use.
77
79
+
78
80
.Example output
79
81
[source,terminal]
80
82
----
81
-
pod/test-bridge created
83
+
pod/test_bridge created
82
84
----
83
85
+
84
-
.Example `test-bridge` pod YAML
86
+
.Example `test_bridge` pod YAML
85
87
[source,yaml]
86
88
----
87
89
apiVersion: v1
88
90
kind: Pod
89
91
metadata:
90
-
name: test-bridge
92
+
name: test_bridge
91
93
annotations:
92
94
k8s.v1.cni.cncf.io/networks: bridge-conf
93
95
labels:
94
-
app: test-bridge
96
+
app: test_bridge
95
97
spec:
96
98
terminationGracePeriodSeconds: 0
97
99
containers:
@@ -128,19 +130,21 @@ metadata:
128
130
# ...
129
131
----
130
132
131
-
. Optional: To confirm that the `NetworkAttachmentDefinition` annotation exists in a `Pod` YAML, run the following command, replacing `<name>` with the name of the pod.
133
+
. Optional: To confirm that the `NetworkAttachmentDefinition` annotation exists in a `Pod` YAML, run the following command, replacing `_<name>_` with the name of the pod.
132
134
+
133
135
[source,terminal]
136
+
[subs="+quotes"]
134
137
----
135
-
$ oc get pod <name> -o yaml <1>
138
+
$ oc get pod __<name>__ -o yaml <1>
136
139
----
137
-
<1> Replace _<name>_ with the pod name you want to use. In the following example, `test-bridge` is used.
140
+
<1> Replace `_<name>_` with the pod name you want to use. In the following example, `_<test_bridge>_` is used.
138
141
+
139
-
In the following example, the `test-bridge` is attached to the `net1` additional network:
142
+
In the following example, the `test_bridge` is attached to the `net1` additional network:
0 commit comments