kubernetes-azure | diagram depicts how a Kubernetes cluster | Runtime Evironment library

by khenidak Shell Version: Current License: MIT

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | kubernetes-azure Summary

kubernetes-azure is a Shell library typically used in Server, Runtime Evironment, Nodejs, Docker applications. kubernetes-azure has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

The above diagram depicts how a Kubernetes cluster will work on Azure. The following notes explain the approach further:.

Support

Quality

Security

License

Reuse

Support

kubernetes-azure has a low active ecosystem.

It has 10 star(s) with 1 fork(s). There are 4 watchers for this library.

It had no major release in the last 6 months.

There are 1 open issues and 0 have been closed. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of kubernetes-azure is current.

Quality

kubernetes-azure has no bugs reported.

Security

kubernetes-azure has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

kubernetes-azure is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

kubernetes-azure releases are not available. You will need to build from source code and install.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of kubernetes-azure

Get all kandi verified functions for this library.

kubernetes-azure Key Features

No Key Features are available at this moment for kubernetes-azure.

kubernetes-azure Examples and Code Snippets

No Code Snippets are available at this moment for kubernetes-azure.

Community Discussions

Trending Discussions on kubernetes-azure

Azure DevOps > Helm > Azure Kubernetes Deployment - Deletes Azure File share when deployment is deleted

QUESTION

Azure DevOps > Helm > Azure Kubernetes Deployment - Deletes Azure File share when deployment is deleted

Asked 2019-Feb-20 at 01:22

TL;DR

My pods mounted Azure file shares are (inconsistently) being deleted by either Kubernetes / Helm when deleting a deployment.

Explanation

I've recently transitioned to using Helm for deploying Kubernetes objects on my Azure Kubernetes Cluster via the DevOps release pipeline.

I've started to see some unexpected behaviour in relation to the Azure File Shares that I mount to my Pods (as Persistent Volumes with associated Persistent Volume Claims and a Storage Class) as part of the deployment.

Whilst I've been finalising my deployment, I've been pushing out the deployment via the Azure Devops release pipeline using the built in Helm tasks, which have been working fine. When I've wanted to fix / improve the process I've then either manually deleted the objects on the Kubernetes Dashboard (UI), or used Powershell (command line) to delete the deployment.

For example:

...

ANSWER

Answered 2019-Feb-20 at 01:22

Credit goes to https://twitter.com/tomasrestrepo here on pointing me in the right direction (the author of the article I mentioned above).

The behaviour here was a consequence of having the Reclaim Policy on the Storage Class & Persistent Volume set to "Delete". When switching over to Helm, I began following their commands to Delete / Purge the releases as I was testing. What I didn't realise, was that deleting the release would also mean that Helm / K8s would also reach out and delete the underlying Volume (in this case an Azure Fileshare). This is documented over at: https://kubernetes.io/docs/concepts/storage/persistent-volumes/#delete

I'll leave this Q & A here for anyone else that misses this subtly with the way in which the Storage Classes, Persistent Volumes (PVs) & underlying storage operates under K8s / Helm.

Note: I think this issue was made slightly more obscure by the fact I was manually creating the Azure Fileshare (through the Azure Portal) and trying to mount that as a static volume (as per https://docs.microsoft.com/en-us/azure/aks/azure-files-volume) within my Helm Chart, but that the underlying volume wasn't immediately being deleted when the release was deleted (sometimes an hour later?).

Source https://stackoverflow.com/questions/54759142

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install kubernetes-azure

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: