Go to file
Matt Peters 26fd273cf5 Add kube-apiserver port to calico failsafe rules
An invalid GlobalNetworkPolicy or NetworkPolicy may prevent
calico-node from communicating with the kube-apiserver.
Once the communication is broken, calico-node is no longer
able to update the policies since it cannot communicate to
read the updated policies.  It can also prevent the pod
from starting since the policies will prevent it from
reading the configuration.

To ensure that this scenario does not happen, the kube-apiserver
port is being added to the failsafe rules to ensure communication
is always possible, regardless of the network policy configuration.

Change-Id: I1b065a74e7ad0ba9b1fdba4b63136b97efbe98ce
Closes-Bug: 1877166
Related-Bug: 1877383
Signed-off-by: Matt Peters <matt.peters@windriver.com>
2020-05-07 14:50:02 -05:00
2019-06-15 14:03:07 -05:00
2019-06-15 14:21:19 -05:00
2019-06-15 14:21:19 -05:00
2019-06-15 14:21:19 -05:00

stx-ansible-playbooks

StarlingX Bootstrap and Deployment Playbooks

Execution environment

  • Unix like OS (recent Linux based distributions, MacOS, Cygwin)
  • Python 2.7

Additional Required Packages

The playbooks in this repo have been verified with the following versions of Ansible and StarlingX playbooks dependencies:

  • sshpass 1.06
  • python2-ptyprocess 0.5
  • python2-pexpect 4.6
  • python2-netaddr 0.7
  • ansible 2.7.5

Supported StarlingX Releases

The playbooks in this repo are compatible with the following StarlingX releases:

  • 20.01

Executing StarlingX Playbooks

Executing Bootstrap Playbook

Please refer to StarlingX Deployment Guides, section Configuration controller-0 of the respective system configuration for instructions on how to set up and execute the bootstrap playbook from another host.

References

Description
StarlingX Ansible Playbooks
Readme 34 MiB
Languages
Jinja 73.1%
Python 17.4%
Shell 6.5%
Smarty 2.9%