Skip to content

replace tridentctl command with kubectl to create k8s resource #112

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ac427 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

replace tridentctl command with kubectl to create k8s resource #112

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
60 changes: 37 additions & 23 deletions kb/2023-08-11/using_netapp_third_party_storage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -136,16 +136,29 @@ The procedure is as follows.

```yaml
cat <<EOF> /tmp/backend.yaml
version: 1
backendName: default_backend_san
storageDriverName: <<ontap-san-economy or ontap-san>>
managementLIF: <<ADMIN_IPADDRESS>> ## Often the same as the storage UI IP address
dataLIF: <<DATA_IPADDRESS>> ## IP assigned to the iSCSI-only SVM
svm: <<SVM_NAME>>
username: <<ONTAP storage admin user>>
password: <<password>>
labels:
name: default_backend_san
apiVersion: v1
kind: Secret
metadata:
name: backend-ontap-nas-secret
namespace: trident
type: Opaque
stringData:
username: <<ONTAP storage admin user>>
password: <<password>>
---
apiVersion: trident.netapp.io/v1
kind: TridentBackendConfig
metadata:
name: default-backend-san
namespace: trident
spec:
storageDriverName: <<ontap-san-economy or ontap-san>>
managementLIF: <<ADMIN_IPADDRESS>> ## Often the same as the storage UI IP address
dataLIF: <<DATA_IPADDRESS>> ## IP assigned to the iSCSI-only SVM
backendName: default_backend_san
svm: <<SVM_NAME>>
credentials:
name: backend-ontap-nas-secret
EOF
```

Expand All @@ -155,9 +168,17 @@ The procedure is as follows.
1. Create the backend

```shell
./tridentctl create backend -f /tmp/backend.yaml -n trident
kubectl apply -f /tmp/backend.yaml -n trident
```

2. You can verify the status of the backend at any time with:

```shell
./tridentctl get backend -n trident
```
* A successful completion of the command will result in an output similar to the following:

* You should see an output similar to below

```text
+------------------------+----------------+--------------------------------------+--------+---------+
| NAME | STORAGE DRIVER | UUID | STATE | VOLUMES |
Expand All @@ -166,13 +187,6 @@ The procedure is as follows.
+------------------------+----------------+--------------------------------------+--------+---------+
```

1. You can verify the status of the backend at any time with:

```shell
./tridentctl get backend -n trident
```

* You should see an output similar to the output for a successful backend creation.

1. Define a StorageClass and SnapshotClass.

Expand All @@ -198,13 +212,13 @@ The procedure is as follows.
```
Select the correct value for the backendType in this file before applying.

1. Apply the definitions:
2. Apply the definitions:

```shell
kubectl apply -f /tmp/storage.yaml
```

1. Enable multipathd
2. Enable multipathd

The following is required to enable multipathd.
This must be done on every node of the Harvester cluster, using root access.
Expand All @@ -223,7 +237,7 @@ The procedure is as follows.
- multipathd
```

1. Configure `multipathd` to exclude pathnames used by Longhorn.
2. Configure `multipathd` to exclude pathnames used by Longhorn.

This part is a little tricky. `multipathd` will automatically discover
device names matching a certain pattern, and attempt to set up multipathing on them.
Expand Down Expand Up @@ -284,7 +298,7 @@ The procedure is as follows.

Remember, this has to be done on every node.

1. Enable multipathd.
3. Enable multipathd.

Adding the above files to `/oem` will take effect on the next reboot of the node; `multipathd` can be enabled immediately without rebooting the node using the following commands:

Expand Down