Skip to content
Snippets Groups Projects
Commit 10f2f611 authored by Thibaud DANDOY's avatar Thibaud DANDOY
Browse files

initial commit

parent 8a6c97e9
No related branches found
No related tags found
No related merge requests found
Showing
with 442 additions and 93 deletions
apiVersion: v2
name: cdb
description: All applications in the cdb ecosystem
# A chart can be either an 'application' or a 'library' chart.
#
# Application charts are a collection of templates that can be packaged into versioned archives
# to be deployed.
#
# Library charts provide useful utilities or functions for the chart developer. They're included as
# a dependency of application charts to inject those utilities and functions into the rendering
# pipeline. Library charts do not define any templates and therefore cannot be deployed.
type: application
# This is the chart version. This version number should be incremented each time you make changes
# to the chart and its templates, including the app version.
# Versions are expected to follow Semantic Versioning (https://semver.org/)
version: 0.1.0
# This is the version number of the application being deployed. This version number should be
# incremented each time you make changes to the application. Versions are not expected to
# follow Semantic Versioning. They should reflect the version the application is using.
appVersion: snapshot
maintainers:
- name: takiformation
email: takiformation@takima.school
# ch3-gitops
## Getting started
To make it easy for you to get started with GitLab, here's a list of recommended next steps.
Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
## Add your files
- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
```
cd existing_repo
git remote add origin https://gitlab.takima.io/tdandoy/ch3-gitops.git
git branch -M main
git push -uf origin main
```
## Integrate with your tools
- [ ] [Set up project integrations](https://gitlab.takima.io/tdandoy/ch3-gitops/-/settings/integrations)
## Collaborate with your team
- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
## Test and Deploy
Use the built-in continuous integration in GitLab.
- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
***
# Editing this README
When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
## Suggestions for a good README
Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
## Name
Choose a self-explaining name for your project.
## Description
Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
## Badges
On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
## Visuals
Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
## Installation
Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
## Usage
Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
## Support
Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
## Roadmap
If you have ideas for releases in the future, it is a good idea to list them in the README.
## Contributing
State if you are open to contributions and what your requirements are for accepting them.
For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
## Authors and acknowledgment
Show your appreciation to those who have contributed to the project.
## License
For open source projects, say how it is licensed.
## Project status
If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
{{/*
Expand the name of the chart.
*/}}
{{- define "MyAppCtx.name" -}}
{{- default .Chart.Name | trunc 63 | trimSuffix "-" }}
{{- end }}
{{/*
Application image tag
We select by default the Chart appVersion or an override in values
*/}}
{{- define "MyAppCtx.imageTag" }}
{{- $name := default .Chart.AppVersion .Values.image.tag }}
{{- printf "%s" $name }}
{{- end }}
{{/*
Create a default fully qualified app name.
We truncate at 63 chars because some Kubernetes name fields are limited to this (by the DNS naming spec).
*/}}
{{- define "MyAppCtx.fullname" }}
{{- $name := default .Chart.Name .Values.nameOverride -}}
{{- printf "%s-%s" .Release.Name $name | trunc 63 | trimSuffix "-"}}
{{- end }}
{{/*
Create chart name and version as used by the chart label.
*/}}
{{- define "MyAppCtx.chart" -}}
{{- printf "%s-%s" .Chart.Name .Chart.Version | replace "+" "_" | trunc 63 | trimSuffix "-" }}
{{- end }}
{{/*
Common labels
*/}}
{{- define "MyAppCtx.labels" -}}
helm.sh/chart: {{ include "MyAppCtx.chart" . }}
{{ include "MyAppCtx.selectorLabels" . }}
{{- if .Chart.AppVersion }}
app.kubernetes.io/version: {{ .Chart.AppVersion | quote }}
{{- end }}
app.kubernetes.io/managed-by: {{ .Release.Service }}
{{- end }}
{{/*
Selector labels
*/}}
{{- define "MyAppCtx.selectorLabels" -}}
app.kubernetes.io/name: {{ include "MyAppCtx.name" . }}
app.kubernetes.io/instance: {{ .Release.Name }}
{{- end }}
apiVersion: v1
kind: ConfigMap
metadata:
name: {{ .Values.api.name }}-config
data:
name: pg-service:5432
apiVersion: apps/v1
kind: Deployment
metadata:
name: {{ .Values.api.name }}-deployment
labels:
app: api
spec:
replicas: {{ .Values.api.replicaCount }}
selector:
matchLabels:
app: {{ .Values.api.name }}
template:
metadata:
labels:
app: {{ .Values.api.name }}
spec:
imagePullSecrets:
- name: takima-school-registry
containers:
- name: {{ .Values.api.name }}
securityContext:
runAsUser: 1001
runAsGroup: 1001
image: {{ .Values.api.image.repository }}:{{ .Values.api.image.tag }}
ports:
- containerPort: 8080
args:
- liveness
- readiness
livenessProbe:
failureThreshold: 5
httpGet:
path: /actuator/health/liveness
port: 8080
initialDelaySeconds: 15
periodSeconds: 3
readinessProbe:
failureThreshold: 5
httpGet:
path: /actuator/health/readiness
port: 8080
initialDelaySeconds: 15
periodSeconds: 3
env:
- name: DB_ENDPOINT
valueFrom:
configMapKeyRef:
name: {{ .Values.api.name }}-config
key: name
- name: POSTGRES_PASSWORD
valueFrom:
secretKeyRef:
name: {{ .Values.pg.name }}-credentials
key: password
- name: POSTGRES_USER
valueFrom:
secretKeyRef:
name: {{ .Values.pg.name }}-credentials
key: username
- name: POSTGRES_DB
valueFrom:
configMapKeyRef:
name: {{ .Values.pg.name }}-config
key: db-name
resources:
limits:
cpu: 2
memory: "256M"
requests:
cpu: "100m"
memory: "192M"
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: api-ingress
annotations:
cert-manager.io/cluster-issuer: letsencrypt-staging
kubernetes.io/tls-acme: 'true'
spec:
ingressClassName: nginx
rules:
- host: api.tdandoy.takima.school
http:
paths:
- backend:
service:
name: api-service
port:
number: 80
path: /
pathType: Prefix
tls:
- hosts:
- kube.tdandoy.takima.school
secretName: app-wildcard
apiVersion: v1
kind: Service
metadata:
name: {{ .Values.api.name }}-service
spec:
selector:
app: {{ .Values.api.name }}
ports:
- protocol: TCP
port: 80
targetPort: 8080
apiVersion: v1
kind: ConfigMap
metadata:
name: {{ .Values.pg.name }}-config
data:
db-name: "cdb-db"
db-path: "/var/lib/postgresql/data/pgdata"
apiVersion: v1
kind: Secret
metadata:
name: {{ .Values.pg.name }}-credentials
type: Opaque
data:
username: cG9vZg==
password: ZGVyZ2Vu
apiVersion: apps/v1
kind: Deployment
metadata:
name: {{ .Values.pg.name }}-deployment
labels:
app: {{ .Values.pg.name }}
spec:
replicas: 1
selector:
matchLabels:
app: {{ .Values.pg.name }}
template:
metadata:
labels:
app: {{ .Values.pg.name }}
spec:
volumes:
- name: {{ .Values.pg.name }}-data
persistentVolumeClaim:
claimName: {{ .Values.pg.name }}-db
imagePullSecrets:
- name: takima-school-registry
containers:
- name: {{ .Values.pg.name }}
volumeMounts:
- mountPath: /var/lib/postgresql/data
name: {{ .Values.pg.name }}-data
image: {{ .Values.pg.image.repository }}:{{ .Values.pg.image.tag }}
ports:
- containerPort: 5432
env:
- name: POSTGRES_PASSWORD
valueFrom:
secretKeyRef:
name: {{ .Values.pg.name }}-credentials
key: password
- name: POSTGRES_USER
valueFrom:
secretKeyRef:
name: {{ .Values.pg.name }}-credentials
key: username
- name: POSTGRES_DB
valueFrom:
configMapKeyRef:
name: {{ .Values.pg.name }}-config
key: db-name
- name: PGDATA
valueFrom:
configMapKeyRef:
name: {{ .Values.pg.name }}-config # Nom du configmap
key: db-path # nom de la clef dans le configMap contenant path où installer la db dans le volume persistant
resources:
limits:
cpu: 1
memory: "256M"
requests:
cpu: "100m"
memory: "192M"
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: {{ .Values.pg.name }}-db
spec:
storageClassName: gp2
accessModes:
- ReadWriteOnce
volumeMode: Filesystem
resources:
requests:
storage: 3Gi
apiVersion: v1
kind: Service
metadata:
name: {{ .Values.pg.name }}-service
spec:
selector:
app: {{ .Values.pg.name }}
ports:
- protocol: TCP
port: 5432
targetPort: 5432
{{- if .Values.front.enabled }}
{{- $apiUrl := "" }}
{{- if .Values.api.ingress.tlsEnabled }}
{{- $apiUrl = printf "https://%s" .Values.api.ingress.host | quote }}
{{- else }}
{{- $apiUrl = printf "http://%s" .Values.api.ingress.host | quote }}
{{- end }}
apiVersion: v1
kind: ConfigMap
metadata:
name: {{ .Values.front.name }}-front
data:
API_URL: {{ $apiUrl }}
{{- end }}
\ No newline at end of file
{{- if .Values.front.enabled }}
apiVersion: apps/v1
kind: Deployment
metadata:
name: {{ .Values.front.name }}-front
labels:
app: front
spec:
replicas: {{ .Values.front.replicaCount }}
selector:
matchLabels:
app: front
template:
metadata:
labels:
app: front
spec:
imagePullSecrets:
- name: takima-school-registry
securityContext:
runAsUser: 101
runAsGroup: 101
containers:
- name: front
image: {{ .Values.front.image.repository }}:{{ .Values.front.image.tag }}
imagePullPolicy: Always
ports:
- containerPort: 8080
resources:
requests:
memory: "32M"
cpu: "0.1"
limits:
memory: "128M"
cpu: "1"
startupProbe:
httpGet:
path: /health
port: 8080
initialDelaySeconds: 3
periodSeconds: 1
successThreshold: 1
failureThreshold: 5
livenessProbe:
httpGet:
path: /health
port: 8080
periodSeconds: 3
successThreshold: 1
failureThreshold: 3
readinessProbe:
httpGet:
path: /health
port: 8080
periodSeconds: 1
successThreshold: 1
failureThreshold: 3
securityContext:
allowPrivilegeEscalation: false
env:
- name: API_URL
valueFrom:
configMapKeyRef:
name: {{ .Values.front.name }}-front
key: API_URL
{{- end }}
\ No newline at end of file
{{- if .Values.front.enabled }}
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: {{ .Values.front.name }}-front
spec:
ingressClassName: nginx
rules:
- host: {{ .Values.front.ingress.host }}
http:
paths:
- backend:
service:
name: {{ .Values.front.name }}-front
port:
number: 80
path: /
pathType: Prefix
{{- if .Values.front.ingress.tlsEnabled }}
tls:
- hosts:
- {{ .Values.front.ingress.host }}
secretName: app-wildcard
{{- end }}
{{- end }}
{{- if .Values.front.enabled }}
apiVersion: v1
kind: Service
metadata:
name: {{ .Values.front.name }}-front
spec:
selector:
app: front
ports:
- protocol: TCP
port: 80
targetPort: 8080
{{- end }}
\ No newline at end of file
# Default values for CDB app.
# This is a YAML-formatted file.
# Declare variables to be passed into your templates.
# We have only done front for now
name: cdb
api:
name: api
replicaCount: 1
image:
repository: registry.gitlab.com/takima-school/images/cdb/api
tag: latest
ingress:
tlsEnabled: true
host: api.tdandoy.takima.school
front:
enabled: true
image:
repository: registry.gitlab.com/takima-school/images/cdb/www
tag: latest
replicaCount: 1
ingress:
tlsEnabled: true
host: kube.tdandoy.takima.school
name: helm
pg:
name: pg
image:
repository: registry.takima.io/school/proxy/postgres
tag: latest
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment