blob: 5308abf1340bd141cc3339d06195242148565df5 [file] [log] [blame]
Samuli Silviuse687cc72019-02-12 15:05:55 +02001---
2#
3# Master playbook to run offline installer.
Petr Ospalý89ee9e42019-02-15 03:36:10 +01004# Run this playbook e.g. with command: ./run_playbook.sh -e @application/application_configuration.yml site.yml
Samuli Silviuse687cc72019-02-12 15:05:55 +02005#
6
Petr Ospalý89ee9e42019-02-15 03:36:10 +01007# the setup.yml playbook is excluded from this list for the following reasons:
8# 1. setup.yml playbook requires either already deployed ssh key or
9# --ask-pass argument to interactively distribute a new key, which may
10# be a redundant effort if you already secured passwordless login
11# 2. Also, the setup.yml playbook is not mandatory and can be replaced with
12# manual or semi-manual steps with ssh-copy-id command or other
13# 3. playbooks here are more or less batch jobs and the ssh authentication
14# is a precondition, which should be done during configuration of the
15# installer
Samuli Silvius29886f02019-02-19 16:00:37 +020016- import_playbook: resources.yml
Samuli Silviuse687cc72019-02-12 15:05:55 +020017- import_playbook: infrastructure.yml
Bartek Grzybowskicf6797c2019-05-22 14:53:31 +020018- import_playbook: rke.yml
Bartek Grzybowskicacb2eb2021-06-11 13:16:10 +020019- import_playbook: nfs.yml
Bartek Grzybowski74ff05d2021-06-01 13:14:39 +020020- import_playbook: kube_prometheus.yml
21 when: kube_prometheus_stack_enabled
Bartek Grzybowskid17900b2021-11-10 12:23:07 +010022- import_playbook: cert_manager.yml
Samuli Silviuse687cc72019-02-12 15:05:55 +020023- import_playbook: application.yml