G'day,
The flink and the dashboard are running in k8s and I am not on the same
network.
We don't have a VPN into the cluster. (Don't ask)
I am not sure how I would access the dashboard without having a port
forward.
On 28/06/2023 14:39, Schwalbe Matthias wrote:
Good Morning Mike,
As a quick fix, sort of, you could use an Ingress on nginx-ingress
(instead of the port-forward) and
Add a sub_filter rule to patch the HTML response.
I use this to add a <base …/> tag to the header and for the
Flink-Dashboard I experience no glitches.
As to point 3. … you don’t need to expose that Ingress to the
internet, but only to the node IP, so it becomes visible only within
your network, … there is a number of ways doing it
I could elaborate a little more, if interested
Hope this helps
Thias
*From:*Mike Phillips <mike.phill...@intellisense.io>
*Sent:* Wednesday, June 28, 2023 3:47 AM
G'day Alex,
Thanks!
1 - hmm.... maybe beyond my capabilities presently
2 - Yuck! :-) Will look at this
3 - Not possible, the dashboards are not accessible via the internet,
so we use kube and port forward, URL looks like
http://wobbegong:30000/ the port changes
4 - I think this requires the dashboard be internet accessible?
On Tue, 27 Jun 2023 at 17:21, Alexander Fedulov
<alexander.fedu...@gmail.com> wrote:
Hi Mike,
no, it is currently hard-coded
https://github.com/apache/flink/blob/master/flink-runtime-web/web-dashboard/src/app/app.component.html#L23
Your options are:
1. Contribute a change to make it configurable
2. Use some browser plugin that allows renaming page titles
3. Always use different ports and bookmark the URLs accordingly
4. Use an Ingress in k8s
Best,
Alex
On Tue, 27 Jun 2023 at 05:58, Mike Phillips
<mike.phill...@intellisense.io> wrote:
G'day all,
Not sure if this is the correct place but...
We have a number of flink dashboards and it is difficult to
know what dashboard we are looking at.
Is there a configurable way to change the 'Apache Flink
Dashboard' heading on the dashboard?
Or some other way of uniquely identifying what dashboard I am
currently looking at?
Flink is running in k8s and we use kubectl port forwarding to
connect to the dashboard so we can't ID using the URL
