Why are we using WildFly 32? Shouldn't we use WildFly 34?

IMO we should name this something like GettingStartedClient or GettingStartedEndpointClient.

I'm not sure I follow this and it seems a bit odd to me.

@jamezp I changed the wording ... I was basically trying to say that the tests that were included with the archetype wouldn't be relevant anymore since we are using service to service invocation

I think we need to be more descriptive here and state something like:

Update the artifactId to <artifactid>simple-microservice-server</artifactId>.

@jamezp tnks, changed

Is there a reason we don't use the wildfly-maven-plugin to generate the Dockerfile/image?

@jamezp thank you for the suggestion ... if you agree I'll add a note that tells about this option (https://docs.wildfly.org/wildfly-maven-plugin/releases/5.1/image-mojo.html) ... throughout the guides I tried to keep it stupid simple and just use the minimal set of tools/configurations the user might be already familiar with ... for example I didn't use glow ... my fear is that the reader might abandon the reading if feeling overwhelmed with too many tools/configurations ... I also wanted to show what's going on under the hood to show it's actually simple stuff

The hello needs to be removed at the end since the GettingStartedEndpointInterface includes @Path("/hello").

@jamezp great catch! Thank you

Where do I create this file? I assume in simple-microservice-server.

I added instructions on where to create kubernetes files

This fails if Kubernetes is not running. We should add a step for minikube start.

Again, I assume this needs to happen in the client, but it's not really described. Or I guess in any directory, but seems it should specify.

I added a link to https://kubernetes.io/docs/concepts/services-networking/service/ which should clarify this statement

This doesn't work for me. It's possible I don't have minikube started correctly. I just did minikube start.

If you don't see a command prompt, try pressing enter.
curl: (6) Could not resolve host: xxx
Hello 'pippo'.pod "curl-my-jaxrs-app-server" deleted

I just deleted and re-installed a fresh minikube .... perhaps the two dashed get copied to some other character ...

try:

kubectl run --rm -it --tty curl-simple-microservice-server --image=curlimages/curl --restart=Never -- http://simple-microservice-server-service:8080/hello/pippo

it worked for me ....

These should be 35.0.0.Final or we could just leave the version off and use channels which will grab the latest version of WildFly.

I upgraded the versions and added #724 ... btw "channels" would be yet another concept an inexperienced reader might be confused by ... that is why in #724 I also added the "adding a note about channels" option.

This should be 5.1.1.Final

Why are we doing this? Should the tests just be removed from the example if we remove them here?

This example is about service ti service invocation and, unless we start both services in the same test, it would fail... perhaps we could leave the tests in the "server" service ...

It's possible I've missed something, but this step fails for me with:

If you don't see a command prompt, try pressing enter.


curl: (28) Failed to connect to simple-microservice-server-service port 8080 after 130287 ms: Could not connect to server
pod "curl-simple-microservice-server" deleted
pod default/curl-simple-microservice-server terminated (Error)

That's supposed to work if the following have already been deployed:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: simple-microservice-server-deployment
  labels:
    app: simple-microservice-server
spec:
  replicas: 1
  selector:
    matchLabels:
      app: simple-microservice-server
  template:
    metadata:
      labels:
        app: simple-microservice-server
    spec:
      containers:
        - name: simple-microservice-server
          image: quay.io/tborgato/simple-microservice-server
          ports:
            - containerPort: 8080
            - containerPort: 9990
          livenessProbe:
            httpGet:
              path: /health/live
              port: 9990
          readinessProbe:
            httpGet:
              path: /health/ready
              port: 9990
          startupProbe:
            httpGet:
              path: /health/started
              port: 9990

apiVersion: v1
kind: Service
metadata:
  name: simple-microservice-server-service
  labels:
    app: simple-microservice-server
spec:
  ports:
    - name: http
      protocol: TCP
      port: 8080
      targetPort: 8080
  selector:
    app: simple-microservice-server
  type: ClusterIP

Then it is working for me:

]$ kubectl run --rm -it --tty curl-simple-microservice-server --image=curlimages/curl --restart=Never -- http://simple-microservice-server-service:8080/hello/tommy
Hello 'tommy'.pod "curl-simple-microservice-server" deleted

The "Hello 'tommy'" part tells the service is OK