1ecac43e0d
New classes and scripts are added to handle sm, kubelet, kubeadm, kube-proxy, calico, multus, and certsans. New variables exported to the hiera are used in this change, in conjunction with the existing ones: platform::kubernetes::params::node_ip_secondary platform::network::cluster_pod::params::* platform::network::cluster_pod::ipv4::params:: platform::network::cluster_pod::ipv6::params::* platform::network::cluster_service::params::* platform::network::cluster_service::ipv4::params:: platform::network::cluster_service::ipv6::params::* Test Plan: ========== In all tests pods were brought up and the datapath was validated directly and through a service [PASS] in AIO-DX IPv4, configure dual-stack and back to single-stack [PASS] in AIO-DX IPv6, configure dual-stack and back to single-stack [PASS] in AIO-SX IPv4, configure dual-stack and back to single-stack [PASS] in AIO-SX IPv6, configure dual-stack and back to single-stack [PASS] in Standard IPv4, configure dual-stack and back to single-stack [PASS] in Standard IPv6, configure dual-stack and back to single-stack Story: 2011027 Task: 50203 Change-Id: Ifb908c097960f90c5eabeca8cc02d2f60ae4d731 Signed-off-by: Andre Kantek <andrefernandozanella.kantek@windriver.com>
stx-puppet
The starlingx/stx-puppet repository handles the Puppet service1.
The Puppet service runs during bootstrap, and at every reboot, to provide a consistent configuration across the StarlingX system nodes.
This repository is not intended to be developed standalone, but rather as part of the StarlingX Source System, which is defined by the StarlingX manifest2.