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

Remove outdated helm install information around accessing ecosystem services #836

Closed

Conversation

eamansour
Copy link
Member

Some parts of the ecosystem helm installation process are outdated and is confusing to users. These include:

  • Mentioning that users can provide an IP address for the externalHostname value - This is no longer true since Ingress doesn't allow IP addresses, which would cause users to encounter errors
  • Mentioning that Ingress is "enabled by default", implying that it could be disabled - This is no longer the case since access to services via NodePorts has been completely replaced with Ingress, so the services can only be accessed via Ingress now
  • Mentioning that the ecosystem's use of Dex is still under development - This has been stable for several releases now, so that line can be removed
  • Mentioning that the bootstrap needs to be "reconfigured" - This isn't true since we already mention the bootstrap how the bootstrap can be accessed in the previous section

The changes in this PR resolve the above issues.

…ervices

Signed-off-by: Eamonn Mansour <47121388+eamansour@users.noreply.github.com>
Signed-off-by: Eamonn Mansour <47121388+eamansour@users.noreply.github.com>
@eamansour eamansour closed this Oct 10, 2024
@eamansour
Copy link
Member Author

Closed in favour of #837

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.

1 participant