Oh, good question. I was assuming you were using the k8s-test style, so that's the one I suggested modifying. But that same change can be applied to the prod style also. Of course you probably want different IP addresses in each of those two styles if you're planning on deploying both the prod style and one or more of the test style at the same time.
But if you just want the test style to continue to use a temporary, automatically assigned IP, then only modify the prod style.
Oh, and note there is a small difference between those two styles...the test style includes
{...testPodProps} and the prod style does not. testPodProps just modify the terminationGracePeriodSeconds value for Pods to kill them without giving them a chance to shut down. That's typically bad practice for real Pods.
I'm going to do some work work and then later this afternoon I want to create that static IP and see if I can get this puppy going.
Or, it will tell you all your deployments, rather.
I think I did one deploy and then started from scratch and it wouldn't let me use the same name.
I must not have destroyed it first
not that it really matters at this point
I'm sure I can do it in the google console
And renaming in the console is not going to play nicely with Adapt. Adapt uses that deployID very extensively in how it names things and how it can tell which resources it's supposed to manage and which ones it's not supposed to touch.
If you rename anything Adapt creates, Adapt will simply re-create it next time you run update
So if I really care, then I should destroy / clean up everything and start fresh.
@kirkbross_gitlab There is one more thing you may want to look at before you make the changes I suggested. Without making any of the suggested changes, you could use the Google Console to add an Ingress that points to the UrlRouter Service. You'd have to manually manage that outside of Adapt because we don't yet have support for Ingress. But the Ingress would give you the stable IP address you need for DNS and you could also use it to enable HTTPS pretty easily too.
is it necessary to run all the adapt commands from the deploy folder? Like adapt destroy app-test2
Obviously Amplify is very AWS-specific where we're trying to be completely agnostic of what cloud you're using or to not use a cloud at all or to use multiple clouds at once.
And of course, Amplify is much more mature than Adapt right now. We're still pretty early.
Did you get everything working?
all ready to go
(kidding of course)
All I did was change the port to 80 and used the existing IP in my A record
It took a while to generate. It was empty last night for a long time and then I just noticed now that it populated: http://34.95.90.233/
I could probably use that as my A record too.