Spring Boot + google kubernetes + Google SQL Cloud not working -


i trying push spring boot application in google kubernetes(google container engine).

i have performed step given in below link.

https://codelabs.developers.google.com/codelabs/cloud-springboot-kubernetes/index.html?index=..%2f..%2findex#0

when trying perform step 9 http://:8080 in browser not reachable.

yes got external ip address.

i able ping ip address

let me know if other information require.

in logging not able connect database

error:

com.mysql.jdbc.exceptions.jdbc4.mysqlnontransientconnectionexception: not create connection database server.

i hope have created cluster in google container engine

follow first 5 step given in link

https://cloud.google.com/sql/docs/mysql/connect-container-engine

change database configuration in application

hostname: 127.0.0.1 port: 3306 or mysql port username: proxyuser

should same link step - 3

  1. mvn package -dmaven.test.skip=true

  2. create file name "dockerfile" , below content

    from openjdk:8 copy target/springbootwithdb-0.0.1-snapshot.jar /app.jar expose 8080/tcp entrypoint ["java", "-jar", "/app.jar"]

  3. docker build -t gcr.io//springbootdb-java:v1 .

  4. docker run -ti --rm -p 8080:8080 gcr.io//springbootdb-java:v1

  5. gcloud docker -- push gcr.io//springbootdb-java:v1

    follow 6th step given in link , create yaml file

  6. kubectl create -f cloudsql_deployment.yaml

    run kubectl deployment , copy name of deployment

  7. kubectl expose deployment --type=loadbalancer

my yaml file

apiversion: extensions/v1beta1 kind: deployment metadata: name: conversationally spec: replicas: 1 template: metadata: labels: app: conversationally spec: containers: - image: gcr.io/<project id>/springbootdb-java:v1 name: web env: - name: db_host # connect sql proxy on local network on fixed port. # change [port] port number used database # (e.g. 3306). value: 127.0.0.1:3306 # these secrets required start pod. # [start cloudsql_secrets] - name: db_password valuefrom: secretkeyref: name: cloudsql-db-credentials key: password - name: db_user valuefrom: secretkeyref: name: cloudsql-db-credentials key: username # [end cloudsql_secrets] ports: - containerport: 8080 name: conv-cluster # change [instance_connection_name] here include gcp # project, region of cloud sql instance , name # of cloud sql instance. format # $project:$region:$instance # insert port number used database. # [start proxy_container] - image: gcr.io/cloudsql-docker/gce-proxy:1.09 name: cloudsql-proxy command: ["/cloud_sql_proxy", "--dir=/cloudsql", "-instances=<instance name>=tcp:3306", "-credential_file=/secrets/cloudsql/credentials.json"] volumemounts: - name: cloudsql-instance-credentials mountpath: /secrets/cloudsql readonly: true - name: ssl-certs mountpath: /etc/ssl/certs - name: cloudsql mountpath: /cloudsql # [end proxy_container] # [start volumes] volumes: - name: cloudsql-instance-credentials secret: secretname: cloudsql-instance-credentials - name: ssl-certs hostpath: path: /etc/ssl/certs - name: cloudsql emptydir: # [end volumes]

===========


Comments

Post a Comment

Popular posts from this blog

Is there a better way to structure post methods in Class Based Views -

i'm using class based views in django , never specify url in ajax calls , omit action parameter in form because know these requests go through post method of class based view. notice view - profile page make many requests depending on user updating on page - post method become convoluted , if/else mess example: def post(self, request, *args, **kwargs): # handle user changing available date if request.post.get('availabledate') != none: self.updateavailabledate(request) return jsonresponse({'result':'success'}) if request.post.get('newprojectname') != none: creative_user = creativeuserprofile.objects.get(id = request.user.id) project = project.create_project(creative_user, request.post['newprojectname']) project.save() return jsonresponse({'projectid': project.id }) if request.post.get('projectimage') != none , request.files['file']: proj...
Read more

performance - Why is XCHG reg, reg a 3 micro-op instruction on modern Intel architectures? -

i'm doing micro-optimization on performance critical part of code , came across sequence of instructions (in at&t syntax): add %rax, %rbx mov %rdx, %rax mov %rbx, %rdx i thought had use case xchg allow me shave instruction , write: add %rbx, %rax xchg %rax, %rdx however, dimay found agner fog's instruction tables , xchg 3 micro-op instruction 2 cycle latency on sandy bridge, ivy bridge, broadwell, haswell , skylake. 3 whole micro-ops , 2 cycles of latency! 3 micro-ops throws off 4-1-1-1 cadence , 2 cycle latency makes worse original in best case since last 2 instructions in original might execute in parallel. now... cpu might breaking instruction micro-ops equivalent to: mov %rax, %tmp mov %rdx, %rax mov %tmp, %rdx where tmp anonymous internal register , suppose last 2 micro-ops run in parallel latency 2 cycles. given register renaming occurs on these micro-architectures, though, doesn't make sense me done way. why wouldn't register renamer ...
Read more

c# - Asp.net web api : redirect unauthorized requst to forbidden page -

im trying redirect unauthorized request forbidden page instead i'm getting forbidden page in response body , how can fix ? here's startup class : app.createperowincontext(storecontext.create); app.createperowincontext<applicationusermanager>(applicationusermanager.create); app.createperowincontext<applicationsigninmanager>(applicationsigninmanager.create); app.usecookieauthentication(new cookieauthenticationoptions { authenticationtype = defaultauthenticationtypes.applicationcookie, expiretimespan = timespan.fromdays(30), }); app.useexternalsignincookie(defaultauthenticationtypes.externalcookie); app.usetwofactorsignincookie(defaultauthenticationtypes.twofactorcookie, timespan.fromminutes(5)); app.usetwofactorrememberbrowsercookie(defaultauthenticationtypes.twofactorrememberbrowsercookie); the method im trying reach : [httpget] [authorize(roles = "admin")] public string getcurrentusername() { return userman...
Read more