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

Add support for multiple paths in Ingresses #33

Open
hazim1093 opened this issue Jul 17, 2018 · 4 comments
Open

Add support for multiple paths in Ingresses #33

hazim1093 opened this issue Jul 17, 2018 · 4 comments

Comments

@hazim1093
Copy link
Member

Currently forecastle only picks apps and associates them with the first path in their ingress. We need to add functionality for forecastle to consider ingresses with multiple paths

@Nuru
Copy link

Nuru commented Aug 2, 2019

I would also like to have the ability to explicitly specify the linked path via an annotation. It is an issue right now in that I have an app where I want the Forecastle icon to take the user to https://host/console/view but it only goes to https://host/

This is somewhat similar to, but different than, the nginx-ingress annotation nginx.ingress.kubernetes.io/app-root. In this case, I do not want to generally redirect /, I just want to specify the path for the Forecastle link.

@waseem-h
Copy link
Contributor

waseem-h commented Aug 5, 2019

This issue actually focuses on multiple paths in a single ingress. But your comment also makes sense as the root app is not always at /. I will see if we can add support for that @Nuru

@waseem-h
Copy link
Contributor

waseem-h commented Aug 5, 2019

I have created a new ticket for your comment @Nuru. Its #67. Feel free to comment on it

@rasheedamir
Copy link
Member

We will need to add support multiple icons

@rasheedamir rasheedamir changed the title Add Support for multiple paths in Ingresses Add support for multiple paths in Ingresses Sep 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants