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

[Feature]: Use a namespace to deploy the App with K8s #127

Open
2 tasks done
orousseau49170 opened this issue Jan 21, 2025 · 2 comments
Open
2 tasks done

[Feature]: Use a namespace to deploy the App with K8s #127

orousseau49170 opened this issue Jan 21, 2025 · 2 comments
Labels
enhancement New feature or request

Comments

@orousseau49170
Copy link
Contributor

Problem Statement

I have tested the deployment of the app-simulator with Kubernetes.
It would be nice to use a namespace to have all 3 pods in the same ns (instead of default)

Proposed Solution

something like:
kind: Namespace
metadata:
name: app-simulator

Alternatives Considered

No response

Additional Context

No response

Checklist

@orousseau49170 orousseau49170 added enhancement New feature or request triage This issue or pull request requires triaging labels Jan 21, 2025
@svrnm svrnm removed the triage This issue or pull request requires triaging label Jan 21, 2025
@svrnm
Copy link
Member

svrnm commented Jan 21, 2025

good point! When I ran it myself I always added the --namespace to the CLI, but having the option to provide the namespace would be great, or maybe even default to one, @noMoreCLI wdyt?

@svrnm
Copy link
Member

svrnm commented Jan 21, 2025

Note, that compose does not have a namespace but a name which is close enough that I argue we can have a global "namespace" (or "name"?) attribute:

https://docs.docker.com/reference/compose-file/version-and-name/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants