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 ingress configuration #1213

Merged
merged 2 commits into from Jul 11, 2022
Merged

add ingress configuration #1213

merged 2 commits into from Jul 11, 2022

Conversation

MonsterChenzhuo
Copy link
Contributor

Problem solved:In most cases enterprise k8s clusters/servers, are firewalled and will only expose port 80 of the master node, the rest of the ports need to be accessed through nginx domain hops, which results in the flink task web interface not being available for streamx link

Add two ways to increase the ingres configuration.

  1. By default, the user can just specify the domain name, and the access address is by default: domain name+namespace+clusterId
  2. You are very familiar with ingress and know what you want to do, you can submit a yaml of ingress to do the configuration of ingress

@wolfboys
Copy link
Member

LGTM

@wolfboys wolfboys merged commit ac78718 into apache:dev Jul 11, 2022
@chenshaojin
Copy link
Contributor

I reviewed the source code and the second approach does not have a frontend interface, right? The only way is through swagger or postman. @MonsterChenzhuo

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

Successfully merging this pull request may close these issues.

None yet

3 participants