Yep, I can see your Hello World. No, you can't put the port number in a DNS A record. So if you put 34.121.219.90 in your A record, you would have to access this particular setup at http://yourdomain.com:8080
However, you can change the port that the Hello World service exposes from 8080 to the typical http port, 80.
Then you could just access http://yourdomain.com
The one thing to be careful of here though is the IP address that GKE automatically assigns to that Service may not stay the same forever. I'm actually not sure what guarantees that GKE makes about the longevity of that IP address. So the issue might be that everything works well for days or months, then GKE moves something around automatically, which assigns a new IP and suddenly http://yourdomain.com is pointing to the wrong IP now.
That long-term stability of address is what you're getting by assigning a static IP.
Are you building an option to create a static IP in the deploy?
I didn't see any yaml files so I presume they are behind the scenes.
We don't have a component to automatically create a static IP address for you, but it's definitely on our to do list. In the meantime, you can follow step 2(a) on [the Google tutorial(https://cloud.google.com/kubernetes-engine/docs/tutorials/configuring-domain-name-static-ip#gcloud) to get the IP address.
Then, edit the style sheet (styles.tsx)...
Oops, sent too early...we just need to add the IP to the existing Service for UrlRouter
{Service}
{Adapt.rule<ServiceProps>(({ handle, ...props }) => {
if (props.key === "UrlRouter") {
return <ServiceDeployment config={config} {...props} {...testPodProps} serviceProps={{ loadBalancerIP: "35.236.65.222" }} />;
} else {
return <ServiceDeployment config={config} {...props} {...testPodProps} />;
}
})}
Oops, replace that IP address with the one you got when you created your static IP
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.