Skip to content

A best practices Helm chart for simplifying Kubernetes CI/CD deployments.

License

Notifications You must be signed in to change notification settings

snowball77/helm-charts

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

7 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Genero

Genero is a best practices Helm chart for greatly simplifying Kubernetes deployments.

Genero was designed to deploy applications from a CI/CD pipeline.

It is also helpful for easily deploying applications that don't have an official Helm chart.

Prerequisites

  • Kubernetes 1.16+
  • Helm 3+

Get Repo

helm repo add polymatic https://polymatic-systems.github.io/helm-charts
helm repo update

Usage

For a full explanation on both using Genero for pipelines and standalone deployments, read the blog here:

https://blog.polymatic.systems/genero-3f788f2167a7

sample values file

A simple Genero values file looks like this (what a dev would store in their app repo):

variables:
- name: env
  data:
    ENV: "production"
    TOKEN: "xyz123"

containers:
- name: app
  ports:
    - containerPort: 3000
  cpu:
    request: 100m
    limit: 1000m
  memory:
    request: 256Mi
    limit: 1Gi

ingress:
- name: app
  urls:
    - app.test.site

hpa:
  min: 3
  max: 10
  cpu: 70

Third-Party Features

Genero assumes that cert-manager is installed if you are provisioning ingresses. If you don't have cert-manager installed, you need to specify the tls secret when adding an ingress. There is no option to enable http, the ingress must be https.

Configuration

About

A best practices Helm chart for simplifying Kubernetes CI/CD deployments.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Shell 87.3%
  • Smarty 12.7%