Skip to content

bigdata06/spring-cloud-deployer-kubernetes

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

spring-cloud-deployer-kubernetes

Building

Build the project without running tests using:

./mvnw clean install -DskipTests 

Integration tests

All testing is curently done against a GKE cluster. Minikube is no longer useful since we test some parts of the external IP features that a LoadBalancer service provides.

Google Container Engine

Create a test cluster and target it using something like (use your own project name, substitute --zone if needed):

gcloud container --project {your-project-name} clusters create "spring-test" --zone "us-central1-b" --machine-type "n1-highcpu-2" --scopes "https://www.googleapis.com/auth/compute","https://www.googleapis.com/auth/devstorage.read_only","https://www.googleapis.com/auth/logging.write" --network "default" --enable-cloud-logging --enable-cloud-monitoring gcloud config set container/cluster spring-test gcloud config set compute/zone us-central1-b gcloud container clusters get-credentials spring-test 

Running the tests

Once the test cluster has been created, you can run all integration tests.

As long as your kubectl config files are set to point to your cluster, you should be able to just run the tests. Verify your config using kubectl config get-contexts and check that your test cluster is the current context.

Now run the tests:

$ ./mvnw test 

NOTE: if you get authentication errors, try setting basic auth credentials:

Navigate to your project and cluster on https://console.cloud.google.com/ and click on show credentials

$export KUBERNETES_AUTH_BASIC_PASSWORD= $export KUBERNETES_AUTH_BASIC_USERNAME=

About

The Spring Cloud Deployer implementation for Kubernetes

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • Java 92.5%
  • Shell 4.4%
  • Batchfile 3.1%