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
@@ -194,11 +194,11 @@ The [Device plugins operator README](cmd/operator/README.md) gives the installat
194
194
195
195
The [Device plugins Operator for OpenShift](https://github.com/intel/intel-technology-enabling-for-openshift) gives the installation and usage details for the operator available on [Red Hat OpenShift Container Platform](https://catalog.redhat.com/software/operators/detail/61e9f2d7b9cdd99018fc5736).
196
196
197
-
## XeLink XPU-Manager Sidecar
197
+
## XeLink XPUManager Sidecar
198
198
199
199
To support interconnected GPUs in Kubernetes, XeLink sidecar is needed.
200
200
201
-
The [XeLink XPU-Manager sidecar README](cmd/xpumanager_sidecar/README.md) gives information how the sidecar functions and how to use it.
201
+
The [XeLink XPUManager sidecar README](cmd/xpumanager_sidecar/README.md) gives information how the sidecar functions and how to use it.
Please see XPU-Manager Kubernetes files for additional info on [installation](https://github.com/intel/xpumanager/tree/master/deployment/kubernetes).
56
+
Please see XPUManager Kubernetes files for additional info on [installation](https://github.com/intel/xpumanager/tree/master/deployment/kubernetes).
56
57
57
-
#### Install Sidecar to an Existing XPU-Manager
58
+
#### Install Sidecar to an Existing XPUManager
58
59
59
-
Use patch to add sidecar into the XPU-Manager daemonset.
60
+
Use patch to add sidecar into the XPUManager daemonset.
NOTE: The sidecar patch will remove other resources from the XPU-Manager container. If your XPU-Manager daemonset is using, for example, the smarter device manager resources, those will be removed.
66
+
NOTE: The sidecar patch will remove other resources from the XPUManager container. If your XPUManager daemonset is using, for example, the smarter device manager resources, those will be removed.
66
67
67
-
####Verify Sidecar Functionality
68
+
### Verify Sidecar Functionality
68
69
69
70
You can verify the sidecar's functionality by checking node's xe-links labels:
70
71
71
72
```bash
72
73
$ kubectl get nodes -A -o=jsonpath="{range .items[*]}{.metadata.name},{.metadata.labels.gpu\.intel\.com\/xe-links}{'\n'}{end}"
73
74
master,0.0-1.0_0.1-1.1
74
75
```
76
+
77
+
### Use HTTPS with XPU Manager
78
+
79
+
XPU Manager can be configured to use HTTPS on the metrics interface. For the gunicorn sidecar, cert and key files have to be added to the command:
80
+
```
81
+
- command:
82
+
- gunicorn
83
+
...
84
+
- --certfile=/certs/tls.crt
85
+
- --keyfile=/certs/tls.key
86
+
...
87
+
- xpum_rest_main:main()
88
+
```
89
+
90
+
The gunicorn container will also need the tls.crt and tls.key files within the container. For example:
91
+
92
+
```
93
+
containers:
94
+
- name: python-exporter
95
+
volumeMounts:
96
+
- mountPath: /certs
97
+
name: certs
98
+
readOnly: true
99
+
volumes:
100
+
- name: certs
101
+
secret:
102
+
defaultMode: 420
103
+
secretName: xpum-server-cert
104
+
```
105
+
106
+
In this case, the secret providing the certificate and key is called `xpum-server-cert`.
107
+
108
+
The certificate and key can be [added manually to a secret](https://kubernetes.io/docs/reference/kubectl/generated/kubectl_create/kubectl_create_secret_tls/). Another way to achieve a secret is to leverage [cert-manager](https://cert-manager.io/).
109
+
110
+
<details>
111
+
<summary>Example for the Cert-manager objects</summary>
112
+
113
+
Cert-manager will create a self-signed certificate and the private key, and store them into a secret called `xpum-server-cert`.
114
+
115
+
```
116
+
apiVersion: cert-manager.io/v1
117
+
kind: Issuer
118
+
metadata:
119
+
name: selfsigned-issuer
120
+
spec:
121
+
selfSigned: {}
122
+
---
123
+
apiVersion: cert-manager.io/v1
124
+
kind: Certificate
125
+
metadata:
126
+
name: serving-cert
127
+
spec:
128
+
dnsNames:
129
+
- xpum.svc
130
+
- xpum.svc.cluster.local
131
+
issuerRef:
132
+
kind: Issuer
133
+
name: selfsigned-issuer
134
+
secretName: xpum-server-cert
135
+
```
136
+
137
+
</details>
138
+
139
+
For the XPU Manager sidecar, `use-https` has to be added to the arguments. Then the sidecar will leverage HTTPS with the connection to the metrics interface.
0 commit comments