This message was deleted.
# general
a
This message was deleted.
a
@creamy-pencil-82913 @big-hydrogen-97240
a
You can customise the rancher helm chart not to deploy an ingress object, so technically you could expose the rancher service via a load balancer service type
a
could you please share any article on this,
yes i agree with you. cusomizing this will not use hostname, and start using public ip directly
Set
ingress.enabled
to false
a
does it need to be set while installing rancher manager using helm?
or while adding it to repo?
a
While installing or you can modify the existing helm install with updated values
a
for example, like this helm install rancher rancher-latest/rancher \ --namespace cattle-system \ --set ingress.enable=false\ --set bootstrapPassword=admin
does it work
?
a
Like that, yes, you'll need to change the rancher service type afterwards as it's currently not customisable from the helm chart
a
can we take a quick remote if you’re okay with. im stuck with this and challenge in moving forward as its my first deploying rancher using helm
let me send zoom.
a
I can't atm as I'm away from my desk
a
ok,
let me know when you back for 5 mins. will do
a
I'd try what's already discussed, it should be straight forward
a
ok, service type needs to be load balancer?
a
Or nodeport, so you to access it externally
a
ok. let me try
David, I have reinstalled helm with ingres enabled value to be true and changed rancher service to Nodeport
but now i get the error 404 not found while accessing the public ip of the machine
attle-system rancher NodePort 10.43.57.69 <none> 8030760/TCP,44330165/TCP 2m22s
a
Are you connecting to the correct port?
a
yes
connecting with 30760
with http
and also https, 30165
a
Hmm. Will need to check next time I have access to a cluster
a
sure David.
David, UI works now
how do we find the password we provided during installation if we are not sure
for the UI
a
You can get values from helm