Update K8s and Helm for Dublin Release

Environment

None

OOM Description

None

Activity

Show:

Former user April 17, 2019 at 8:56 AM

Hi , please confirm that this will be delivered for the Dublin release. If not please adjust accordingly. Thanks!

Former user November 15, 2018 at 3:29 PM

 

Former user November 7, 2018 at 1:55 AM

the cluster seems to work fine under 1.6.22/k8s1.11 - 14+1 VMs (8 vCores/16Gb ram) - k8s node ram: 187G, k8s overall ram(onap): 102G, vCore idle: 19, avail ram: 224G, avail vCPU: 112, HD: 6G master, 16-40G cluster-vms, NFS: 9G, total pods: 241-onap, 217 up (216 on a 13 vm cluster) - 0 !! failures, healthcheck 49/51 (dmaap, holmes, holmes failures) - all details under https://wiki.onap.org/display/DW/Cloud+Native+Deployment#CloudNativeDeployment-WithONAPdeployed

Former user November 5, 2018 at 7:23 PM

See related
align with official
https://onap.readthedocs.io/en/latest/guides/onap-developer/settingup/onap_oom.html

Integration has moved up to 1.6.22 - need to investigate k8s versions and scope the official update on our side
Since casablanca is at RC2 right now - likely this will be a Dublin change - pending any fix required in 1.11

https://git.onap.org/integration/tree/deployment/heat/onap-oom/onap-oom.yaml#n68

old
k8s 1.10.3
agent 1.2.10

new
rancher_version:
type: string
default: "1.6.22"

rancher_agent_version:
type: string
default: "1.2.11"

kubectl_version:
type: string
default: "1.11.2"

Done

Details

Assignee

Reporter

Fix versions

Affects versions

Priority

Created November 1, 2018 at 6:40 PM
Updated July 10, 2019 at 5:38 PM
Resolved May 1, 2019 at 11:57 AM