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 Request]: Decouple Chroma pod port from ingress port #39

Open
tazarov opened this issue Jan 6, 2024 · 0 comments
Open

[Feature Request]: Decouple Chroma pod port from ingress port #39

tazarov opened this issue Jan 6, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@tazarov
Copy link
Contributor

tazarov commented Jan 6, 2024

Describe the problem

Both the ingress port and the pod configurable port share the same value from values chromadb.serverHttpPort

Describe the proposed solution

Move the ingress port to its own config in the values

Alternatives considered

N/A

Importance

nice to have

Additional Information

No response

@tazarov tazarov added the enhancement New feature or request label Jan 6, 2024
@tazarov tazarov assigned tazarov and unassigned tazarov Jan 6, 2024
tazarov added a commit to amikos-tech/chroma-go that referenced this issue Jan 6, 2024
- Added support for Basic and API token

Waiting on amikos-tech/chromadb-chart#39 to be implemented to add the integration tests.

Refs: #2
tazarov added a commit to amikos-tech/chroma-go that referenced this issue Jan 8, 2024
- Added support for Basic and API token

Waiting on amikos-tech/chromadb-chart#39 to be implemented to add the integration tests.

Refs: #2
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

When branches are created from issues, their pull requests are automatically linked.

1 participant