-
Notifications
You must be signed in to change notification settings - Fork 582
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
problems running the skipper #5528
Comments
checking the behavior here, when I use the already generated skipper image in springcloud/spring-cloud-skipper-server it can read the application.yaml, however when I build this image and generate my own docker to work with the oracle driver , it can no longer fill these files. The documentation only says to add the dependency and generate the jar. |
I will be better to use 2.11.1 or skipper and 2.9.2 of deployer dependencies. |
Hi @DaniloSottoDeLima |
Closing due to inactivity. If closed in error please let us know. |
Description:
I'm creating a project that will use spring cloud dataflow with an oracle database. However, looking at the documentation, I saw that there is no driver for Oracle, thus forcing the dependency to be added to the skipper's pom.xml, for example.
After adding this dependency, I generated the jar file and a docker image on top of it. Therefore, when I try to deploy this image to Kuberentes, based on the skipper-config-kafka.yaml and skipper-deployment.yaml files, it is not able to read the configmap's application.yaml.
Release versions:
latest
Steps to reproduce:
Build the skipper-server application with the oracle database dependency in pom.xml and upload it to the kubernetes environment using the files skipper-config-kafka.yaml and skipper-deployment.yaml.
Screenshots:
skipper-config-kafka.yaml:
skipper-deployment.yaml:
error on deploy skipper:
Error text
Parameter 2 of method cloudFoundryPlatform in org.springframework.cloud.skipper.server.autoconfigure.CloudFoundryPlatformAutoConfiguration required a bean of type 'org.cloudfoundry.logcache.v1.LogCacheClient' that could not be found.
Additional context:
It seems to me that he can't fill the application.yaml settings.
The text was updated successfully, but these errors were encountered: