Channels
extensions
rancher-extensions
supermicro-sixsq
ozt
os
one-point-x
rio
onlinemeetup
v16-v21-migration
events
onlinetraining
training-1220
training-0110
training-0124
k3s-contributor
submariner
storage
k3os
windows
ci-cd
theranchcast
rfed_ara
nederlands
ukranian
danish
training-0131
masterclass
training-0207
training-0214
terraform-controller
epinio
phillydotnet
swarm
rancher-wrangler
deutsch
russian
chinese
mesos
français
japanese
arm
longhorn-dev
terraform-provider-rke
service-mesh
azure
gcp
academy
random
elemental
espanol
lima
harvester-dev
portugues
kubernetes
kim
hypper
kubewarden
opni
logging
neuvector-security
rancher-setup
developer
office-hours
mexico
cabpr
rke
vsphere
longhorn-storage
k3s
k3d
terraform-provider-rancher2
fleet
amazon
harvester
rke2
s3gw
hobbyfarm
rancher-desktop
general
Title
b
bright-fireman-42144
08/03/2022, 1:10 AMshrug, ok... I can go through the infra.tf and seeing how it obtains the IP assigned by GCP and crafts the name/IP.
Thought there might be a simple way but after reading everything on-line, it looks way too complicated (although it shouldn't be) so maybe this is the best bet after all.
Thanks for responding. I really appreciate that mate.
🙌 1
I'd love to learn more terraform scripting but in my journey to understand kubernetes (and Rancher) more. I'm beginning to think that SUSE support doc on changing the URL is based on helm v2 and not v3 and that is where my problem is.
this is stupid... looking at the history of this issue and all the work Seb has done and even the SUSE docs aren't up to date to perform this on the SLES rancher server itself.