Skip to content
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.

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

Possibility to create a backend with a custom resource instead tridentctl. #538

Closed
ykoer opened this issue Feb 25, 2021 · 3 comments
Closed

Comments

@ykoer
Copy link

ykoer commented Feb 25, 2021

We are managing our Kubernetes clusters with ArgoCD. It is currently installing the Trident Operator, but backends can be managed only with tridentctl. I would like to have the possibility to create backends with a custom resource.
Is that feature already on your radar?

Thanks
Yusuf

@clintonk
Copy link
Contributor

@ykoer Yes. @gnarl may be able to provide more insight on when you might see that.

@gnarl
Copy link
Contributor

gnarl commented Mar 8, 2021

Hi @ykoer,

Closing this issue as a duplicate of GitHub Issue #358. We are working on providing this support in a future Trident release.

@gnarl gnarl closed this as completed Mar 8, 2021
@c4m4
Copy link

c4m4 commented Mar 22, 2023

This is an example about how to create the backend, using the crd:

apiVersion: trident.netapp.io/v1
kind: TridentBackendConfig
metadata:
  name: backend-btc-solidfire
  namespace: trident
type: Opaque
spec:
  version: 1
  storageDriverName: solidfire-san
  credentials:
    name: backend-btc-solidfire
  SVIP: x.x.x.x:3260
  TenantName: K8S-LAB
  Types:
    - Type: btc
      Qos:
        minIOPS: 1000
        maxIOPS: 2000
        burstIOPS: 4000
    - Type: ada
      Qos:
        minIOPS: 1000
        maxIOPS: 3000
        burstIOPS: 5000
  storage:
  storage:
    - labels:
        performance: btc
      type: btc
    - labels:
        performance: ada
      type: ada

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants