Skip to content

add note about resources#296

Open
pwright wants to merge 1 commit into
skupperproject:mainfrom
pwright:resource-note
Open

add note about resources#296
pwright wants to merge 1 commit into
skupperproject:mainfrom
pwright:resource-note

Conversation

@pwright

@pwright pwright commented Jun 17, 2026

Copy link
Copy Markdown
Member

No description provided.

@pwright pwright requested a review from hash-d June 17, 2026 13:28
- A Secret containing a signing CA for site linking

The output resources generated by the controller belong to the
`internal.skupper.io` API group. The controller acts as the field

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure what API group stands for, in this context. Also, a resource may have several field managers, for different sets of fields.

There are things, such as adding new labels or changing non-skupper labels that the user may be allowed to do.

I think I originally suggested mentioning that skupper works as a field manager for those resources, but on a second thought that's more noise than signal.

Perhaps we could tell them simply that they're allowed to add or change their own entries on metadata.annotations and metadata.labels (but not skupper's, as identified with internal.skupper.io), and that any changes done within spec.* are subject to be overwritten by the controller.

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.

2 participants