[SURE-11255] Pass Annotations to Namespace Created by Workspace

[kkaempf]

SURE-11255

Issue description:

The user reports that when creating a workspace in fleet the annotations are not inherited by the corresponding namespace object. They would like Rancher Fleet workspace annotation to pass to namespace or at least to have an optional field to pass fleet workspace annotations to namespace during workspace creation.

// for example:

apiVersion: management.cattle.io/v3
kind: Workspace
metadata:
name: example-workspace
spec:
namespaceMetadata:
annotations:
owner: team-a
environment: production
cost-center: 12345
labels:
team: team-a
project: example 

Business impact:

This capability is important for the user workflows, as it enables them to integrate with other tools and apply necessary metadata at the time of namespace creation.

Troubleshooting steps:

When testing in the lab I can see that labels are inherited by the namespace, but annotations indeed are not.

Repro steps:

step 1: Create a Rancher environment v2.13.2, or v2.12.x
step 2: Create a new Fleet Workspace and add annotations and labels:
Continuous Delivery > Workspaces > Create New :

step 3:Note that the Fleet Workspace contains the annotations and labels set using the UI:

step 4: Check the corresponding namespace generated in the local cluster:

step 5: Observe that labels the labels set during the workspace creation are present on the generated namespace yaml, but annotations are not:

Workaround:

Is a workaround available and implemented? no

Actual behavior:

Annotations are not passed to the namespace object generated by the fleet workspace creation process

Expected behavior:

There is a way to pass annotations to the namespace object generated by the fleet workspace creation process.

[weyfonk]

A fix for this would live in Rancher; we need to determine whether this issue happens with passing annotations to a namespace created from any workspace, or only for a Fleet-specific workspace.
That information would inform ownership of the fix, and possible transfer of this issue in case it turns out to be a wider Rancher issue.