Few changes for default helm chart on github: Few new features only available in new components images(e.g authorization), so update your images. New Fron50 requires adding Credentials into /home/spinnaker/.aws, so make sure you mount it correctly: "volumeMounts": [ { "name": "spinnaker-spinnaker-spinnaker-config", "mountPath": "/opt/spinnaker/config" }, { "name": "spinnaker-spinnaker-s3-config", "mountPath": "/root/.aws" }, { "name": "spinnaker-spinnaker-s3-config", "mountPath": "/home/spinnaker/.aws" } ], To enable authentication and authorization, you need to configure Gate and Fiat.

Continue reading

Overview Openstack-Helm is AT&T leaded project to deploy Openstack on top of Kubernetes using Helm, it offers version control and k8s advantages which includes HA, PaaS, RollingUpdate, etc. It’s an advanced version of Kolla. Github Projects Explorer cni/bin #CNI resource pool openstack-helm-infra #helm charts for infra (k8s) openstack-helm #helm charts for openstack components vancouver-workshop #Single node example Folder Explorer Under openstack-helm/tools/deployment/ you’ll see: armada #Openstack-Helm centralized Yaml providing life-cycle hooks baremetal #Install Openstack-Helm on Baremetal K8s common #Generic for all scenario developer #Multiple k8s scenario for single node deployment multinode #Prod ready multinode Install example single node: Kubernetes and Common Setup $ cd /opt/openstack-helm $ .

Continue reading

Fabric8 hints

Install Fabric8 on k8s by using helm k8s needs to integrated properly with openstack, it needs to use cinder pv storageclass standard and LBaas. besides, configmap for exposecontroller need to be changed for: “data”: { “config.yml”: “exposer: "LoadBalancer"\n” } to make it use openstack LBaas to automatically create LB for each deployed service. gogs may failed because of insufficient permission on cinder mounted folder, to fix this, need to find out where gogs resides and where data-gogs mounted, and chmod 777 -R it.

Continue reading

Helm hints

on kube 1.9, if run “helm install” any package, will give error like “no available release name found”, the following cmd fixes it. kubectl create serviceaccount --namespace kube-system tiller kubectl create clusterrolebinding tiller-cluster-rule --clusterrole=cluster-admin --serviceaccount=kube-system:tiller kubectl patch deploy --namespace kube-system tiller-deploy -p '{"spec":{"template":{"spec":{"serviceAccount":"tiller"}}}}' you can customize helm chart by modify default chart parameters, using helm inspect stable/mysql can show you parameters allowed to be changed. Simply pick up the parameters you’d like to change and save them into mariadb.

Continue reading

Author's picture

LuLU

Love coding and new technologies

Cloud Solution Consultant

Canada