kubernetes
/
examples
mirror of https://github.com/kubernetes/examples.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

improve formatting

This commit is contained in:
Jason Murray 2020-08-10 19:07:46 -07:00
parent cc3e7657d1
commit bc7a20b62c
No known key found for this signature in database
GPG Key ID: A931039A241EBC2A
1 changed files with 20 additions and 22 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

42
staging/volumes/fibre_channel/README.md
View File

@ -22,40 +22,38 @@
## Step-by-Step
1. Set up a Fibre Channel Target
### Set up a Fibre Channel Target
Using your Fibre Channel SAN Zone manager you must allocate and mask LUNs so that all hosts in the Kubernetes cluster can access them
Using your Fibre Channel SAN Zone manager you must allocate and mask LUNs so that all hosts in the Kubernetes cluster can access them
2. Prepare nodes in your Kubernetes cluster
### Prepare nodes in your Kubernetes cluster
You will need to install and configured a Fibre Channel initiator on the hosts within your Kubernetes cluster.
You will need to install and configured a Fibre Channel initiator on the hosts within your Kubernetes cluster.
3. Create a Pod using Fibre Channel persistent storage
### Create a Pod using Fibre Channel persistent storage
Create a pod manifest based on [fc.yaml](fc.yaml). You will need to provide *targetWWNs* (array of Fibre Channel target's World Wide Names), *lun*, and the type of the filesystem that has been created on the LUN if it is not _ext4_
Create a pod manifest based on [fc.yaml](fc.yaml). You will need to provide *targetWWNs* (array of Fibre Channel target's World Wide Names), *lun*, and the type of the filesystem that has been created on the LUN if it is not _ext4_
Once you have created a pod manifest you can deploy it by running:
Once you have created a pod manifest you can deploy it by running:
```console
kubectl apply -f ./your_new_pod.yaml
```
```console
kubectl apply -f ./your_new_pod.yaml
```
You can then confirm that the pod hase been sucessfully deployed by running `kubectl get pod fibre-channel-example-pod -o wide`
You can then confirm that the pod hase been sucessfully deployed by running `kubectl get pod fibre-channel-example-pod -o wide`
```console
# kubectl get pod fibre-channel-example-pod -o wide
NAME READY STATUS RESTARTS AGE
1/1 Running 0 1m
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
fibre-channel-example-pod 1/1 READY 0 1m8s 192.168.172.11 node0 <none> <none>
```console
# kubectl get pod fibre-channel-example-pod -o wide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
fibre-channel-example-pod 1/1 READY 0 1m8s 192.168.172.11 node0 <none> <none>
```
```
If you connect to the console on the Kubernetes node that the pod has been assigned to you can see that the volume is mounted to the pod by running `mount | grep /var/lib/kubelet/plugins/kubernetes.io/fc/`
If you connect to the console on the Kubernetes node that the pod has been assigned to you can see that the volume is mounted to the pod by running `mount | grep /var/lib/kubelet/plugins/kubernetes.io/fc/`
```console
# mount | grep /var/lib/kubelet/plugins/kubernetes.io/fc/
/dev/mapper/360a98000324669436c2b45666c567946 on /var/lib/kubelet/plugins/kubernetes.io/fc/500a0982991b8dc5-lun-2 type ext4 (relatime,seclabel,stripe=16,data=ordered)
```console
# mount | grep /var/lib/kubelet/plugins/kubernetes.io/fc/
/dev/mapper/360a98000324669436c2b45666c567946 on /var/lib/kubelet/plugins/kubernetes.io/fc/500a0982991b8dc5-lun-2 type ext4 (relatime,seclabel,stripe=16,data=ordered)
```
## Multipath Considerations