spring-petclinic / spring-petclinic-cloud Goto Github PK

Fork of the Spring Cloud Microservices project packaged to be deployed on several Cloud platforms: Kubernetes and Cloud Foundry

License: Apache License 2.0

Dockerfile 1.04% Java 68.77% HTML 11.15% JavaScript 8.46% Makefile 0.86% Shell 2.01% Less 7.70%

spring-cloud docker kubernetes cloud-foundry tanzu wavefront

spring-petclinic-cloud's People

Contributors

Stargazers

Watchers

Forkers

aruns1975 murali535 otoukebri anelechila carlos-nieto jonathanvila usulek gmariotti petereltgroth ktpv cary205 agilderdale riazvm sandrdali lingling1420q ramanareddy03 austinlparker abhiml0809 qggao aspineon madhavnitw84 odedia tomcat33031 ellybusinge togata arey bxtp4p madhavi0891 opssemnik manu-pocs brajdev benjaminhuo pgottam malston bthelen rushins isabella232 quyip8818 ravekev joshisa alphagov-mirror vaibhavbhatnagar alex-y-kozlov-sandbox cybernetics dahr owinocliff ajitkadari carmelopz axymthr luismiguelmartinsanchez lee-zhg dbuchko rassidm ashgit301 renugadevi-2613 gopaddle-demo iipolovinkin vazenich mtroschiy frog97 marceltft gauravhub uk-gov-mirror akwei mamtajha-ts emilyzeng1977 svrc kpaxer joaomlneto marctanguy platform9-community yogendra drgeb achuchekwi harivemula benmthomas mrporcles yanickxia murthy-vmware mandeeps-cloud sampathgoud258 msyhu patsevanton trumpssta dystudio dlinsley mtritabaugh email2dhiren laurentgrangeau anandsoft rockhowse alexrogalskiy ronggenliu2019 skp15121980 jaynzr skpandey108 tedtheripper dove6 ykhadilkar shayn1234

spring-petclinic-cloud's Issues

Docker spring-petclinic-config-server:latest not found

Hello. I try run spring-petclinic-cloud

git clone https://github.com/spring-petclinic/spring-petclinic-cloud.git
docker-compose up
Creating network "spring-petclinic-cloud_default" with the default driver
Pulling config-server (springcommunity/spring-petclinic-config-server:)...
ERROR: manifest for springcommunity/spring-petclinic-config-server:latest not found: manifest unknown: manifest unknown

Add documentation to setup local KIND dev environment

Update documentation to reflect setting up a local KIND environment for development.

how to deploy any war file or any html file into spring petclinic, is it possible? how to deploy anything by usnig this spring petclinic projetc

how to deploy any war file or any html file into spring petclinic, is it possible?
how to deploy anything by usnig this spring petclinic project can any please tell me the steps or procedure

Skaffold Build Fails - Incompatible Maven Version

Background

Skaffold build use paketo-buildpacks for building the code. The paketo-buildpacks/maven added the build flag "--no-transfer-progress" to mvn command which was introuced in Maven 3.6.1 https://maven.apache.org/docs/3.6.1/release-notes.html

Current failure

Compiled Application: Contributing to layer
    Executing mvnw --batch-mode -Dmaven.test.skip=true --no-transfer-progress package
      Unable to parse command line options: Unrecognized option: --no-transfer-progress

Proposal

Upgrade Maven Wrapper and Maven to latest version(3.8.6)

Consider using the official Spring Cloud Docker images

Spring Cloud 2021.0.0 is coming with new Features For Spring Cloud Kubernetes and 2 official Docker images :

spring-cloud-kubernetes-configserver
spring-cloud-kubernetes-discoveryserver

Refer to this blog post: https://spring.io/blog/2021/10/26/new-features-for-spring-cloud-kubernetes-in-spring-cloud-2021-0-0-m3

Switch to the spring-petclinic-cloud-config repo

Following the exchanges carried out in the pull request #7, the https://github.com/spring-petclinic/spring-petclinic-cloud-config repository has been created to manage the project configuration.
@odedia may now move its own repo https://github.com/odedia/spring-petclinic-microservices-config to this new one.

Fix typo in config-map.yaml - vists instead of visits

diff --git a/k8s/init-services/02-config-map.yaml b/k8s/init-services/02-config-map.yaml
index 32de900..6a8de77 100644
--- a/k8s/init-services/02-config-map.yaml
+++ b/k8s/init-services/02-config-map.yaml
@@ -53,7 +53,7 @@ data:
             enabled: true

     customers-service-id: http://customers-service.spring-petclinic.svc.cluster.local:8080
-    visits-service-id: http://vists-service.spring-petclinic.svc.cluster.local:8080
+    visits-service-id: http://visits-service.spring-petclinic.svc.cluster.local:8080

     spring:
       datasource:

Remove use of Spring Cloud's bootstrap context

Spring Cloud's bootstrap context is problematic for things that need to react to the environment early, such as the wavefront integration. Could you please upgrade to a more recent version of Spring Cloud that doesn't require this?

Consider Wavefront integration

Following a discussion with @maciejwalkowiak spring-petclinic/spring-petclinic-data-jdbc#4 (comment), it could make sense to integrate Wavefront into the k8s version of Petclinic.

@odedia has already implement a fork here: https://github.com/odedia/spring-petclinic-microservices

java.sql.SQLSyntaxErrorException: Unknown database 'service_instance_db'

skaffold dev --default-repo antonpatsev

skaffold.yaml

apiVersion: skaffold/v2beta6
kind: Config
metadata:
  name: spring-petclinic-cloud
build:
  tagPolicy:
    sha256: {}
  artifacts:
  - image: spring-petclinic-config-server
    context:  ./spring-petclinic-config-server
    buildpacks:
      builder:  gcr.io/paketo-buildpacks/builder:base
      trustBuilder: true
  - image: spring-petclinic-discovery-server
    context:  ./spring-petclinic-discovery-server
    buildpacks:
      builder:  gcr.io/paketo-buildpacks/builder:base
      trustBuilder: true
  - image: spring-petclinic-customers-service
    context:  ./spring-petclinic-customers-service
    buildpacks:
      builder:  gcr.io/paketo-buildpacks/builder:base
      trustBuilder: true
  - image: spring-petclinic-visits-service
    context:  ./spring-petclinic-visits-service
    buildpacks:
      builder: gcr.io/paketo-buildpacks/builder:base
      trustBuilder: true
  - image: spring-petclinic-vets-service
    context:  ./spring-petclinic-vets-service
    buildpacks:
      builder:  gcr.io/paketo-buildpacks/builder:base
      trustBuilder: true
  - image: spring-petclinic-api-gateway
    context:  ./spring-petclinic-api-gateway
    buildpacks:
      builder:  gcr.io/paketo-buildpacks/builder:base
      trustBuilder: true     
deploy:
  statusCheckDeadlineSeconds: 240
  helm:
    releases:
    - name: customers-db-mysql
      chartPath: bitnami/mysql #Change to your local ChartRepo if appropriate -> kubeapps/mysql
      valuesFiles: 
        - k8s/helm-values/db-values.yaml
      namespace: spring-petclinic
      remote: true
      wait: true
    - name: vets-db-mysql
      chartPath: bitnami/mysql #Change to your local ChartRepo if appropriate -> kubeapps/mysql
      valuesFiles: 
        - k8s/helm-values/db-values.yaml
      namespace: spring-petclinic
      remote: true
      wait: true
    - name: visits-db-mysql
      chartPath: bitnami/mysql #Change to your local ChartRepo if appropriate -> kubeapps/mysql
      valuesFiles: 
        - k8s/helm-values/db-values.yaml
      namespace: spring-petclinic
      remote: true
      wait: true
    flags:
      install:
        - "--create-namespace" 
  kubectl:
    manifests:
    - k8s/init-namespace/01-namespace.yaml
    - k8s/init-namespace/02-regcreds.yaml
    - k8s/init-services/02-config-map.yaml
    - k8s/init-services/03-role.yaml
    #- k8s/init-services/04-wavefront.yaml
    - k8s/init-services/05-api-gateway-service.yaml
    - k8s/init-services/06-customers-service-service.yaml
    - k8s/init-services/07-vets-service-service.yaml
    - k8s/init-services/08-visits-service-service.yaml
    - k8s/api-gateway-deployment.yaml
    - k8s/customers-service-deployment.yaml
    - k8s/vets-service-deployment.yaml
    - k8s/visits-service-deployment.yaml

Full log https://gist.github.com/patsevanton/98464348a6d01885d36303f89e599555

Align k8s namespace to spring-petclinic

I propose to change the k8s namespace from namespace/spring-pet-clinic to namespace/spring-petclinic-cloud

How deploy spring-petclinic-cloud to k8s without wavefront?

Hello!
I try run spring-petclinic-cloud in kubernetes locally.
I get error.
How deploy spring-petclinic-cloud to k8s without wavefront?

api-gateway-87b794774-kn2rc api-gateway 2021-10-28 10:18:45.674 ERROR [api-gateway,,,] 1 --- [tClientSender-0] c.w.s.c.c.service.ReportingService       : Unable to obtain status code from the Wavefront service at http://wavefront-proxy.spring-petclinic.svc.cluster.local:2878/report?f=trace
api-gateway-87b794774-kn2rc api-gateway 
api-gateway-87b794774-kn2rc api-gateway java.net.UnknownHostException: wavefront-proxy.spring-petclinic.svc.cluster.local
api-gateway-87b794774-kn2rc api-gateway         at java.base/java.net.AbstractPlainSocketImpl.connect(Unknown Source)
api-gateway-87b794774-kn2rc api-gateway         at java.base/java.net.Socket.connect(Unknown Source)
api-gateway-87b794774-kn2rc api-gateway         at java.base/sun.net.NetworkClient.doConnect(Unknown Source)
api-gateway-87b794774-kn2rc api-gateway         at java.base/sun.net.www.http.HttpClient.openServer(Unknown Source)
api-gateway-87b794774-kn2rc api-gateway         at java.base/sun.net.www.http.HttpClient.openServer(Unknown Source)
api-gateway-87b794774-kn2rc api-gateway         at java.base/sun.net.www.http.HttpClient.<init>(Unknown Source)
api-gateway-87b794774-kn2rc api-gateway         at java.base/sun.net.www.http.HttpClient.New(Unknown Source)
api-gateway-87b794774-kn2rc api-gateway         at java.base/sun.net.www.http.HttpClient.New(Unknown Source)
api-gateway-87b794774-kn2rc api-gateway         at java.base/sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown Source)
api-gateway-87b794774-kn2rc api-gateway         at java.base/sun.net.www.protocol.http.HttpURLConnection.plainConnect0(Unknown Source)
api-gateway-87b794774-kn2rc api-gateway         at java.base/sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
api-gateway-87b794774-kn2rc api-gateway         at java.base/sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source)
api-gateway-87b794774-kn2rc api-gateway         at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown Source)
api-gateway-87b794774-kn2rc api-gateway         at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
api-gateway-87b794774-kn2rc api-gateway         at java.base/java.net.HttpURLConnection.getResponseCode(Unknown Source)
api-gateway-87b794774-kn2rc api-gateway         at com.wavefront.sdk.common.clients.service.ReportingService.safeGetResponseCodeAndClose(ReportingService.java:77)
api-gateway-87b794774-kn2rc api-gateway         at com.wavefront.sdk.common.clients.service.ReportingService.send(ReportingService.java:68)
api-gateway-87b794774-kn2rc api-gateway         at com.wavefront.sdk.common.clients.WavefrontClient.internalFlush(WavefrontClient.java:515)
api-gateway-87b794774-kn2rc api-gateway         at com.wavefront.sdk.common.clients.WavefrontClient.flushNoCheck(WavefrontClient.java:472)
api-gateway-87b794774-kn2rc api-gateway         at com.wavefront.sdk.common.clients.WavefrontClient.flush(WavefrontClient.java:460)
api-gateway-87b794774-kn2rc api-gateway         at com.wavefront.sdk.common.clients.WavefrontClient.run(WavefrontClient.java:448)
api-gateway-87b794774-kn2rc api-gateway         at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
api-gateway-87b794774-kn2rc api-gateway         at java.base/java.util.concurrent.FutureTask.runAndReset(Unknown Source)
api-gateway-87b794774-kn2rc api-gateway         at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
api-gateway-87b794774-kn2rc api-gateway         at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
api-gateway-87b794774-kn2rc api-gateway         at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
api-gateway-87b794774-kn2rc api-gateway         at java.base/java.lang.Thread.run(Unknown Source)

Can i help for actualization readme?

Hello!
I read readme and see Cloud Foundry.
Can i help for actualization readme?
May be simple delete text "Cloud Foundry"?

couldn't parse image reference "${REPOSITORY_PREFIX}

Show files with REPOSITORY_PREFIX

grep -R  {REPOSITORY_PREFIX}/api-gateway:latest .
./scripts/pushImages.sh:docker push ${REPOSITORY_PREFIX}/api-gateway:latest
./k8s/api-gateway-deployment.yaml:      - image: ${REPOSITORY_PREFIX}/api-gateway:latest

Create ENV variable

export REPOSITORY_PREFIX=antonpatsev

Run skafford

