text stringlengths 0 59.1k |
|---|
persistentVolumeReclaimPolicy: Retain |
azureFile: |
# Replace with your secret name |
secretName: azure-secret |
# Replace with correct storage share name |
shareName: k8stest |
# In case the secret is stored in a different namespace |
#secretNamespace: default |
readOnly: false |
<|endoftext|> |
# source: k8s_examples/_archived/volumes/azure_file/README.md type: docs |
# How to Use it? |
Install *cifs-utils* on the Kubernetes host. For example, on Fedora based Linux |
# yum -y install cifs-utils |
Note, as explained in [Azure File Storage for Linux](https://azure.microsoft.com/en-us/documentation/articles/storage-how-to-use-files-linux/), the Linux hosts and the file share must be in the same Azure region. |
## Create a storage access secret |
Obtain an Microsoft Azure storage account and extract the storage account name (which you provided) and one of the storage account keys. You will then need to create a Kubernetes secret which holds both the account name and key. You can use `kubectl` directly to create the secret: |
```console |
# kubectl create secret generic azure-secret --from-literal=azurestorageaccountname=<...> --from-literal=azurestorageaccountkey=<...> |
``` |
Alternatively, you can create a [secret](secret/azure-secret.yaml) that contains the base64 encoded Azure Storage account name and key. In the secret file, base64-encode Azure Storage account name and pair it with name `azurestorageaccountname`, and base64-encode Azure Storage access key and pair it with name `azuresto... |
Based on the storage account name, and using the [`az` command line](https://docs.microsoft.com/en-us/cli/azure/?view=azure-cli-latest), you can also extract the storage account key using the following command line, given that you are logged in using `az login` with a service principal which has access to the service a... |
```console |
# export STORAGE_ACCOUNT_KEY=$(az storage account keys list -n <storage account name> -g <resource group> --query='[0].value' | tr -d '"') |
``` |
## Pod creation |
Then create a Pod using the volume spec based on [azure](azure.yaml). |
In the pod, you need to provide the following information: |
- `secretName`: the name of the secret that contains both Azure storage account name and key. |
- `shareName`: The share name to be used. |
- `readOnly`: Whether the filesystem is used as readOnly. |
Create the secret: |
```console |
# kubectl create -f examples/volumes/azure_file/secret/azure-secret.yaml |
``` |
You should see the account name and key from `kubectl get secret` |
### Mount volume directly in Pod |
Then create the Pod: |
```console |
# kubectl create -f examples/volumes/azure_file/azure.yaml |
``` |
### Mount volume via `pv` and `pvc` |
The same mechanism can also be used to mount the Azure File Storage using a Persistent Volume and a Persistent Volume Claim: |
* [Persistent Volume using `azureFile`](azure-pv.yaml) |
* [Persistent Volume Claim matching the Volume](azure-pvc.yaml) |
Correspondingly, you then mount the volume inside pods using the normal `persistentVolumeClaim` reference. This mechanism is used in the sample pod YAML [azure-2.yaml](azure-2.yaml). |
<|endoftext|> |
# source: k8s_examples/_archived/volumes/azure_file/azure-2.yaml type: yaml |
apiVersion: v1 |
kind: Pod |
metadata: |
name: azure-2 |
spec: |
containers: |
- image: kubernetes/pause |
name: azure-2 |
volumeMounts: |
- name: azure |
mountPath: /mnt/azure |
volumes: |
- name: azure |
persistentVolumeClaim: |
claimName: sample-storage-claim |
<|endoftext|> |
# source: k8s_examples/_archived/volumes/azure_file/secret/azure-secret.yaml type: yaml |
apiVersion: v1 |
kind: Secret |
metadata: |
name: azure-secret |
type: Opaque |
data: |
azurestorageaccountname: azhzdGVzdA== |
azurestorageaccountkey: eElGMXpKYm5ub2pGTE1Ta0JwNTBteDAyckhzTUsyc2pVN21GdDRMMTNob0I3ZHJBYUo4akQ2K0E0NDNqSm9nVjd5MkZVT2hRQ1dQbU02WWFOSHk3cWc9PQ== |
<|endoftext|> |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.