make HA clustered mode the default for Docker and Linux distributions of ziti controller #2872
+904
−367
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
599e6ae to
b282d56
Compare
|
Docker and Linux deployments are 90%. I'm planning to re-add database init now that it's more clear how to accomplish that in a reverse-compatible way. |
dovholuknf
reviewed
Mar 14, 2025
b282d56 to
98dd0d0
Compare
ee64660 to
b90caff
Compare
d3c26e6 to
bcff633
Compare
143d0bb to
017297e
Compare
017297e to
bbcb94c
Compare
|
Can you squash this when you merge, please? |
plorenz
approved these changes
Jun 10, 2025
ed0774c to
80cb3da
Compare
|
I'm waiting for the clustered mode beta to be promoted to GA before I ship this change to use clustered mode by default in production Docker and Linux deployments. |
80cb3da to
75d24c4
Compare
75d24c4 to
4e757be
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bootstrap a new cluster (
spiffe://ziti.example.com/controller/ctrl1) with any of the following:# explicit node name, trust domain, and address ZITI_CLUSTER_NODE_NAME=ctrl1 ZITI_CLUSTER_TRUST_DOMAIN=ziti.example.com ZITI_CTRL_ADVERTISED_ADDRESS=ctrl1.ziti.example.comor
ZITI_CLUSTER_NODE_NAME=ctrl1 ZITI_CLUSTER_TRUST_DOMAIN=ziti.example.com # ZITI_CTRL_ADVERTISED_ADDRESS=ctrl1.ziti.example.com # implied addressor
Join an existing cluster with:
...or by building the new joiner's address with node name and trust name.
where ZITI_CLUSTER_NODE_PKI is a tree like:
├── intermediate │ ├── certs │ │ ├── client.cert │ │ ├── client.chain.pem │ │ ├── intermediate.cert │ │ ├── intermediate.chain.pem │ │ ├── server.cert │ │ └── server.chain.pem │ ├── crlnumber │ ├── crls │ ├── index.txt │ ├── index.txt.attr │ ├── keys │ │ ├── client.key │ │ ├── intermediate.key │ │ └── server.key │ └── serial └── root ├── certs │ ├── intermediate.cert │ └── root.cert ├── crlnumber ├── crls ├── index.txt ├── index.txt.attr ├── keys └── serialwhich can be created with
tar -cvf /tmp/ctrl2.tar --exclude root/keys/ ./ziti-controller/pki/