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 a warning for MeshExternalServices when mesh requirements are not met #2957

Closed
slonka opened this issue Sep 17, 2024 · 1 comment · Fixed by #2964
Closed

Add a warning for MeshExternalServices when mesh requirements are not met #2957

slonka opened this issue Sep 17, 2024 · 1 comment · Fixed by #2964
Assignees
Labels
kind/feature New feature triage/pending This issue will be looked at on the next triage meeting
Milestone

Comments

@slonka
Copy link
Contributor

slonka commented Sep 17, 2024

Description

MeshExternalService requires:

would be nice to display a warning somewhere in MeshExternalServices tab if these requirements are not met

image

so something like this maybe could work:

image

On the user side when they are not met the MeshExternalService won't work and will error out with:

/app # wget -O- http://mes-https.extsvc.mesh.local/
Connecting to mes-https.extsvc.mesh.local ([::ffff:242.0.0.1]:80)
wget: error getting response: Connection reset by peer

Which is not very helpful, not sure we can do something there 🤔

@slonka slonka added triage/pending This issue will be looked at on the next triage meeting kind/feature New feature labels Sep 17, 2024
@slonka slonka added this to the 2.9.x milestone Sep 17, 2024
@jakubdyszkiewicz
Copy link
Contributor

It does not required routing.zoneEgress: true now. However, it requires mTLS

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature triage/pending This issue will be looked at on the next triage meeting
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants