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

Allow HTTP for Console #13

Open
mjnagel opened this issue Sep 3, 2021 · 2 comments
Open

Allow HTTP for Console #13

mjnagel opened this issue Sep 3, 2021 · 2 comments
Labels
enhancement New feature or request

Comments

@mjnagel
Copy link

mjnagel commented Sep 3, 2021

Is your feature request related to a problem?

Currently the default setup using ClusterIP service type creates a service with HTTPS management port and the comms port. When using an ingress method like Istio without a passthrough gateway the HTTP 8081 port needs to be exposed to have the service mesh handle HTTPS.

Describe the solution you'd like

Add an additional "toggle" in the spec to enable the HTTP 8081 port to be exposed.

Additional context

I reviewed the resource spec document to see if there was an existing option but did not see anything. If there is definitely point me to it and I can test it out. Thanks!

@mjnagel mjnagel added the enhancement New feature or request label Sep 3, 2021
@wfg
Copy link
Collaborator

wfg commented Sep 7, 2021

You're right--there's no option to do this today. Thanks for the feedback @mjnagel.

@pfox1969
Copy link
Contributor

pfox1969 commented Sep 28, 2021

This leads into having the ability to modify the twistlock.cfg and the resulting yamls from twistcli console/defender export kubernetes prior to calling ansible's k8s Console / Defender creation.

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

3 participants