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

How do we host services that should not expose an external enpoint? #220

Open
LucaLanziani opened this issue Oct 12, 2023 · 1 comment
Open
Assignees

Comments

@LucaLanziani
Copy link
Member

This is mostly a research task to see if it's possible to have a knative service that doesn't expose a public endpoint.

@zaremba-tomasz zaremba-tomasz self-assigned this Oct 12, 2023
@zaremba-tomasz
Copy link
Contributor

According to docs this can be done by just labelling knative service as shown below:

  1. Current initium deployment
    Image

  2. After adding a label
    Image

@LucaLanziani adding this feature looks like a low hanging fruit but it seems pretty useful, do we want to implement this?

Potential implementation:

  1. Extend initium init config by adding a flag defining whether app/service should be private (public by default).
  2. Persisting user choice in .initium config file.
  3. Modification of service.yaml.tmpl to add the knative label depending on the user's choice.

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

No branches or pull requests

3 participants