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

Look at all namespace unless overridden #370

Merged
merged 1 commit into from
Aug 13, 2024
Merged

Conversation

willemm
Copy link

@willemm willemm commented Aug 1, 2024

Description

Removes the default setting where not specifying the kubernetes-namespace defaults it to whatever namespace the controller is running in

Why is this needed

tinkerbell/cluster-api-provider-tinkerbell#385

With this change, you can create hardware resources in different namespaces.

Fixes: #

How Has This Been Tested?

We have a cluster-api setup where we're adding some bare metal nodes to a cluster.
With this change, the hardware resources that previously only worked from the tink-system namespace now also work from a different namespace. I also tested the old working setup and that still works as well.
The change is minimal, so it shouldn't impact much.
I haven't tested if the --kubernetes-namespace setting would restrict it to one namespace again.

How are existing users impacted? What migration steps/scripts do we need?

The Role and RoleBinding resources in the helm chart (or whatever other deployment method) need to be changed to ClusterRole and ClusterRoleBinding, otherwise it will not be able to read from the other namespaces.

Otherwise no migration steps are needed, unless users have multiple instances of hegel running in different namespaces, or have another reason why they specifically don't want resources in a different namespace to be picked up.

This could probably be avoided by having the helm chart add the kubernetes-namespace argument to the deployment and have it pull the value from the downward api somehow, but it seems to me that having it default to looking at all namespaces would be preferrable for most users.

Checklist:

I have:

  • updated the documentation and/or roadmap (if required)
  • added unit or e2e tests
  • provided instructions on how to upgrade

Copy link

codecov bot commented Aug 1, 2024

Codecov Report

Attention: Patch coverage is 0% with 2 lines in your changes missing coverage. Please review.

Project coverage is 56.34%. Comparing base (d8923f9) to head (733cb22).
Report is 10 commits behind head on main.

Files Patch % Lines
internal/backend/kubernetes/backend.go 0.00% 1 Missing and 1 partial ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #370      +/-   ##
==========================================
+ Coverage   55.60%   56.34%   +0.74%     
==========================================
  Files          27       27              
  Lines         633      630       -3     
==========================================
+ Hits          352      355       +3     
+ Misses        267      259       -8     
- Partials       14       16       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@jacobweinstock jacobweinstock added the ready-to-merge Signal to Mergify to merge the PR. label Aug 13, 2024
@mergify mergify bot merged commit 8936515 into tinkerbell:main Aug 13, 2024
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready-to-merge Signal to Mergify to merge the PR.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants