-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
[MetalLB] Remove unused resources #10004
[MetalLB] Remove unused resources #10004
Conversation
This will fix MetalLB deploy
Hi @eugene-marchanka. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
Nice cleanup, the places of /ok-to-test |
I'm still getting weird errors when deploying. |
The scope of this pull request is changed after my review. /approve cancel |
reverted |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@eugene-marchanka Ok all good after revert, @oomichi wilm probably lgtm when dropping by 👍
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: eugene-marchanka, floryut The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
I'm getting the following error trying to use this branch:
My addons.yml has the following content for MetalLB: metallb_protocol: "bgp"
metallb_config:
address_pools:
primary:
ip_range:
- 10.5.0.0/16
auto_assign: true
layer3:
metallb_peers:
peer1:
peer_address: 10.0.50.1
peer_asn: 65000
my_asn: 65001
address_pool:
- primary Could be my issue though if I'm doing something wrong here |
With
|
I'm very sorry but unfortunately issues you are describing are out of this PR scope. |
Thank you that is what I assumed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for making this simple.
/lgtm
@@ -45,7 +39,7 @@ | |||
src: "{{ item }}.j2" | |||
dest: "{{ kube_config_dir }}/{{ item }}" | |||
mode: 0644 | |||
with_items: ["metallb.yml", "metallb-config.yml", "pools.yaml", "layer2.yaml", "layer3.yaml"] | |||
with_items: ["metallb.yml", "pools.yaml", "layer2.yaml", "layer3.yaml"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A nice catch for non-existent metallb-config.yml.j2 under ./roles/kubernetes-apps/metallb/templates/
This was already being addressed here: #9995 |
* Fix MetalLB deploy This will fix MetalLB deploy * Remove `metallb_ip_range` check * Remove missing `metallb-config.yml` * fix template name * make deployment of layer3 conditional * revert * revert
What type of PR is this?
/kind bug
What this PR does / why we need it:
Fix cluster deployment when MetalLB settings are specified
Which issue(s) this PR fixes:
Fixes #10003
Special notes for your reviewer:
Does this PR introduce a user-facing change?: