全文検索:
- 13 Kubernetes Nginxを立ててみる @06_virtualization:05_container
- READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS ... # curl 10.224.1.17 pod3 </code> ===== 4.cluster IP 作成 ===== cluster ipの8080にアクセスが来ると、nginx-appへ渡す ... rsion: v1 kind: Service metadata: name: cluster-ip spec: type: ClusterIP ports: - name: clus... kubectl get svc NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE cluster-ip C
- 17 Kubernetes IPマスカレード @06_virtualization:05_container
- ersion: apps/v1 kind: DaemonSet metadata: name: ip-masq-agent namespace: kube-system spec: selector: matchLabels: k8s-app: ip-masq-agent template: metadata: labels: k8s-app: ip-masq-agent spec: hostNetwork: true containers: - name: ip-masq-agent image: gcr.io/google-container
- 18 Kubernetes GlusterFS @06_virtualization:05_container
- ==== 18 Kubernetes GlusterFS ====== ^ hostname ^ IP ^ |g-master|172.16.0.103| |g-work01|172.16.0.93| ... ated-by: ssbostan subsets: - addresses: - ip: 172.16.0.93 hostname: g-work01 - ip: 172.16.0.153 hostname: g-work02 - ip: 172.16.0.166 hostname: g-work03 port
- 34 UnboundでHA構成 @06_virtualization:05_container
- m1.png}} ===== IP構成 ===== ^ HV ^ VM ^ Gloval IP ^ Local IP ^ Gloval VIP ^ Local VIP ^ | HV01 | lvs01 | ens5: NIC only | ens4: 192.168.0.21 | 100.10.1... == track_script用意(冗長構成を切り替える際にトリガー) これを用意する事によって、ip l set ens5 down すると、VRRPが切り替わる。 <code> cat << __... .KeepAlive確認 ==== MASTER側にVIPが付いている事確認 <code> # ip -4 a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdis
- 20 Kubernetes GlusterFS Galera Wordpress @06_virtualization:05_container
- a NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE my-release-mariadb-galera ClusterIP 10.110.173.32 <none> ... sion: v1 kind: Service metadata: name: external-ip spec: type: ClusterIP externalIPs: - 172.
- 16 Kubernetes + DRBD Linstor @06_virtualization:05_container
- == 今回はKubernetesのworkerノード3台で、Linstor ^ name ^ IP ^ Disk ^ DRBD用 ^ |node1|172.16.0.65|/dev/sda|/dev... NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READI
- 12 Kubernetes @06_virtualization:05_container
- net.bridge.bridge-nf-call-iptables = 1 net.ipv4.ip_forward = 1 net.bridge.bridge-nf-call-ip6tables = 1 EOF sysctl --system </code> ==== パッケ
- 15 Kubernetes Error @06_virtualization:05_container
- failed to set bridge addr: "cni0" already has an IP address different from 10.244.6.1/24 ==== 対応 ==... に接続できないからnot foundで出るよう。 一度下記などで、VIPを付けて試してみる。 ip addr add [VIP] dev [Eth] ※VIPだけ先に用意していおいて、後からipv
- 27 Docker Djnago @06_virtualization:05_container
- HOSTS = ['django.fl8.jp'] or ALLOWED_HOSTS = ['{IP}'] </code> ===== 5 確認 ===== ブラウザで http://[IP]:8000 をアクセス {{:06_virtualization:05_container:pasted:
- VMware ESXi で 3ware 9650se を使用する @06_virtualization:02_vmware_esxi
- are vSphere CLI\bin>perl vihostupdate.pl -server [IP] -username root -password "[パスワード]" -b c:\AMCC_2.
- 03 Xenインバンドに制限をかける @06_virtualization:03_xen
- (script /etc/xen/scripts/vif-bridge) (ip 8.30.162.23) (rate '625000,50000')
- 05 Xen Guestインストール @06_virtualization:03_xen
- v=bond1 antispoof=yes echo 0 >/proc/sys/net/ipv4/ip_forward </code> ==== 3.network-bridge2作成へ実行権限追加
- 05 Docker Nginx reverse proxy @06_virtualization:05_container
- roto $scheme; proxy_set_header X-Real-IP $remote_addr; proxy_ignore_headers Ca
- 14 Kubernetes Master冗長化 @06_virtualization:05_container
- 応 ==== これはVIPへの通信ができない時にでるよう。 下記などでVIPを先に割振ってみる。 ip addr add [VIP] dev [ETHER] {{tag>Kubernetes}}