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.

Sign up for GitHub

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

Jump to bottom

Ingress controller #80

Closed
migmartri opened this issue Dec 4, 2017 · 2 comments
Closed

Ingress controller #80

migmartri opened this issue Dec 4, 2017 · 2 comments

Comments

@migmartri
Copy link
Contributor

Is there any way to configure the ingress controller service to for example be exposed via ELB/NodePort at deployment time? If not, what's the recommended way to do it?

Would it make sense to allow user to choose an existing an existing ingress controller?
@prydonius
Copy link
Contributor

Currently no, but we will make it configurable later, but IMO we should wait until we have a good authentication model.

Using an existing ingress controller is an interesting idea, the only issue is that some controllers don't fully support the annotations we might need. How useful do you think this would be?

prydonius pushed a commit to prydonius/kubeapps that referenced this issue Mar 5, 2018
@evanlouie
Fix: Empty Tables (vmware-tanzu#80)
781b7e7 
* Plans Table

- Listing ServiceClass plans as table instead of cards
- Changed Plan Provision button to be smaller to fit table better
- Moved AddBindingButton to InstanceView folder

* Fix: messaging for empty tables
@prydonius
Copy link
Contributor

Closing as we no longer use an Ingress controller and just deploy a single nginx pod.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@migmartri @prydonius