Non Admin Controller (NAC) restricts the usage of OADP operator with NonAdminBackups, NonAdminRestores and NonAdminBackupStorageLocations. Admin users may want to further restrict this by restricting NonAdminBackup/NonAdminRestore/NonAdminBackupStorageLocation spec fields values.
Non Admin Controller (NAC) adds the ability to admin users restrict the use of OADP operator for non admin users, by only allowing them to create backup/restore/backupstoragelocation objects from their namespaces with NonAdminBackups/NonAdminRestores/NonAdminBackupStorageLocations. Admin users may want to further restrict non admin users operations, like forcing a specific time to live (TTL) for NonAdminBackups associated Velero Backups. This design enables admin users to set custom default values for NonAdminBackup/NonAdminRestore/NonAdminBackupStorageLocation spec fields, which can not be overridden by non-admin users.
Enable admin users to
- set custom default values for NonAdminBackup spec.backupSpec fields, which can not be overridden
- set custom default values for NonAdminRestore spec.restoreSpec fields, which can not be overridden
- set custom default values for NonAdminBackupStorageLocation spec.backupStorageLocationSpec fields, which can not be overridden
Also
- Show custom default values validation errors in NAC object statuses and in NAC logs
- Show the custom default values to non admin users in NonAdminBackup/NonAdminRestore/NonAdminBackupStorageLocation spec fields
- Prevent non admin users to create NonAdminBackup/NonAdminRestore/NonAdminBackupStorageLocation with overridden defaults
- Allow admin users to set second level defaults (for example, NonAdminBackup
spec.backupSpec.labelSelectorcan have a custom default value, but not justspec.backupSpec.labelSelector.matchLabels) - Check if there are on-going NAC operations prior to recreating NAC Pod
- Allow admin users to enforce falsy values (like empty maps or empty lists) for NonAdminBackup spec.backupSpec fields/NonAdminRestore spec.restoreSpec fields/NonAdminBackupStorageLocation spec.backupStorageLocationSpec fields
New fields will be added to the OADP DPA object, allowing admin users to define custom default and enforced values for specific fields in NonAdminBackup, NonAdminRestore, and NonAdminBackupStorageLocation specifications. The NAC will enforce these values accordingly.
-
NonAdminBackup: Admin users can specify which
spec.backupSpecfields have custom default and enforced values. If a NonAdminBackup is created with values that override enforced settings, it will fail validation before creating an associated Velero Backup. -
NonAdminRestore: Admin users can define enforced and default values for
spec.restoreSpecfields. Any NonAdminRestore that attempts to override enforced values will fail validation before creating an associated Velero Restore. -
NonAdminBackupStorageLocation: Admin users can set enforced and default values for
spec.backupStorageLocationSpecfields, except for spec.backupStorageLocationSpec.default, which is not included in the enforcement BSL Spec. If a NonAdminBackupStorageLocation attempts to override enforced values, it will fail validation before creating an associated Velero BackupStorageLocation.
If admin user changes any enforced field value, NAC Pod is recreated to always be up to date with admin user enforcements.
Note: if there are on-going NAC operations prior to recreating NAC Pod, reconcile progress might get lost for NAC objects.
Field spec.nonAdmin.enforceBackupSpec, of the same type as the Velero Backup Spec, will be added to OADP DPA object.
Field spec.nonAdmin.enforceRestoreSpec, of the same type as the Velero Restore Spec, will be added to OADP DPA object.
Field spec.nonAdmin.enforceBSLSpec, which mirrors the Velero BackupStorageLocation Spec, will be introduced in the
OADP DPA object with the following exceptions:
- Fields marked as
requiredin the Velero BSL Spec are treated asoptionalin the enforcement BSL Spec. This allows admin users to enforce specific fields without requiring others. - The
defaultfield is excluded from the enforcement BSL Spec, because it can not be enforced.
With the above fields, admin users will be able to select for example which NonAdminBackup spec.backupSpec fields have custom default (and enforced) values.
To avoid mistakes, not all fields will be able to be enforced, like IncludedNamespaces, that could break NAC usage.
NAC will respect the set values by reading DPA field during startup.If admin user changes any enforced field value, NAC Pod is recreated (and only NAC Pod) to always be up to date with admin user enforcements.
If a NonAdminBackup is created with fields overriding any enforced values, it will fail validation prior to creating an associated Velero Backup. Validation error is shown in NonAdminBackup status and NAC logs.
If NonAdminBackup respects enforcement, the created associated Velero Backup will have the enforced spec field values.
Enforcement is done dynamically. If new field is added to Velero Backup Spec, it will be presented to user without code changes. If a field changes type/or default value, tests will warn us.
In this example, admin user has configured NAC with the following OADP DPA options
...
spec:
...
nonAdmin:
enable: true
enforceBackupSpecs:
snapshotVolumes: falseThat means, that the 2 following NonAdminBackup will be accepted by NAC validation
...
spec:
backupSpec:
snapshotVolumes: false...
spec:
backupSpec:
ttl: 3hNote: the related Velero Backup for this NonAdminBackup will have
spec.snapshotVolumesset to false
But this NonAdminBackup will not be accepted by NAC validation
...
spec:
backupSpec:
snapshotVolumes: trueNonAdminBackup status and NAC log will have the following message:
spec.backupSpec.snapshotVolumes field value is enforced by admin user, can not override it
Instead of using a DPA field, using a ConfigMap was considered. Since users would not have type assertion when creating those ConfigMap and parsing it would be harder in NAC side, it was discarded.
No security considerations.
No compatibility issues.
Add EnforceBackupSpec struct to OADP DPA NonAdmin struct
type NonAdmin struct {
// which bakup spec field values to enforce
// +optional
EnforceBackupSpec *velero.BackupSpec `json:"enforceBackupSpec,omitempty"`
}Add EnforceRestoreSpec struct to OADP DPA NonAdmin struct
type NonAdmin struct {
// which restore spec field values to enforce
// +optional
EnforceRestoreSpec *velero.RestoreSpec `json:"enforceRestoreSpec,omitempty"`
}Add EnforceBSLSpec struct to OADP DPA NonAdmin struct
type NonAdmin struct {
// which backupstoragelocation spec field values to enforce
// +optional
EnforceBSLSpec *velero.BackupStorageLocationSpec `json:"enforceBSLSpec,omitempty"`
}
During NAC startup, read OADP DPA, to be able to apply admin user enforcement
```go
restConfig := ctrl.GetConfigOrDie()
dpaClientScheme := runtime.NewScheme()
utilruntime.Must(v1alpha1.AddToScheme(dpaClientScheme))
dpaClient, err := client.New(restConfig, client.Options{
Scheme: dpaClientScheme,
})
if err != nil {
setupLog.Error(err, "unable to create Kubernetes client")
os.Exit(1)
}
dpaList := &v1alpha1.DataProtectionApplicationList{}
err = dpaClient.List(context.Background(), dpaList)
if err != nil {
setupLog.Error(err, "unable to list DPAs")
os.Exit(1)
}Modify ValidateBackupSpec function to use EnforceBackupSpec and apply that to non admin users' NonAdminBackup request
func ValidateBackupSpec(nonAdminBackup *nacv1alpha1.NonAdminBackup, enforcedBackupSpec *velerov1.BackupSpec) error {
enforcedSpec := reflect.ValueOf(enforcedBackupSpec).Elem()
for index := range enforcedSpec.NumField() {
enforcedField := enforcedSpec.Field(index)
enforcedFieldName := enforcedSpec.Type().Field(index).Name
currentField := reflect.ValueOf(nonAdminBackup.Spec.BackupSpec).Elem().FieldByName(enforcedFieldName)
if !enforcedField.IsZero() && !currentField.IsZero() && !reflect.DeepEqual(enforcedField.Interface(), currentField.Interface()) {
field, _ := reflect.TypeOf(nonAdminBackup.Spec.BackupSpec).Elem().FieldByName(enforcedFieldName)
tagName, _, _ := strings.Cut(field.Tag.Get("json"), ",")
return fmt.Errorf(
"NonAdminBackup spec.backupSpec.%v field value is enforced by admin user, can not override it",
tagName,
)
}
}
}Before creating NonAdminBackup's related Velero Backup, apply any missing fields to it that admin user has enforced
enforcedSpec := reflect.ValueOf(r.EnforcedBackupSpec).Elem()
for index := range enforcedSpec.NumField() {
enforcedField := enforcedSpec.Field(index)
enforcedFieldName := enforcedSpec.Type().Field(index).Name
currentField := reflect.ValueOf(backupSpec).Elem().FieldByName(enforcedFieldName)
if !enforcedField.IsZero() && currentField.IsZero() {
currentField.Set(enforcedField)
}
}Modify ValidateRestoreSpec function to use EnforceRestoreSpec and apply that to non admin users' NonAdminRestore request
enforcedSpec := reflect.ValueOf(enforcedRestoreSpec).Elem()
for index := range enforcedSpec.NumField() {
enforcedField := enforcedSpec.Field(index)
enforcedFieldName := enforcedSpec.Type().Field(index).Name
currentField := reflect.ValueOf(nonAdminRestore.Spec.RestoreSpec).Elem().FieldByName(enforcedFieldName)
if !enforcedField.IsZero() && !currentField.IsZero() && !reflect.DeepEqual(enforcedField.Interface(), currentField.Interface()) {
field, _ := reflect.TypeOf(nonAdminRestore.Spec.RestoreSpec).Elem().FieldByName(enforcedFieldName)
tagName, _, _ := strings.Cut(field.Tag.Get("json"), ",")
return fmt.Errorf(
"NonAdminRestore spec.restoreSpec.%v field value is enforced by admin user, can not override it",
tagName,
)
}
}Before creating NonAdminRestore's related Velero Restore, apply any missing fields to it that admin user has enforced
enforcedSpec := reflect.ValueOf(r.EnforcedRestoreSpec).Elem()
for index := range enforcedSpec.NumField() {
enforcedField := enforcedSpec.Field(index)
enforcedFieldName := enforcedSpec.Type().Field(index).Name
currentField := reflect.ValueOf(restoreSpec).Elem().FieldByName(enforcedFieldName)
if !enforcedField.IsZero() && currentField.IsZero() {
currentField.Set(enforcedField)
}
}Modify ValidateBSLSpec function to use EnforceBSLSpec and apply that to non admin users' NonAdminBackupStorageLocation request
enforcedSpec := reflect.ValueOf(enforcedBSLSpec).Elem()
for index := range enforcedSpec.NumField() {
enforcedField := enforcedSpec.Field(index)
enforcedFieldName := enforcedSpec.Type().Field(index).Name
currentField := reflect.ValueOf(nonAdminBsl.Spec.BackupStorageLocationSpec).Elem().FieldByName(enforcedFieldName)
if !enforcedField.IsZero() && !currentField.IsZero() && !reflect.DeepEqual(enforcedField.Interface(), currentField.Interface()) {
field, _ := reflect.TypeOf(nonAdminBsl.Spec.BackupStorageLocationSpec).Elem().FieldByName(enforcedFieldName)
tagName, _, _ := strings.Cut(field.Tag.Get("json"), ",")
return fmt.Errorf(
"NonAdminBackupStorageLocation spec.backupStorageLocationSpec.%v field value is enforced by admin user, can not override it",
tagName,
)
}
}Before creating NonAdminBackupStorageLocation's related Velero BackupStorageLocation, apply any missing fields to it that admin user has enforced
enforcedSpec := reflect.ValueOf(r.EnforcedBSLSpec).Elem()
for index := range enforcedSpec.NumField() {
enforcedField := enforcedSpec.Field(index)
enforcedFieldName := enforcedSpec.Type().Field(index).Name
currentField := reflect.ValueOf(bslSpec).Elem().FieldByName(enforcedFieldName)
if !enforcedField.IsZero() && currentField.IsZero() {
currentField.Set(enforcedField)
}
}For more details, check openshift/oadp-operator#1584, migtools#110, openshift/oadp-operator#1600 and migtools#122.
- Show NonAdminBackup spec.backupSpec fields/NonAdminRestore spec.restoreSpec fields custom default values to non admin users migtools#111