Ingo Oppermann b5976f37f0 Start cluster after core API has been started ...

The core API will be started before the cluster is started in order to
access the cluster endpoints during a cluster upgrade. If TLS is enabled,
possibly stale certificates are loaded into the cache. Otherwise the
leader has to be contacted via the cluster API which might have changed.

2023-07-10 16:24:08 +02:00

..

autocert

Add CORE_TLS_SECRET configuration

2023-07-03 16:02:39 +02:00

client

Use clone of http.Transport defaults

2023-07-07 11:23:41 +02:00

docs

Check for equal FFmpeg skills, remove /v1/version

2023-07-06 16:12:06 +02:00

forwarder

Use clone of http.Transport defaults

2023-07-07 11:23:41 +02:00

iam

Return error on reload on encountering an invalid identity

2023-06-26 14:05:22 +02:00

kvs

Add CORE_TLS_SECRET configuration

2023-07-03 16:02:39 +02:00

logger

Fix logging

2023-05-11 16:12:41 +02:00

node

Cleanup of cluster proxy and proxy node

2023-07-07 22:51:53 +02:00

proxy

Cleanup of cluster proxy and proxy node

2023-07-07 22:51:53 +02:00

raft

Add /v3/cluster/snapshot endpoint

2023-06-27 15:11:31 +02:00

store

Fix cluster process update on metadata change

2023-06-28 16:26:36 +02:00

api.go

Start cluster after core API has been started

2023-07-10 16:24:08 +02:00

cluster.go

Start cluster after core API has been started

2023-07-10 16:24:08 +02:00

follower.go

Adjusting naming of functions

2023-06-08 14:48:28 +02:00

iam.go

Rearrange code

2023-07-03 20:39:47 +02:00

kvs.go

Start cluster after core API has been started

2023-07-10 16:24:08 +02:00

leader_test.go

Deploy processes with order stop to nodes

2023-07-05 09:55:11 +02:00

leader.go

Deploy processes with order stop to nodes

2023-07-05 09:55:11 +02:00

process.go

Add /api/v3/cluster/process/:id/probe endpoint

2023-07-05 11:03:45 +02:00

version.go

Start cluster after core API has been started

2023-07-10 16:24:08 +02:00