feat: User service K8S ingresses for reverse proxy routing #1941
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lostbean
approved these changes
Dec 14, 2023
...ib/lib/backend_impls/kubernetes/kubernetes_kurtosis_backend/shared_helpers/shared_helpers.go
Outdated
Show resolved
Hide resolved
..._impls/kubernetes/kubernetes_kurtosis_backend/user_services_functions/start_user_services.go
Show resolved
Hide resolved
h4ck3rk3y
pushed a commit
that referenced
this pull request
Dec 15, 2023
## Description: Similar to how we are adding Traefik labels for user services on Docker, we are adding a K8S ingress for each user service with a path per HTTP port so HTTP traffic can be routed to them. ## Is this change user facing? NO ## References (if applicable): #1871
github-merge-queue bot
pushed a commit
that referenced
this pull request
Dec 15, 2023
## Description: The user service K8S ingress labels need to be set properly so the ingress can be found during retrieval and deletion operations. ## Is this change user facing? NO ## References (if applicable): #1941
github-merge-queue bot
pushed a commit
that referenced
this pull request
Dec 18, 2023
🤖 I have created a release *beep* *boop* --- ## [0.85.49](0.85.48...0.85.49) (2023-12-18) ### Features * add production mode to k8s ([#1963](#1963)) ([b0e27e6](b0e27e6)) * persistent volumes work on multi node k8s clusters ([#1943](#1943)) ([b2fd9f2](b2fd9f2)) * User service K8S ingresses for reverse proxy routing ([#1941](#1941)) ([c37dd7f](c37dd7f)) ### Bug Fixes * adding remove logs aggregator container function when it already exists ([#1974](#1974)) ([5d74d16](5d74d16)) * Do not fail if the Traefik config dir path already exists ([#1966](#1966)) ([4e6f7d7](4e6f7d7)) * ignore the current status of the service during a start/stop ([#1965](#1965)) ([1c4863f](1c4863f)) * refactor the emui components to the shared package ([#1959](#1959)) ([a406973](a406973)) * Set the user service K8S ingress labels so it can be found ([#1962](#1962)) ([9cc5f77](9cc5f77)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). --------- Co-authored-by: kurtosisbot <[email protected]> Co-authored-by: leoporoli <[email protected]>
github-merge-queue bot
pushed a commit
that referenced
this pull request
Jan 2, 2024
## Description:
Create engine K8S ingress for the REST API port so we can interact with
the API via Traefik. The `Host` header is set to `engine`.
Tested with k3d locally:
```
curl -i http://localhost:9730/engine/info -H "Host: engine"
HTTP/1.1 200 OK
...
{"engine_version":"ae7579"}
```
## Is this change user facing?
NO
## References (if applicable):
#1941
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
Similar to how we are adding Traefik labels for user services on Docker, we are adding a K8S ingress for each user service with a path per HTTP port so HTTP traffic can be routed to them.
Is this change user facing?
NO
References (if applicable):
#1871