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.

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

Can I use pools in different namespaces ? #1071

Closed
huaqing1994 opened this issue Jun 29, 2023 · 5 comments
Closed

Can I use pools in different namespaces ? #1071

huaqing1994 opened this issue Jun 29, 2023 · 5 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. needs-triage Indicates an issue lacks a `triage/foo` label and requires one. question Further information is requested triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@huaqing1994
Copy link

User Story

As a developer I would like to use an IPPool in other namespace in CAPM3 for Metal3Clusters in different namespaces can be associated with a common IPPool.

Detailed Description

I found that when filling IPPool in Metal3DataTemplate, you can only fill in name, not namespace.
The need to allow IPPools with different namespaces should be reasonable, like corev1.SecretReference and corev1.ObjectReference.
I don't know what the reason for this design is, if anyone knows, thanks for letting me know. And I hope this can be improved in the future.

Thank you all! :)

/kind feature

@metal3-io-bot metal3-io-bot added kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue lacks a `triage/foo` label and requires one. labels Jun 29, 2023
@metal3-io metal3-io deleted a comment from metal3-io-bot Jul 5, 2023
@Rozzii Rozzii added the question Further information is requested label Jul 5, 2023
@Rozzii
Copy link
Member

Rozzii commented Jul 5, 2023

The feature you describe here @huaqing1994 makes sense, but as far as I know k8s operators could be configured to watch either 1 namespace or all namespaces thus the use-case you describe where the operator is able to selectively access resources in different namespaces might not be supported. But I am not an expert in this topic so I hope others from the community can add extra info here.

@Rozzii Rozzii added the triage/needs-information Indicates an issue needs more information in order to work on it. label Jul 5, 2023
@mboukhalfa
Copy link
Member

There might be also issue with ownerReference since it can only point to resource in the same namespace or cluster-wide resource as already investigated here
#795 (comment)

@metal3-io-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues will close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@metal3-io-bot metal3-io-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 3, 2023
@metal3-io-bot
Copy link
Contributor

Stale issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle stale.

/close

@metal3-io-bot
Copy link
Contributor

@metal3-io-bot: Closing this issue.

In response to this:

Stale issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle stale.

/close

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/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. needs-triage Indicates an issue lacks a `triage/foo` label and requires one. question Further information is requested triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
None yet
Development

No branches or pull requests

4 participants