Files F117750650

README.md
No OneTemporary
Actions

Authored By

Unknown

Size

893 B

Referenced Files

None

Subscribers

None

README.md
View Options

	This is an example of a replicated deployment on two nodes.

	The initial configuration is done via the inventory.yaml file.

	'make ansible' will execute the ansible playbook which will provision vm's and deploy kolab on them using k3s.

	* make ansible: Provision the vm's via ansible
	* make connect-infra1/connect-infra2/connect-worker1/connect-worker2: Connect via ssh to the relevant instance
	* make deploy: (Re-)Deploy kolab. The ansible scripts will trigger the initial deployment, but after a change to the values.yaml file, kolab can be redeployed using "make deploy".
	* make apply: (Re-)Deploy kolab. This will deploy the changes by generating an inflated.yaml file, show a diff to what is currently running, and then after confirmation apply the changeset. This is recommented for a git-ops approach as inflated.yaml can be tracked in git to have a record of what's currently running.

File Metadata

Mime Type: text/plain
Expires: Sat, Apr 4, 2:34 AM (1 w, 1 d ago)
Storage Engine: local-disk
Storage Format: Raw Data
Storage Handle: fb/83/f31aaaad89bb9eb8272d95e22883
Default Alt Text: README.md (893 B)

Event Timeline