skaffold dev --default-repo antonpatsev
Listing files to watch...
 - spring-petclinic-config-server
 - spring-petclinic-discovery-server
 - spring-petclinic-customers-service
 - spring-petclinic-visits-service
 - spring-petclinic-vets-service
 - spring-petclinic-api-gateway
Generating tags...
 - spring-petclinic-config-server -> antonpatsev/spring-petclinic-config-server:latest
 - spring-petclinic-discovery-server -> antonpatsev/spring-petclinic-discovery-server:latest
 - spring-petclinic-customers-service -> antonpatsev/spring-petclinic-customers-service:latest
 - spring-petclinic-visits-service -> antonpatsev/spring-petclinic-visits-service:latest
 - spring-petclinic-vets-service -> antonpatsev/spring-petclinic-vets-service:latest
 - spring-petclinic-api-gateway -> antonpatsev/spring-petclinic-api-gateway:latest
Checking cache...
 - spring-petclinic-config-server: Found Remotely
 - spring-petclinic-discovery-server: Found Remotely
 - spring-petclinic-customers-service: Found Remotely
 - spring-petclinic-visits-service: Found Remotely
 - spring-petclinic-vets-service: Found Remotely
 - spring-petclinic-api-gateway: Found Remotely
Tags used in deployment:
 - spring-petclinic-config-server -> antonpatsev/spring-petclinic-config-server:latest@sha256:2792e7678e83f01cda7d71754f7dad1403416ac672f7078d81cbe8ebb1cf1c33
 - spring-petclinic-discovery-server -> antonpatsev/spring-petclinic-discovery-server:latest@sha256:3af5b8f83d44cf11f7aa26be1fcf595a68ee82a73ea6c2b8feaa1478c213080b
 - spring-petclinic-customers-service -> antonpatsev/spring-petclinic-customers-service:latest@sha256:62e940d6655e18d4b3af73902839b1fc377379fa6acc0bc33e72204e47acb6df
 - spring-petclinic-visits-service -> antonpatsev/spring-petclinic-visits-service:latest@sha256:38f48e411ce963ca5e8e083ca6a64b36438f2ca51b613ee2830e8aecda25d214
 - spring-petclinic-vets-service -> antonpatsev/spring-petclinic-vets-service:latest@sha256:9ad091cd546153f4ccafffdbf31db2c7f987c2b6cc18146ed07fa5ebd05636d3
 - spring-petclinic-api-gateway -> antonpatsev/spring-petclinic-api-gateway:latest@sha256:7f8b9598f263c16ec75ec6e9d8bc8e1885be090f180150470a6d452a2b52d953
Starting deploy...
Helm release customers-db-mysql not installed. Installing...
NAME: customers-db-mysql
LAST DEPLOYED: Fri Oct  1 05:32:43 2021
NAMESPACE: spring-petclinic
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
** Please be patient while the chart is being deployed **

Tip:

  Watch the deployment status using the command: kubectl get pods -w --namespace spring-petclinic

Services:

  echo Primary: customers-db-mysql.spring-petclinic.svc.cluster.local:3306

Execute the following to get the administrator credentials:

  echo Username: root
  MYSQL_ROOT_PASSWORD=$(kubectl get secret --namespace spring-petclinic customers-db-mysql -o jsonpath="{.data.mysql-root-password}" | base64 --decode)

To connect to your database:

  1. Run a pod that you can use as a client:

      kubectl run customers-db-mysql-client --rm --tty -i --restart='Never' --image  docker.io/bitnami/mysql:8.0.26-debian-10-r60 --namespace spring-petclinic --command -- bash

  2. To connect to primary service (read/write):

      mysql -h customers-db-mysql.spring-petclinic.svc.cluster.local -uroot -p"$MYSQL_ROOT_PASSWORD"



To upgrade this helm chart:

  1. Obtain the password as described on the 'Administrator credentials' section and set the 'root.password' parameter as shown below:

      ROOT_PASSWORD=$(kubectl get secret --namespace spring-petclinic customers-db-mysql -o jsonpath="{.data.mysql-root-password}" | base64 --decode)
      helm upgrade --namespace spring-petclinic customers-db-mysql bitnami/mysql --set auth.rootPassword=$ROOT_PASSWORD
Helm release vets-db-mysql not installed. Installing...
NAME: vets-db-mysql
LAST DEPLOYED: Fri Oct  1 05:33:08 2021
NAMESPACE: spring-petclinic
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
** Please be patient while the chart is being deployed **

Tip:

  Watch the deployment status using the command: kubectl get pods -w --namespace spring-petclinic

Services:

  echo Primary: vets-db-mysql.spring-petclinic.svc.cluster.local:3306

Execute the following to get the administrator credentials:

  echo Username: root
  MYSQL_ROOT_PASSWORD=$(kubectl get secret --namespace spring-petclinic vets-db-mysql -o jsonpath="{.data.mysql-root-password}" | base64 --decode)

To connect to your database:

  1. Run a pod that you can use as a client:

      kubectl run vets-db-mysql-client --rm --tty -i --restart='Never' --image  docker.io/bitnami/mysql:8.0.26-debian-10-r60 --namespace spring-petclinic --command -- bash

  2. To connect to primary service (read/write):

      mysql -h vets-db-mysql.spring-petclinic.svc.cluster.local -uroot -p"$MYSQL_ROOT_PASSWORD"



To upgrade this helm chart:

  1. Obtain the password as described on the 'Administrator credentials' section and set the 'root.password' parameter as shown below:

      ROOT_PASSWORD=$(kubectl get secret --namespace spring-petclinic vets-db-mysql -o jsonpath="{.data.mysql-root-password}" | base64 --decode)
      helm upgrade --namespace spring-petclinic vets-db-mysql bitnami/mysql --set auth.rootPassword=$ROOT_PASSWORD
Helm release visits-db-mysql not installed. Installing...
NAME: visits-db-mysql
LAST DEPLOYED: Fri Oct  1 05:33:35 2021
NAMESPACE: spring-petclinic
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
** Please be patient while the chart is being deployed **

Tip:

  Watch the deployment status using the command: kubectl get pods -w --namespace spring-petclinic

Services:

  echo Primary: visits-db-mysql.spring-petclinic.svc.cluster.local:3306

Execute the following to get the administrator credentials:

  echo Username: root
  MYSQL_ROOT_PASSWORD=$(kubectl get secret --namespace spring-petclinic visits-db-mysql -o jsonpath="{.data.mysql-root-password}" | base64 --decode)

To connect to your database:

  1. Run a pod that you can use as a client:

      kubectl run visits-db-mysql-client --rm --tty -i --restart='Never' --image  docker.io/bitnami/mysql:8.0.26-debian-10-r60 --namespace spring-petclinic --command -- bash

  2. To connect to primary service (read/write):

      mysql -h visits-db-mysql.spring-petclinic.svc.cluster.local -uroot -p"$MYSQL_ROOT_PASSWORD"



To upgrade this helm chart:

  1. Obtain the password as described on the 'Administrator credentials' section and set the 'root.password' parameter as shown below:

      ROOT_PASSWORD=$(kubectl get secret --namespace spring-petclinic visits-db-mysql -o jsonpath="{.data.mysql-root-password}" | base64 --decode)
      helm upgrade --namespace spring-petclinic visits-db-mysql bitnami/mysql --set auth.rootPassword=$ROOT_PASSWORD
WARN[0081] image [antonpatsev/spring-petclinic-config-server:latest@sha256:2792e7678e83f01cda7d71754f7dad1403416ac672f7078d81cbe8ebb1cf1c33] is not used. 
WARN[0081] See helm documentation on how to replace image names with their actual tags: https://skaffold.dev/docs/pipeline-stages/deployers/helm/#image-configuration 
WARN[0081] image [antonpatsev/spring-petclinic-discovery-server:latest@sha256:3af5b8f83d44cf11f7aa26be1fcf595a68ee82a73ea6c2b8feaa1478c213080b] is not used. 
WARN[0081] See helm documentation on how to replace image names with their actual tags: https://skaffold.dev/docs/pipeline-stages/deployers/helm/#image-configuration 
WARN[0081] image [antonpatsev/spring-petclinic-customers-service:latest@sha256:62e940d6655e18d4b3af73902839b1fc377379fa6acc0bc33e72204e47acb6df] is not used. 
WARN[0081] See helm documentation on how to replace image names with their actual tags: https://skaffold.dev/docs/pipeline-stages/deployers/helm/#image-configuration 
WARN[0081] image [antonpatsev/spring-petclinic-visits-service:latest@sha256:38f48e411ce963ca5e8e083ca6a64b36438f2ca51b613ee2830e8aecda25d214] is not used. 
WARN[0081] See helm documentation on how to replace image names with their actual tags: https://skaffold.dev/docs/pipeline-stages/deployers/helm/#image-configuration 
WARN[0081] image [antonpatsev/spring-petclinic-vets-service:latest@sha256:9ad091cd546153f4ccafffdbf31db2c7f987c2b6cc18146ed07fa5ebd05636d3] is not used. 
WARN[0081] See helm documentation on how to replace image names with their actual tags: https://skaffold.dev/docs/pipeline-stages/deployers/helm/#image-configuration 
WARN[0081] image [antonpatsev/spring-petclinic-api-gateway:latest@sha256:7f8b9598f263c16ec75ec6e9d8bc8e1885be090f180150470a6d452a2b52d953] is not used. 
WARN[0081] See helm documentation on how to replace image names with their actual tags: https://skaffold.dev/docs/pipeline-stages/deployers/helm/#image-configuration 
Waiting for deployments to stabilize...
Deployments stabilized in 7.411549ms
 - Warning: resource namespaces/spring-petclinic is missing the kubectl.kubernetes.io/last-applied-configuration annotation which is required by kubectl apply. kubectl apply should only be used on resources created declaratively by either kubectl create --save-config or kubectl apply. The missing annotation will be patched automatically.
 - namespace/spring-petclinic configured
 - secret/regcred created
 - configmap/petclinic-config created
 - role.rbac.authorization.k8s.io/namespace-reader created
 - rolebinding.rbac.authorization.k8s.io/namespace-reader-binding created
 - service/api-gateway created
 - service/customers-service created
 - service/vets-service created
 - service/visits-service created
 - deployment.apps/api-gateway created
 - deployment.apps/customers-service created
 - deployment.apps/vets-service created
 - deployment.apps/visits-service created
Waiting for deployments to stabilize...
 - spring-petclinic:deployment/api-gateway: InspectFailed: Failed to apply default image tag "${REPOSITORY_PREFIX}/api-gateway:latest": couldn't parse image reference "${REPOSITORY_PREFIX}/api-gateway:latest": invalid reference format: repository name must be lowercase
    - spring-petclinic:pod/api-gateway-5bc8d44664-48tgv: InspectFailed: Failed to apply default image tag "${REPOSITORY_PREFIX}/api-gateway:latest": couldn't parse image reference "${REPOSITORY_PREFIX}/api-gateway:latest": invalid reference format: repository name must be lowercase
 - spring-petclinic:deployment/customers-service: InspectFailed: Failed to apply default image tag "${REPOSITORY_PREFIX}/customers-service:latest": couldn't parse image reference "${REPOSITORY_PREFIX}/customers-service:latest": invalid reference format: repository name must be lowercase
    - spring-petclinic:pod/customers-service-75c77f6cd9-qf9ts: InspectFailed: Failed to apply default image tag "${REPOSITORY_PREFIX}/customers-service:latest": couldn't parse image reference "${REPOSITORY_PREFIX}/customers-service:latest": invalid reference format: repository name must be lowercase
 - spring-petclinic:deployment/vets-service: InspectFailed: Failed to apply default image tag "${REPOSITORY_PREFIX}/vets-service:latest": couldn't parse image reference "${REPOSITORY_PREFIX}/vets-service:latest": invalid reference format: repository name must be lowercase
    - spring-petclinic:pod/vets-service-854775b9b9-nz6vr: InspectFailed: Failed to apply default image tag "${REPOSITORY_PREFIX}/vets-service:latest": couldn't parse image reference "${REPOSITORY_PREFIX}/vets-service:latest": invalid reference format: repository name must be lowercase
 - spring-petclinic:deployment/visits-service: InspectFailed: Failed to apply default image tag "${REPOSITORY_PREFIX}/visits-service:latest": couldn't parse image reference "${REPOSITORY_PREFIX}/visits-service:latest": invalid reference format: repository name must be lowercase
    - spring-petclinic:pod/visits-service-86f868f9f7-nczj7: InspectFailed: Failed to apply default image tag "${REPOSITORY_PREFIX}/visits-service:latest": couldn't parse image reference "${REPOSITORY_PREFIX}/visits-service:latest": invalid reference format: repository name must be lowercase
 - spring-petclinic:deployment/api-gateway: InspectFailed: Failed to apply default image tag "${REPOSITORY_PREFIX}/api-gateway:latest": couldn't parse image reference "${REPOSITORY_PREFIX}/api-gateway:latest": invalid reference format: repository name must be lowercase
    - spring-petclinic:pod/api-gateway-5bc8d44664-48tgv: InspectFailed: Failed to apply default image tag "${REPOSITORY_PREFIX}/api-gateway:latest": couldn't parse image reference "${REPOSITORY_PREFIX}/api-gateway:latest": invalid reference format: repository name must be lowercase
 - spring-petclinic:deployment/api-gateway failed. Error: InspectFailed: Failed to apply default image tag "${REPOSITORY_PREFIX}/api-gateway:latest": couldn't parse image reference "${REPOSITORY_PREFIX}/api-gateway:latest": invalid reference format: repository name must be lowercase.
 - spring-petclinic:deployment/visits-service: InspectFailed: Failed to apply default image tag "${REPOSITORY_PREFIX}/visits-service:latest": couldn't parse image reference "${REPOSITORY_PREFIX}/visits-service:latest": invalid reference format: repository name must be lowercase
    - spring-petclinic:pod/visits-service-86f868f9f7-nczj7: InspectFailed: Failed to apply default image tag "${REPOSITORY_PREFIX}/visits-service:latest": couldn't parse image reference "${REPOSITORY_PREFIX}/visits-service:latest": invalid reference format: repository name must be lowercase
 - spring-petclinic:deployment/visits-service failed. Error: InspectFailed: Failed to apply default image tag "${REPOSITORY_PREFIX}/visits-service:latest": couldn't parse image reference "${REPOSITORY_PREFIX}/visits-service:latest": invalid reference format: repository name must be lowercase.
 - spring-petclinic:deployment/vets-service: InspectFailed: Failed to apply default image tag "${REPOSITORY_PREFIX}/vets-service:latest": couldn't parse image reference "${REPOSITORY_PREFIX}/vets-service:latest": invalid reference format: repository name must be lowercase
    - spring-petclinic:pod/vets-service-854775b9b9-nz6vr: InspectFailed: Failed to apply default image tag "${REPOSITORY_PREFIX}/vets-service:latest": couldn't parse image reference "${REPOSITORY_PREFIX}/vets-service:latest": invalid reference format: repository name must be lowercase
 - spring-petclinic:deployment/vets-service failed. Error: InspectFailed: Failed to apply default image tag "${REPOSITORY_PREFIX}/vets-service:latest": couldn't parse image reference "${REPOSITORY_PREFIX}/vets-service:latest": invalid reference format: repository name must be lowercase.
 - spring-petclinic:deployment/customers-service: InspectFailed: Failed to apply default image tag "${REPOSITORY_PREFIX}/customers-service:latest": couldn't parse image reference "${REPOSITORY_PREFIX}/customers-service:latest": invalid reference format: repository name must be lowercase
    - spring-petclinic:pod/customers-service-75c77f6cd9-qf9ts: InspectFailed: Failed to apply default image tag "${REPOSITORY_PREFIX}/customers-service:latest": couldn't parse image reference "${REPOSITORY_PREFIX}/customers-service:latest": invalid reference format: repository name must be lowercase
 - spring-petclinic:deployment/customers-service failed. Error: InspectFailed: Failed to apply default image tag "${REPOSITORY_PREFIX}/customers-service:latest": couldn't parse image reference "${REPOSITORY_PREFIX}/customers-service:latest": invalid reference format: repository name must be lowercase.
Cleaning up...
release "customers-db-mysql" uninstalled
release "vets-db-mysql" uninstalled
release "visits-db-mysql" uninstalled
 - namespace "spring-petclinic" deleted
 - secret "regcred" deleted
 - configmap "petclinic-config" deleted
 - role.rbac.authorization.k8s.io "namespace-reader" deleted
 - rolebinding.rbac.authorization.k8s.io "namespace-reader-binding" deleted
 - service "api-gateway" deleted
 - service "customers-service" deleted
 - service "vets-service" deleted
 - service "visits-service" deleted
 - deployment.apps "api-gateway" deleted
 - deployment.apps "customers-service" deleted
 - deployment.apps "vets-service" deleted
 - deployment.apps "visits-service" deleted
4/4 deployment(s) failed

Update services to run inside k8s

Support Azure Spring Cloud

Replatform the solution for Azure Spring Cloud: https://azure.microsoft.com/en-us/services/spring-cloud/

Error: INSTALLATION FAILED: chart requires kubeVersion: >= 1.18.10 <= 1.20.5

I tried to install the Helm Chart on Minikube and get the following error:

$ helm install spring-petclinic-cloud Platform9-Community/spring-petclinic-cloud --namespace spring-petclinic --create-namespace
Error: INSTALLATION FAILED: chart requires kubeVersion: >= 1.18.10 <= 1.20.5 which is incompatible with Kubernetes v1.26.3

Give unique image name

I would like to publish the docker images to the springcommunity organization: https://hub.docker.com/u/springcommunity. So people could test k8s deployment without building the docker images.
I didn't try but I suppose it will publish image without prefix (ie: springcommunity:vets-service)

To avoid naming conflict, could we add as prefix the name of the github project: spring-petclinic-cloud and a suffix with the k8s maven profile ? Thus we will have springcommunity:spring-petclinic-cloud-vets-service-k8s
What do you think about? Does docker image name and k8s service name are linked?

how to deploy any war file or any html file into spring petclinic, is it possible?

How correct enable/disable endpoint of Spring Cloud via env variable?

Hello!
How correct enable/disable endpoint of Spring Cloud via env variable?

I see only MANAGEMENT_METRICS_EXPORT_WAVEFRONT_URI
https://github.com/spring-petclinic/spring-petclinic-cloud/blob/master/k8s/api-gateway-deployment.yaml#L48
Thanks!

deploying "customers-db-mysql": install: exit status 1

skaffold dev --default-repo antonpatsev
Listing files to watch...
 - spring-petclinic-config-server
 - spring-petclinic-discovery-server
 - spring-petclinic-customers-service
 - spring-petclinic-visits-service
 - spring-petclinic-vets-service
 - spring-petclinic-api-gateway
Generating tags...
 - spring-petclinic-config-server -> antonpatsev/spring-petclinic-config-server:latest
 - spring-petclinic-discovery-server -> antonpatsev/spring-petclinic-discovery-server:latest
 - spring-petclinic-customers-service -> antonpatsev/spring-petclinic-customers-service:latest
 - spring-petclinic-visits-service -> antonpatsev/spring-petclinic-visits-service:latest
 - spring-petclinic-vets-service -> antonpatsev/spring-petclinic-vets-service:latest
 - spring-petclinic-api-gateway -> antonpatsev/spring-petclinic-api-gateway:latest
Checking cache...
 - spring-petclinic-config-server: Found Remotely
 - spring-petclinic-discovery-server: Found Remotely
 - spring-petclinic-customers-service: Found Remotely
 - spring-petclinic-visits-service: Found Remotely
 - spring-petclinic-vets-service: Found Remotely
 - spring-petclinic-api-gateway: Found Remotely
Tags used in deployment:
 - spring-petclinic-config-server -> antonpatsev/spring-petclinic-config-server:latest@sha256:2792e7678e83f01cda7d71754f7dad1403416ac672f7078d81cbe8ebb1cf1c33
 - spring-petclinic-discovery-server -> antonpatsev/spring-petclinic-discovery-server:latest@sha256:3af5b8f83d44cf11f7aa26be1fcf595a68ee82a73ea6c2b8feaa1478c213080b
 - spring-petclinic-customers-service -> antonpatsev/spring-petclinic-customers-service:latest@sha256:62e940d6655e18d4b3af73902839b1fc377379fa6acc0bc33e72204e47acb6df
 - spring-petclinic-visits-service -> antonpatsev/spring-petclinic-visits-service:latest@sha256:38f48e411ce963ca5e8e083ca6a64b36438f2ca51b613ee2830e8aecda25d214
 - spring-petclinic-vets-service -> antonpatsev/spring-petclinic-vets-service:latest@sha256:9ad091cd546153f4ccafffdbf31db2c7f987c2b6cc18146ed07fa5ebd05636d3
 - spring-petclinic-api-gateway -> antonpatsev/spring-petclinic-api-gateway:latest@sha256:7f8b9598f263c16ec75ec6e9d8bc8e1885be090f180150470a6d452a2b52d953
Starting deploy...
Helm release customers-db-mysql not installed. Installing...
Error: failed to download "bitnami/mysql" (hint: running `helm repo update` may help)
Cleaning up...
Error: uninstall: Release not loaded: customers-db-mysql: release: not found
WARN[0003] deployer cleanup:exit status 1                subtask=-1 task=DevLoop
deploying "customers-db-mysql": install: exit status 1

arey@MacBook scripts % cf create-service -c '{ "git": { "uri": "https://github.com/arey/spring-petclinic-cloud-config.git", "periodic": true }, "count": 3 }' p.config-server standard config
Création de l'instance de service config dans l'organisation cfdev-org/l'espace cfdev-space en tant que admin...
Service offering 'p.config-server' not found.
ECHEC

arey@MacBook scripts % cf dev version  
CLI: 0.0.18
BUILD: 36 (f58f3cc)
cf: v13.2.0
cf-mysql: 36.19.0