I have syncope now running on Kubernetes and created a simple (two command) install with helm charts. Seems to work pretty well but there is room for growth. I will add liveness probes, readiness checks, and autoscaling for my own needs and would be happy to commit that as well. I also created a simple installation document to assist in the install.
I tried to commit it but don't have access to the github repo. Can someone grant me access (username: mornindew)? I was going to create a feature branch off of master and let you all PR it, is that correct? *Small comment and maybe feature request:* The Syncope Bootstrap is very coupled to the database (obviously) but it doesn't handle very well if it cannot connect to the DB on startup(e.g. retrys or circuit breaking). K8s is actually pretty opinionated that you shouldn't create tight coupling like this and it should auto heal itself. It would be nice if Syncope-core was a bit more resiliant and could poll or retry. This would make installation only one command (as opposed to two) but more importantly could help it recover if there is a connection issue. Thank you all for your stuff, I am happy to be digging deeper into it. Cool stuff!!! Craig On Mon, Aug 6, 2018 at 4:03 PM craig <craigma...@gmail.com> wrote: > I am setting up syncope in Kubernetes. I will be happy to contribute my > yamls once I get it running as it doesn't seem to be a common setup for > Syncope. I am new to Syncope and I am having some issues. > > I was able to get the docker-compose examples working just fine but having > connectivity issues when running in K8s. Without knowing Syncope (or even > postgres) that well I am struggling on where to start. > > Issue: Syncope cannot connect to postgres:5432 > > 20:49:13.640 ERROR > org.flowable.common.engine.impl.AbstractEngineConfiguration - Exception > while initializing Database connection > org.postgresql.util.PSQLException: Connection to postgres:5432 refused. > Check that the hostname and port are correct and that the postmaster is > accepting TCP/IP connections. > at > > org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:245) > ~[postgresql-42.2.2.jar:42.2.2] > at > > org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:49) > ~[postgresql-42.2.2.jar:42.2.2] > at org.postgresql.jdbc.PgConnection.<init>(PgConnection.java:195) > ~[postgresql-42.2.2.jar:42.2.2] > at org.postgresql.Driver.makeConnection(Driver.java:452) > ~[postgresql-42.2.2.jar:42.2.2] > at org.postgresql.Driver.connect(Driver.java:254) > ~[postgresql-42.2.2.jar:42.2.2] > at > > com.zaxxer.hikari.util.DriverDataSource.getConnection(DriverDataSource.java:136) > ~[HikariCP-3.2.0.jar:?] > at com.zaxxer.hikari.pool.PoolBase.newConnection(PoolBase.java:369) > ~[HikariCP-3.2.0.jar:?] > at com.zaxxer.hikari.pool.PoolBase.newPoolEntry(PoolBase.java:198) > ~[HikariCP-3.2.0.jar:?] > at > com.zaxxer.hikari.pool.HikariPool.createPoolEntry(HikariPool.java:467) > ~[HikariCP-3.2.0.jar:?] > at > com.zaxxer.hikari.pool.HikariPool.checkFailFast(HikariPool.java:541) > ~[HikariCP-3.2.0.jar:?] > at com.zaxxer.hikari.pool.HikariPool.<init>(HikariPool.java:115) > ~[HikariCP-3.2.0.jar:?] > at > com.zaxxer.hikari.HikariDataSource.getConnection(HikariDataSource.java:112) > ~[HikariCP-3.2.0.jar:?] > > > Things that I did: > > 1) Connect to database directly from postgres container command line "psql > -U syncope" > 2) Connect to database from syncope conatiner command line "psql -U > syncope > -h postgres" > 3) Confirm that the port 5432 is open by running the command "telnet > postgres 5432" and it was open > 4) Confirm that both a database named "syncope" and user named "syncope" > exist in the postgres database > 5) Confirmed the configuration of K8s looks correct. The port appears to > be up, the replica sets look correct > > Any help or guidance on things to look at would be helpful. > > Craig > > > -- > Sent from: http://syncope-user.1051894.n5.nabble.com/ >
