Skip to content

Use namespaced backupstorages/retentionpolicies list for client-org users - #1106

Merged
ArnobKumarSaha merged 1 commit into
masterfrom
arnob-ks-ns-list
Jul 31, 2026
Merged

Use namespaced backupstorages/retentionpolicies list for client-org users#1106
ArnobKumarSaha merged 1 commit into
masterfrom
arnob-ks-ns-list

Conversation

@ArnobKumarSaha

Copy link
Copy Markdown
Member

Follow-up to #1101 for the kubestash options charts.

getData in corekubestashcom-backupconfiguration-editor-options listed storage.kubestash.com/v1alpha1/{retentionpolicies,backupstorages} cluster-scoped, which client-org users (orgType === 3) are not allowed to do. It now falls back to the namespaced URL when the org is a client org and a namespace is known.

The other kubestash *-editor-options charts were checked and need no change: restoresession's getRepositories already has this check, backupsession/repository already use namespaced URLs, backupstorage's getResources is only called for namespaced secrets, and addons/clusterchartpresets are cluster-scoped kinds.

…sers

Signed-off-by: Arnob kumar saha <arnob@appscode.com>
@ArnobKumarSaha
ArnobKumarSaha merged commit 4d86e06 into master Jul 31, 2026
8 checks passed
@ArnobKumarSaha
ArnobKumarSaha deleted the arnob-ks-ns-list branch July 31, 2026 13:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant