Skip to content

[Suggest]: Remove Ingress from Jaeger Operator's simplest Profile #2520

Open

Description

Requirement

According to the current documentation for getting started with the Jaeger Operator, users are advised to deploy an ingress-controller to access the Jaeger UI. This approach has caused some confusion and operational hurdles for users. Especially for beginners.

#1174
#2515

Problem

  • The approach to exposing Kubernetes services has changed considerably over the years. While Ingress is still relevant, it may not be the preferred choice for the majority.
  • The variance in ingress controller implementations makes it challenging to support and test all of them. And should not be the scope of this project.
  • Exposing services outside of the cluster might not be advisable for all users, especially those just starting with Kubernetes.

Proposal

I propose the following changes to the Jaeger Operator's simplest profile and Getting started guide

  • Remove the Ingress setup from the simplest profile configuration.
  • Introduce kubectl port-forward as the recommended method for accessing the Jaeger UI in the simplest profile.

Open questions

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions