Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

v1beta2: Class Namespace API change #11500

Open
Tracked by #10852
Danil-Grigorev opened this issue Nov 28, 2024 · 1 comment
Open
Tracked by #10852

v1beta2: Class Namespace API change #11500

Danil-Grigorev opened this issue Nov 28, 2024 · 1 comment
Labels
kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API needs-priority Indicates an issue lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@Danil-Grigorev
Copy link
Member

Danil-Grigorev commented Nov 28, 2024 •
edited
Loading

We need to implement update to the API definitions of the Cluster object in order to properly leverage cross-namespace ClusterClass references.

Proposed design change:

topology:
  class:
    name: ...
    namespace: ...

which will deprecate introduced addition of the classNamespace field:

topology:
  class: …
  classNamespace: ...

/kind api-change
@k8s-ci-robot k8s-ci-robot added kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API needs-priority Indicates an issue lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Nov 28, 2024
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If CAPI contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@Danil-Grigorev Danil-Grigorev mentioned this issue Nov 28, 2024
Open
@chrischdi chrischdi mentioned this issue Dec 13, 2024
Open
56 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API needs-priority Indicates an issue lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@k8s-ci-robot @Danil-Grigorev