[helm] deployment url of che
See original GitHub issueIs your enhancement related to a problem? Please describe.
When I deploy che using helm, it’s using multi-host server strategy, but at the end I have URL with
https://che-che.my-domain.com
Describe the solution you’d like
I would expect to have che deployed by default without this double che-che
but more like
https://che.my-domain.com
Describe alternatives you’ve considered
Additional context
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Eclipse Che Helm Charts - Artifact Hub
A Helm chart for deploying Eclipse Che on a Kubernetes. ... When all Eclipse Che containers are running, the Eclipse Che URL is...
Read more >Using Helm
A full URL ( helm install foo https://example.com/charts/foo-1.2.3.tgz ). 'helm upgrade' and 'helm rollback': Upgrading a Release, and Recovering on Failure.
Read more >What is the best deploy code base to use for a custom plugin ...
helm chart in che-plugin-registry is for deploying it on it's own, while charts in che repository is to deploy it together with Che....
Read more >Deploy the GitLab Helm chart
Deploy using Helm. Once you have all of your configuration options collected, we can get any dependencies and run Helm. In this example,...
Read more >Kubernetes Helm Chart Repositories - JFrog
Deploying Helm charts is done using cURL, Wget, JFrog CLI or any of the ways described in Deploying Artifacts. Setting the Default Deployment ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Also, it makes sense to improve URLs of plugin and devfile registries.
Updated: with latest @sparkoo changes URLs are the following:
Issues go stale after
180
days of inactivity.lifecycle/stale
issues rot after an additional7
days of inactivity and eventually close.Mark the issue as fresh with
/remove-lifecycle stale
in a new comment.If this issue is safe to close now please do so.
Moderators: Add
lifecycle/frozen
label to avoid stale mode.