Datasets:
roanbrasil
/
devops-gitops-corpus

Dataset card Data Studio Files
xet
 Community
1
text
stringlengths
0
59.1k
# source: k8s_examples/_archived/volumes/nfs/provisioner/nfs-server-azure-pv.yaml type: yaml
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: nfs-pv-provisioning-demo
annotations:
volume.beta.kubernetes.io/storage-class: managed-premium
labels:
demo: nfs-pv-provisioning
spec:
accessModes: [ "ReadWriteOnce" ]
resources:
requests:
storage: 200Gi
<|endoftext|>
# source: k8s_examples/_archived/volumes/nfs/provisioner/nfs-server-cdk-pv.yaml type: yaml
# PersistentVolumeClaim for Canonical's Charmed Distribution of Kubernetes.
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: nfs-pv-provisioning-demo
labels:
demo: nfs-pv-provisioning
spec:
accessModes: [ "ReadWriteOnce" ]
resources:
requests:
storage: 200Gi
storageClassName: cdk-cinder
<|endoftext|>
# source: k8s_examples/_archived/volumes/nfs/provisioner/nfs-server-gce-pv.yaml type: yaml
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: nfs-pv-provisioning-demo
labels:
demo: nfs-pv-provisioning
spec:
accessModes: [ "ReadWriteOnce" ]
resources:
requests:
storage: 200Gi
<|endoftext|>
# source: k8s_examples/_archived/volumes/nfs/nfs-data/README.md type: docs
# NFS-exporter container with a file
This container exports /exports with index.html in it via NFS. Based on
../exports. Since some Linux kernels have issues running NFSv4 daemons in containers,
only NFSv3 is opened in this container.
Available as `gcr.io/google-samples/nfs-server`
<|endoftext|>
# source: k8s_examples/_archived/volumes/azure_disk/azure.yaml type: yaml
apiVersion: v1
kind: Pod
metadata:
name: azure
spec:
containers:
- image: kubernetes/pause
name: azure
volumeMounts:
- name: azure
mountPath: /mnt/azure
volumes:
- name: azure
azureDisk:
diskName: test.vhd
diskURI: https://someaccount.blob.microsoft.net/vhds/test.vhd
<|endoftext|>
# source: k8s_examples/_archived/volumes/azure_disk/README.md type: docs
# How to Use it?
On Azure VM, create a Pod using the volume spec based on [azure](azure.yaml).
In the pod, you need to provide the following information:
- *diskName*: (required) the name of the VHD blob object OR the name of an Azure managed data disk if Kind is Managed.
- *diskURI*: (required) the URI of the vhd blob object OR the resourceID of an Azure managed data disk if Kind is Managed.
- *kind*: (optional) kind of disk. Must be one of Shared (multiple disks per storage account), Dedicated (single blob disk per storage account), or Managed (Azure managed data disk). Default is Shared.
- *cachingMode*: (optional) disk caching mode. Must be one of None, ReadOnly, or ReadWrite. Default is None.
- *fsType*: (optional) the filesystem type to mount. Default is ext4.
- *readOnly*: (optional) whether the filesystem is used as readOnly. Default is false.
Launch the Pod:
```console
# kubectl create -f examples/staging/volumes/azure_disk/azure.yaml
```
<|endoftext|>
# source: k8s_examples/_archived/volumes/azure_disk/static-provisioning/managed-disk/pod-uses-existing-managed-disk.yaml type: yaml
kind: Pod