https://github.com/beemi/jaitechltd-common-apps
Helm releases for all applications
https://github.com/beemi/jaitechltd-common-apps
Last synced: 4 months ago
JSON representation
Helm releases for all applications
- Host: GitHub
- URL: https://github.com/beemi/jaitechltd-common-apps
- Owner: beemi
- License: mit
- Created: 2022-03-27T13:52:20.000Z (about 4 years ago)
- Default Branch: main
- Last Pushed: 2023-12-15T20:29:04.000Z (over 2 years ago)
- Last Synced: 2025-09-07T11:53:11.376Z (9 months ago)
- Language: Smarty
- Size: 104 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# jaitechltd-common-apps
Helm releases for all applications, The package manager for Kubernetes
## Prerequisites
### Install Helm
```shell
brew install helm
```
### Install kubectl
```shell
brew install kubectl
```
### Install kubectx
```shell
brew install kubectx
```
### Install kubens
```shell
brew install kubens
```
### Install minikube
```shell
brew install minikube
```
### Minikube commands
```shell
minikube status
minikube start
minikube stop
minikube delete
minikube logs
minikube dashboard
```
### Install k9s
https://k9scli.io/
```shell
brew install k9s
```
## Chart.yaml:
A Chart is a Helm package. It contains all of the resource definitions necessary to run an application, tool, or service inside of a Kubernetes cluster. Think of it like the Kubernetes equivalent of a Homebrew formula, an Apt dpkg, or a Yum RPM file.
## Release:
A Release is an instance of a chart running in a Kubernetes cluster. One chart can often be installed many times into the same cluster. And each time it is installed, a new release is created. Consider a MySQL chart. If you want two databases running in your cluster, you can install that chart twice. Each one will have its own release, which will in turn have its own release name.
create a new helm chart with the following command:
```shell
helm create latlong-app --namespace=jaitechltd
```
Chart.yaml
values.yaml
deployment.yaml
service.yaml
### Helm template
```shell
helm template latlong-app --namespace=jaitechltd > latlong-app.yaml
```
```shell
helm template latlong-javaservice --namespace=jaitechltd > latlong-javaservice.yaml
```
### Helm lint
```shell
helm lint latlong-app.yaml
```
### Helm dry run
```shell
helm install latlong-app --debug --dry-run latlong-app
```
### Helm install
install a chart with the following command:
```shell
helm install latlong latlong-app --namespace=jaitechltd
```
```shell
helm install latlong-javaservice latlong-javaservice --namespace=jaitechltd
```
### Helm get list of releases
```shell
helm list --namespace=jaitechltd
```
Delete a release with the following command:
```shell
helm delete latlong --namespace=jaitechltd
```
```shell
helm delete latlong-javaservice --namespace=jaitechltd
```
# Kubernetes
Kubernetes get running nodes from cluster
```shell
kubectl get nodes -A
```
(or)
```shell
kubectl get nodes -n
```
Kubernetes get all contexts
```shell
kubectl config get-contexts
```
Switch to a context with the following command:
```shell
kubectl config use-context
```
Example:
```shell
kubectl config use-context minikube
```
Create a new namespace with the following command:
```shell
kubectl create namespace
```
Example:
```shell
kubectl create namespace jaitechltd
```
Get all namespaces with the following command:
```shell
kubectl get namespace
```
Get all pods in a namespace with the following command:
```shell
kubectl get pods --namespace=jaitechltd
```
Get all pods in all namespaces with the following command:
```shell
kubectl get deployments
```
Delete pods from a namespace
```shell
kuectl delete pods --all --namespace=jaitechltd
```
```shell
kubectl delete pod --namespace=jaitechltd
```
## :e-mail: Contacts
Owner: [beemi.raja@gmail.com](beemi.raja@gmail.com)