Scripts User Guide
This README documents:
- What update-crd.sh and update-generated-code.sh do
- When and how to use them
update-generated-code.sh
This is the script to update clientset/informers/listers and API deepcopy code using code-generator.
Make sure to run this script after making changes to /client/apis/volumesnapshot/v1/types.go.
Pre-requisites for running update-generated-code.sh:
-
Set
GOPATH
export GOPATH=~/go
-
Ensure external-snapshotter repository is at
~/go/src/github.com/kubernetes-csi/external-snapshotter
-
Clone code-generator
cd ~/go/src/k8s.io git clone https://github.com/kubernetes/code-generator.git
-
Checkout latest release version
git checkout v0.29.1
-
Ensure the file
generate-groups.sh
existsls ${GOPATH}/src/k8s.io/code-generator/generate-groups.sh
Update generated client code in external-snapshotter
cd ~/go/src/github.com/kubernetes-csi/external-snapshotter/client
./hack/update-generated-code.sh
Once you run the script, you will get an output as follows:
Generating deepcopy funcs
Generating clientset for volumesnapshot:v1 at github.com/kubernetes-csi/external-snapshotter/client/v7/clientset
Generating listers for volumesnapshot:v1 at github.com/kubernetes-csi/external-snapshotter/client/v7/listers
Generating informers for volumesnapshot:v1 at github.com/kubernetes-csi/external-snapshotter/client/v7/informers
update-crd.sh
NOTE: We need to keep both v1beta1 and v1 snapshot APIs but set served and storage version of v1beta1 to false. Please copy back the v1beta1 manifest back to the files as this script will remove it.
This is the script to update CRD yaml files under /client/config/crd/ based on types.go file.
Make sure to run this script after making changes to /client/apis/volumesnapshot/v1/types.go.
Follow these steps to update the CRD:
-
Run ./hack/update-crd.sh from client directory, new yaml files should have been created under ./config/crd/
-
Add api-approved.kubernetes.io annotation value in all yaml files in the metadata section with the PR where the API is approved by the API reviewers. The current approved PR for snapshot v1 API is https://github.com/kubernetes-csi/external-snapshotter/pull/419. Refer to https://github.com/kubernetes/enhancements/pull/1111 for details about this annotation.
-
Update the restoreSize property to string in snapshot.storage.k8s.io_volumesnapshots.yaml
The generated yaml file contains restoreSize property anyOf as described below:
restoreSize:
anyOf:
- type: integer
- type: string
description: restoreSize represents the complete size of the snapshot
in bytes. In dynamic snapshot creation case, this field will be filled
in with the "size_bytes" value returned from CSI "CreateSnapshotRequest"
gRPC call. For a pre-existing snapshot, this field will be filled
with the "size_bytes" value returned from the CSI "ListSnapshots"
gRPC call if the driver supports it. When restoring a volume from
this snapshot, the size of the volume MUST NOT be smaller than the
restoreSize if it is specified, otherwise the restoration will fail.
If not specified, it indicates that the size is unknown.
Update the restoreSize property to use type string only:
restoreSize:
type: string
description: restoreSize represents the complete size of the snapshot
in bytes. In dynamic snapshot creation case, this field will be filled
in with the "size_bytes" value returned from CSI "CreateSnapshotRequest"
gRPC call. For a pre-existing snapshot, this field will be filled
with the "size_bytes" value returned from the CSI "ListSnapshots"
gRPC call if the driver supports it. When restoring a volume from
this snapshot, the size of the volume MUST NOT be smaller than the
restoreSize if it is specified, otherwise the restoration will fail.
If not specified, it indicates that the size is unknown.
- In
client/config/crd/snapshot.storage.k8s.io_volumesnapshots.yaml
, we need to add theoneOf
constraint to make sure only one ofpersistentVolumeClaimName
andvolumeSnapshotContentName
is specified in thesource
field of thespec
ofVolumeSnapshot
.
source:
description: source specifies where a snapshot will be created from. This field is immutable after creation. Required.
properties:
persistentVolumeClaimName:
description: persistentVolumeClaimName specifies the name of the PersistentVolumeClaim object representing the volume from which a snapshot should be created. This PVC is assumed to be in the same namespace as the VolumeSnapshot object. This field should be set if the snapshot does not exists, and should be created. This field is immutable.
type: string
volumeSnapshotContentName:
description: volumeSnapshotContentName specifies the name of a pre-existing VolumeSnapshotContent object representing an existing volume snapshot. This field should be set if the snapshot already exists. This field is immutable.
type: string
type: object
oneOf:
- required: ["persistentVolumeClaimName"]
- required: ["volumeSnapshotContentName"]
volumeSnapshotClassName:
- In
client/config/crd/snapshot.storage.k8s.io_volumesnapshotcontents.yaml
, we need to add theoneOf
constraint to make sure only one ofsnapshotHandle
andvolumeHandle
is specified in thesource
field of thespec
ofVolumeSnapshotContent
.
source:
description: source specifies from where a snapshot will be created. This field is immutable after creation. Required.
properties:
snapshotHandle:
description: snapshotHandle specifies the CSI "snapshot_id" of a pre-existing snapshot on the underlying storage system. This field is immutable.
type: string
volumeHandle:
description: volumeHandle specifies the CSI "volume_id" of the volume from which a snapshot should be dynamically taken from. This field is immutable.
type: string
type: object
oneOf:
- required: ["snapshotHandle"]
- required: ["volumeHandle"]
sourceVolumeMode:
-
Add the VolumeSnapshot namespace to the
additionalPrinterColumns
section. Refer https://github.com/kubernetes-csi/external-snapshotter/pull/535 for more details. -
In
client/config/crd/groupsnapshot.storage.k8s.io_volumegroupsnapshotcontents.yaml
, we need to add theoneOf
constraint to make sure only one ofvolumeHandles
andgroupSnapshotHandles
is specified in thesource
field of thespec
ofVolumeGroupSnapshotContent
.
source:
description: Source specifies whether the snapshot is (or should be)
dynamically provisioned or already exists, and just requires a Kubernetes
object representation. This field is immutable after creation. Required.
properties:
groupSnapshotHandles:
description: GroupSnapshotHandles specifies the CSI "group_snapshot_id"
of a pre-existing group snapshot and a list of CSI "snapshot_id"
of pre-existing snapshots on the underlying storage system for
which a Kubernetes object representation was (or should be)
created. This field is immutable.
properties:
volumeGroupSnapshotHandle:
description: VolumeGroupSnapshotHandle specifies the CSI "group_snapshot_id"
of a pre-existing group snapshot on the underlying storage
system for which a Kubernetes object representation was
(or should be) created. This field is immutable. Required.
type: string
volumeSnapshotHandles:
description: VolumeSnapshotHandles is a list of CSI "snapshot_id"
of pre-existing snapshots on the underlying storage system
for which Kubernetes objects representation were (or should
be) created. This field is immutable. Required.
items:
type: string
type: array
required:
- volumeGroupSnapshotHandle
- volumeSnapshotHandles
type: object
volumeHandles:
description: VolumeHandles is a list of volume handles on the
backend to be snapshotted together. It is specified for dynamic
provisioning of the VolumeGroupSnapshot. This field is immutable.
items:
type: string
type: array
type: object
oneOf:
- required: ["volumeHandles"]
- required: ["groupSnapshotHandles"]
volumeGroupSnapshotClassName: