blob: ea00f5819399ad09755273bdc73ed08da8040bf7 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
|
oc -n adei patch dc/mysql --type=json --patch '[{"op": "remove", "path": "/spec/template/spec/nodeSelector"}]'
oc process -f mysql.yml | oc -n adei replace dc/mysql -f -
oc -n adei delete --force --grace-period=0 pod mysql-1-m4wcq
We use rpcbind from the host.
we need isciinitiators, rpcbind is used for host but check with telnet. The mother volumes are provisioned 100GiB large. So we can't allocate more.
We can use rpcbind (and other services) from the host. Host networking.
oc -n adei delete --force --grace-period=0 pod mysql-1-m4wcq
| grep -oP '^GBID:\s*\K.*'
Top level (nodeSelector restarPolciy SecurityContext)
dnsPolicy: ClusterFirstWithHostNet
dnsPolicy: ClusterFirst
hostNetwork: true
oc -n kaas adm policy add-scc-to-user hostnetwork -z default
Check (in users list)
oc get scc hostnetwork -o yaml
firewall-cmd --add-port=5002/tcp
OnDelete: This is the default update strategy for backward-compatibility. With OnDelete update strategy, after you update a DaemonSet template, new DaemonSet pods will only be created when you manually delete old DaemonSet pods. This is the same behavior of DaemonSet in Kubernetes version 1.5 or before.
RollingUpdate: With RollingUpdate update strategy, after you update a DaemonSet template, old DaemonSet pods will be killed, and new DaemonSet pods will be created automatically, in a controlled fashion.
Caveat: Updating DaemonSet created from Kubernetes version 1.5 or before
.spec.updateStrategy.rollingUpdate.maxUnavailable (default to 1) and .spec.minReadySeconds
“Default”: The Pod inherits the name resolution configuration from the node that the pods run on. See related discussion for more details.
“ClusterFirst”: Any DNS query that does not match the configured cluster domain suffix, such as “www.kubernetes.io”, is forwarded to the upstream nameserver inherited from the node. Cluster administrators may have extra stub-domain and upstream DNS servers configured. See related discussion for details on how DNS queries are handled in those cases.
“ClusterFirstWithHostNet”: For Pods running with hostNetwork, you should explicitly set its DNS policy “ClusterFirstWithHostNet”.
“None”: A new option value introduced in Kubernetes v1.9. This Alpha feature allows a Pod to ignore DNS settings from the Kubernetes environment. All DNS settings are supposed to be provided using the dnsConfig field in the Pod Spec. See DNS config subsection below.
|
