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

Consider moving management HTTP endpoints to separate HTTP port #7343

Open
snazy opened this issue Aug 7, 2023 · 0 comments · May be fixed by #8207
Open

Consider moving management HTTP endpoints to separate HTTP port #7343

snazy opened this issue Aug 7, 2023 · 0 comments · May be fixed by #8207

Comments

@snazy
Copy link
Member

snazy commented Aug 7, 2023

Quarkus since version 3 allows a separate HTTP endpoint for management endpoints (health, metrics, prometheus), see Quarkus management interface docs.

This allows for example different authentication settings, but especially allows isolation of the management endpoints, to not expose those "to the public".
@snazy snazy mentioned this issue Mar 15, 2024
Merged
snazy added a commit to snazy/nessie that referenced this issue Mar 15, 2024
@snazy
Move management endpoints to separate HTTP port
8d3b2ac 
Quarkus since version 3 allows a separate HTTP endpoint for management endpoints (health, metrics, prometheus), see [Quarkus management interface docs](https://quarkus.io/guides/management-interface-reference).

This allows for example different authentication settings, but especially allows isolation of the management endpoints, to not expose those "to the public".

Fixes projectnessie#7343
@snazy snazy linked a pull request Mar 15, 2024 that will close this issue
Open
snazy added a commit to snazy/nessie-apprunner that referenced this issue Mar 16, 2024
@snazy
Support Quarkus with separate management port
3a04d64 
For projectnessie/nessie#7343
snazy added a commit to snazy/nessie that referenced this issue Mar 16, 2024
@snazy
Move management endpoints to separate HTTP port
501f0df 
Quarkus since version 3 allows a separate HTTP endpoint for management endpoints (health, metrics, prometheus), see [Quarkus management interface docs](https://quarkus.io/guides/management-interface-reference).

This allows for example different authentication settings, but especially allows isolation of the management endpoints, to not expose those "to the public".

Fixes projectnessie#7343
snazy added a commit to snazy/nessie that referenced this issue Mar 16, 2024
@snazy
Move management endpoints to separate HTTP port
7e846be 
Quarkus since version 3 allows a separate HTTP endpoint for management endpoints (health, metrics, prometheus), see [Quarkus management interface docs](https://quarkus.io/guides/management-interface-reference).

This allows for example different authentication settings, but especially allows isolation of the management endpoints, to not expose those "to the public".

Fixes projectnessie#7343
snazy added a commit to snazy/nessie that referenced this issue Mar 16, 2024
@snazy
Move management endpoints to separate HTTP port
a848789 
Quarkus since version 3 allows a separate HTTP endpoint for management endpoints (health, metrics, prometheus), see [Quarkus management interface docs](https://quarkus.io/guides/management-interface-reference).

This allows for example different authentication settings, but especially allows isolation of the management endpoints, to not expose those "to the public".

Fixes projectnessie#7343
snazy added a commit to snazy/nessie that referenced this issue Mar 18, 2024
@snazy
Move management endpoints to separate HTTP port
aef4bc1 
Quarkus since version 3 allows a separate HTTP endpoint for management endpoints (health, metrics, prometheus), see [Quarkus management interface docs](https://quarkus.io/guides/management-interface-reference).

This allows for example different authentication settings, but especially allows isolation of the management endpoints, to not expose those "to the public".

Fixes projectnessie#7343
snazy added a commit to projectnessie/nessie-apprunner that referenced this issue Mar 18, 2024
@snazy
Support Quarkus with separate management port (#317)
2852c15 
For projectnessie/nessie#7343
snazy added a commit to snazy/nessie that referenced this issue Mar 18, 2024
@snazy
Move management endpoints to separate HTTP port
e34ac9d 
Quarkus since version 3 allows a separate HTTP endpoint for management endpoints (health, metrics, prometheus), see [Quarkus management interface docs](https://quarkus.io/guides/management-interface-reference).

This allows for example different authentication settings, but especially allows isolation of the management endpoints, to not expose those "to the public".

Fixes projectnessie#7343
snazy added a commit to snazy/nessie that referenced this issue Mar 21, 2024
@snazy
Move management endpoints to separate HTTP port
279fe8f 
Quarkus since version 3 allows a separate HTTP endpoint for management endpoints (health, metrics, prometheus), see [Quarkus management interface docs](https://quarkus.io/guides/management-interface-reference).

This allows for example different authentication settings, but especially allows isolation of the management endpoints, to not expose those "to the public".

Fixes projectnessie#7343
snazy added a commit to snazy/nessie that referenced this issue Mar 21, 2024
@snazy
Move management endpoints to separate HTTP port
1932b36 
Quarkus since version 3 allows a separate HTTP endpoint for management endpoints (health, metrics, prometheus), see [Quarkus management interface docs](https://quarkus.io/guides/management-interface-reference).

This allows for example different authentication settings, but especially allows isolation of the management endpoints, to not expose those "to the public".

Fixes projectnessie#7343
snazy added a commit to snazy/nessie that referenced this issue Mar 21, 2024
@snazy
Move management endpoints to separate HTTP port
accf37f 
Quarkus since version 3 allows a separate HTTP endpoint for management endpoints (health, metrics, prometheus), see [Quarkus management interface docs](https://quarkus.io/guides/management-interface-reference).

This allows for example different authentication settings, but especially allows isolation of the management endpoints, to not expose those "to the public".

Fixes projectnessie#7343
snazy added a commit to snazy/nessie that referenced this issue Mar 28, 2024
@snazy
Move management endpoints to separate HTTP port
f2d0e7b 
Quarkus since version 3 allows a separate HTTP endpoint for management endpoints (health, metrics, prometheus), see [Quarkus management interface docs](https://quarkus.io/guides/management-interface-reference).

This allows for example different authentication settings, but especially allows isolation of the management endpoints, to not expose those "to the public".

Fixes projectnessie#7343
snazy added a commit to snazy/nessie that referenced this issue Apr 30, 2024
@snazy
Move management endpoints to separate HTTP port
8d7cb3f 
Quarkus since version 3 allows a separate HTTP endpoint for management endpoints (health, metrics, prometheus), see [Quarkus management interface docs](https://quarkus.io/guides/management-interface-reference).

This allows for example different authentication settings, but especially allows isolation of the management endpoints, to not expose those "to the public".

Fixes projectnessie#7343
snazy added a commit to snazy/nessie that referenced this issue Apr 30, 2024
@snazy
Move management endpoints to separate HTTP port
5ce6ebc 
Quarkus since version 3 allows a separate HTTP endpoint for management endpoints (health, metrics, prometheus), see [Quarkus management interface docs](https://quarkus.io/guides/management-interface-reference).

This allows for example different authentication settings, but especially allows isolation of the management endpoints, to not expose those "to the public".

Fixes projectnessie#7343
snazy added a commit to snazy/nessie that referenced this issue Apr 30, 2024
@snazy
Move management endpoints to separate HTTP port
331bc77 
Quarkus since version 3 allows a separate HTTP endpoint for management endpoints (health, metrics, prometheus), see [Quarkus management interface docs](https://quarkus.io/guides/management-interface-reference).

This allows for example different authentication settings, but especially allows isolation of the management endpoints, to not expose those "to the public".

Fixes projectnessie#7343
snazy added a commit to snazy/nessie that referenced this issue Apr 30, 2024
@snazy
Move management endpoints to separate HTTP port
3c02065 
Quarkus since version 3 allows a separate HTTP endpoint for management endpoints (health, metrics, prometheus), see [Quarkus management interface docs](https://quarkus.io/guides/management-interface-reference).

This allows for example different authentication settings, but especially allows isolation of the management endpoints, to not expose those "to the public".

Fixes projectnessie#7343
snazy added a commit to snazy/nessie that referenced this issue Apr 30, 2024
@snazy
Move management endpoints to separate HTTP port
477cd49 
Quarkus since version 3 allows a separate HTTP endpoint for management endpoints (health, metrics, prometheus), see [Quarkus management interface docs](https://quarkus.io/guides/management-interface-reference).

This allows for example different authentication settings, but especially allows isolation of the management endpoints, to not expose those "to the public".

Fixes projectnessie#7343
snazy added a commit to snazy/nessie that referenced this issue Apr 30, 2024
@snazy
Move management endpoints to separate HTTP port
bf1a82e 
Quarkus since version 3 allows a separate HTTP endpoint for management endpoints (health, metrics, prometheus), see [Quarkus management interface docs](https://quarkus.io/guides/management-interface-reference).

This allows for example different authentication settings, but especially allows isolation of the management endpoints, to not expose those "to the public".

Fixes projectnessie#7343
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

Successfully merging a pull request may close this issue.

Move management endpoints to separate HTTP port snazy/nessie
1 participant
@snazy