Skip to content
This repository has been archived by the owner on Feb 15, 2025. It is now read-only.

223 - Expose metallb lb outside the network #241

Merged
merged 2 commits into from
Nov 7, 2023

Conversation

CollectiveUnicorn
Copy link
Contributor

Adds Kustomizations that will create static nodeports that can be exposed by the k3d lb

…etal deployment

* admin and tenant ingress gateways are updated to accept incoming traffic from "*"
* services updated to have static "nodeport" values to facilitate routing via the
k3d loadbalancer
@CollectiveUnicorn CollectiveUnicorn merged commit 1cbefb7 into main Nov 7, 2023
@justinthelaw justinthelaw deleted the 223-expose-lb-local branch November 7, 2023 23:40
andrewrisse pushed a commit that referenced this pull request Apr 18, 2024
* Adds kustomization to update ingress gateways and services for bare metal deployment

* admin and tenant ingress gateways are updated to accept incoming traffic from "*"
* services updated to have static "nodeport" values to facilitate routing via the
k3d loadbalancer

* Adds changes to successfully deploy service updates via zarf
andrewrisse pushed a commit that referenced this pull request Apr 18, 2024
* Adds kustomization to update ingress gateways and services for bare metal deployment

* admin and tenant ingress gateways are updated to accept incoming traffic from "*"
* services updated to have static "nodeport" values to facilitate routing via the
k3d loadbalancer

* Adds changes to successfully deploy service updates via zarf
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants