- MTU added as param
- Config refactored for calico ge 1.4
- MASTER_IP added
Murano spawns VM with MTU set for 1400. We should use use lower setting
for calico mesh network.
Closes-Bug: #1626999
Change-Id: I77efb3ae2abaf7c2705524b6e8b78e83c30f34e3
Added How Murano installs Kubernetes Cluster
Added How Murano upgrades Kubernetes Cluster
Minor updates on Networking
Fixed broken links
Added detailed info on Calico
Change-Id: Ic1538b33fa79ba0bb772a442dfc7c0a5db3a2e97
Following sections has been addedd:
* Features
* Rolling Updates of Kubernetes application
* Interacting with Kubernetes Cluster deployed by Murano
Co-Authored-By: Nikolay Mahotkin <nmakhotkin@mirantis.com>
Change-Id: I7d7572d6c53c9f6f0165ff55fa4d0ed5abdedef9
- binaries and scripts updated to use calico networking
Co-Authored-By: ddovbii <ddovbii@mirantis.com>
Change-Id: I3187b9cc171aa15caa4912a665c642ab057b4eae
1. default_scripts/kube-apiserver parametres updates:
Replaced: address, ports with insecure-bind-address, insecure-port
Added: service-cluster-ip-range, admission-control, advertise-address
Depricated: portal_net
2. environ/apiserver parametres updates:
Updated: KUBE_API_ADDRESS, KUBE_API_PORTS
Added: KUBE_API_IP
Depricated: KUBE_API_ARGS
3. systemd/kube-apiserver.service parametres updates:
Added: KUBE_API_IP
Update: KUBE_SERVICE_ADDRESSES with KUBE_SERVICE
Depricated: KUBE_API_ARGS
4. default_scripts/kube-controller-manager updates:
Added: New params for KUBE_CONTROLLER_MANAGER_OPTS such as
service-cluster-ip-range, cluster-cidr, cluster-name
5. systemd/kube-controller-manager.service updates:
Added: new argumunets to start up command such as
KUBE_SERVICE, KUBE_NAME, KUBE_CIDR
Removed: KUBE_CONTROLLER_MANAGER_ARGS
6. kube-config updates with new
Added new argumunets to start up command such as
KUBE_SERVICE, KUBE_NAME, KUBE_CIDR
7. scripts/master-kube-setup.sh update:
Set Master IP value for apiserver and kube-apiserver scripts
Change-Id: I808ef5459e5fd5f1f5c916ddd3f94beab05e5c5d
Scenario:
1. Create murano environment
2. Create session for create environment.
3. Initialize k8s cluster parameters and add app to env.
4. Initialize k8s pod parameters and add app to env.
5. Deploy session.
7. Check env status and port availability on k8s master node.
8. Get k8s minions' ips and check that correct initial number
of them was created and k8s api port is available on them.
9. Run 'scaleNodesUp' action for k8s minions.
10. Check that number of minions was increased and
k8s api port is available on all of them
11. Run 'scaleNodesDown' action for k8s minions.
12. Check that number of minions was decreased and
k8s api port is available on all of them
Change-Id: I63bf61b6f9e5fd45b8e6bde0fab87da5826bedc6
This commit does not resolve a bug with docker0 due to the fact
that murano-agent is unable to execute script for reconfiguration
So, this patch reverts commit 6547024fa3.
Change-Id: Ic522d54b14ade7878ce2c6b5729c1e117c329551
For running k8s and docker autotests against this repo
we need to prepare and upload packages first.
This is a POC of script, it should be refactored and improved in
future, but for now we need to have some prototype somewhere, otherwise
it will be hardcoded in jenkins job.
Change-Id: I58c7965b275dd3a86de69f9e341c61edc04cc976
