Run server in IBM Cloud about pityoulish HOT 8 CLOSED

Registering for a Pay-as-you-go account got me $200 credit within the first 30 days. Should be plenty, with network traffic being the only paid service I'm planning to make use of. 30 days suffice to figure out how to run the server in Cloud, but the student sessions will be afterwards. We'll see.

from pityoulish.

I'm installing the IBM Cloud developer tools locally for trying out.
Eventually, I'd like to have GitHub workflows (actions) for deploying.

grrr They're installing docker, while I'm using podman. Tough luck.

from pityoulish.

The images I build on my workstation with podman are not visible to docker and vice versa.
Setting up a GitHub workflow to push an image into IBM Cloud Registry will be a priority.

Maybe afterwards, I can get rid of the container-registry plugin and docker on my workstation again.

from pityoulish.

Here's how to authenticate against the IBM Cloud Container Registry for pushing images:
https://cloud.ibm.com/docs/Registry?topic=Registry-registry_access#registry_access_apikey_auth_other
The trick is to use "iamapikey" as the user name.

I should be able to push directly with podman from my workstation, or promote images from GitHub to IBM Cloud with skopeo in a GitHub workflow.

from pityoulish.

Pushing from my workstation works on the second attempt. It's "iamapikey", not "ibmapikey" ;-)

from pityoulish.

I got the pod running, and could connect to the Socket server port.

The Java RMI exercise requires some more effort. The ports in the container must be the same as those outside. And the external IP address of the worker node needs to be passed as hostname to Java RMI. That's because the internal port number and provided hostname appears in the stubs that Java RMI returns.

from pityoulish.

I've made the server ports and hostname configurable through environment variables.
But somehow, I cannot get the port mapping to work - not even for the Socket server port anymore.
Getting tired now... will try another day.

from pityoulish.

Duh... it works better when I use the external IP address of the worker node.

kubectl describe nodes | grep IP

  InternalIP:  10.x.y.z
  ExternalIP:  184.x.y.z

Got it working now for both Sockets and Java RMI. Still have to write it down though.

from pityoulish.