Skip to content

Trident and k8s 1.35 warnings and missing RBACS #1123

@marsom

Description

@marsom

Describe the bug

there are several warning probabliy comming from the kuectl ingrgreation:

│ I0316 15:35:29.458318       1 warnings.go:107] "Warning: unknown field \"backendUUID\""                                                                                                                            │
│ I0316 15:35:29.458343       1 warnings.go:107] "Warning: unknown field \"pool\""                                                                                                                                   │
│ I0316 15:35:29.458348       1 warnings.go:107] "Warning: unknown field \"storageClass\""                                                                                                                           │
│ I0316 15:35:29.458355       1 warnings.go:107] "Warning: metadata.finalizers: \"trident.netapp.io\": prefer a domain-qualified finalizer name including a path (/) to avoid accidental conflicts with other finali │
│ I0316 15:35:30.236387       1 warnings.go:107] "Warning: unknown field \"backendUUID\""
│ I0316 15:35:30.236408       1 warnings.go:107] "Warning: unknown field \"pool\""
│ I0316 15:35:30.236413       1 warnings.go:107] "Warning: unknown field \"storageClass\""

thurdermoere i need to add some rbacs because the csi-reziser pod complained about misssing rbacs

apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: trident-controller-missing
rules:
  - apiGroups:
      - storage.k8s.io
    resources:
      - volumeattachments
      - volumeattributesclasses
    verbs:
      - get
      - list
      - watch
      - create
      - delete
      - update
      - patch
  - apiGroups:
      - storage.k8s.io
    resources:
      - volumeattachments/status
      - volumeattributesclasses/status
    verbs:
      - update
      - patch
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: trident-controller-missing
subjects:
  - kind: ServiceAccount
    name: trident-controller
    namespace: {{ .Release.Namespace }}
roleRef:
  kind: ClusterRole
  name: trident-controller-missing
  apiGroup: rbac.authorization.k8s.io

Environment
Provide accurate information about the environment to help us reproduce the issue.

  • Trident version: 100.2602.0 / 26.0.2
  • Trident installation flags used: TridentOperator
  • Kubernetes version: 1.35.1
  • Kubernetes orchestrator: vanilla
  • OS: Talos
  • NetApp backend types: ONTAP
  • Other:

To Reproduce

deploy trident to a 1.35 clsuter

Expected behavior

warnings are ok, if they are not problematik.
missing rbacs shoudl be fixed in helm chart

Additional context
Add any other context about the problem here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions