New video on Containerized app deployment -- Kubernetes with Calm


Userlevel 3
Badge +15
David Keefe from Nutanix Services has created another excellent video showing how to deploy K8s on Nutanix using the sample blueprint published to the Calm Marketplace. The video also shows how to create a Calm blueprint for a custom containerized application deployed on the K8s cluster. Lastly, it also covers application lifecycle operations, such as scaling containers up and down, and perform an upgrade of the application using Calm actions.


For more information on Nutanix Calm including signing up for a demo, visit www.nutanix.com/calm. You can also send a note to our services consulting team to learn how they can help automate application lifecycle management for complex multi-tier applications -- services@nutanix.com.

PS. Nutanix is hosting our first ever .NEXT Hackathon in New Orleans in May with categories around application automation (potentially using Calm), management automation, and next generation tech. Interested in participating -- submit your nomination and read more about the event at www.nutanix.com/next/hackathon.

2 replies

Badge
I'm not familiar with how Kubernetes works -
Can you please provide some background on the network requirements for the demo environment being created. Which network values are internal while which are actually used on the vlan defined in the blueprint?


Cluster_Subnet
(Mandatory) Cluster subnet used by CNI between minion nodes.
Service_Subnet
(Mandatory) Service subnet used to access services.
Kube_Cluster_DNS
(Mandatory) Cluster DNS IP within Service_Subnet range.
Prism_Cluster_IP
(Optional) Nutanix Prism IP address for volume plug-in.
Prism_Data_Service_IP
(Optional) Data service IP address.
Prism_Username
(Optional) Prism username.
Prism_Password
(Optional) Prism password.
Container_Name
(Optional) Container name where VG needs to be created.
Hi Daiyu,

CLUSTER_SUBNET : This is a internal network subnet used by pods. Primarily for Pod - Pod communication across different nodes. you should not access this ip directly as there is no guarantee that the address won’t change the next time the pod is recreated. example 10.200.0.0/16

SERVICE_SUBNET: This Subnet is a pool of Ip's which acts as Virtual IP's that proxy and load-balances the requests to the pods that span across nodes. This should be a unique subnet inside your lab setup. You can use these IP's to access the services from extenal applications (browser). example 192.168.0.0/24

KUBE_CLUSTER_DNS: This is a single ip in your SERVICE_SUBNET which will be used by kube-dns service for dns resolution. example 192.168.0.10


For more on kubernetes networking : https://medium.com/google-cloud/understanding-kubernetes-networking-services-f0cb48e4cc82

Reply