style(convention): Remove file naming convention
The previously used file naming convention is no longer necessary as Kustomize already orders any request done to the fluster, without having to rely on the `--recursive` fly of the `apply` command.
This commit is contained in:
parent
982120fe36
commit
64edf557d6
20
README.md
20
README.md
@ -92,26 +92,8 @@ Cf : https://docs.k3s.io/advanced#auto-deploying-manifests
|
|||||||
|
|
||||||
### Development domains
|
### Development domains
|
||||||
To access a service publicly when developing, the domain name should be *.beta.halia.dev
|
To access a service publicly when developing, the domain name should be *.beta.halia.dev
|
||||||
To only expose a service internally, the domain name should be *.k3s.beta
|
To only expose a service internally, the domain name should be *.beta.entos
|
||||||
|
|
||||||
### Ingresses
|
### Ingresses
|
||||||
To split between external and internal services, two traefik ingresses are implemented through the `ingressclass` annotation.
|
To split between external and internal services, two traefik ingresses are implemented through the `ingressclass` annotation.
|
||||||
`traefik-external` will only allow external access to a given service, while `traefik-internal` restrict to an internal only access.
|
`traefik-external` will only allow external access to a given service, while `traefik-internal` restrict to an internal only access.
|
||||||
|
|
||||||
### Naming convention
|
|
||||||
As the project grows in size, all files must be renamed the following norm for easier readability and maintability :
|
|
||||||
```
|
|
||||||
{priority}-{optional-detail}-{service-name}.yaml
|
|
||||||
```
|
|
||||||
The priority here gives an execution order when applying files in bulk.
|
|
||||||
This means that, for example, to avoid the `namespace doesn't exist` error, the following order can be followed :
|
|
||||||
|
|
||||||
```
|
|
||||||
- 0-namespace.yaml
|
|
||||||
- 1-pvc.yaml
|
|
||||||
- 2-deployment.yaml
|
|
||||||
- 2-service.yaml
|
|
||||||
- 2-ingress.yaml
|
|
||||||
```
|
|
||||||
|
|
||||||
This also applies to directories, this behaviour can be seen in the `traefik` directory, where RBAC are prioritized before other files, as they are the first dependency.
|
|
||||||
|
@ -107,8 +107,8 @@ spec:
|
|||||||
- "--accesslog=true"
|
- "--accesslog=true"
|
||||||
- "--entrypoints.websecure.http.tls=true"
|
- "--entrypoints.websecure.http.tls=true"
|
||||||
- "--entrypoints.websecure.http.tls.certresolver=letsencrypt"
|
- "--entrypoints.websecure.http.tls.certresolver=letsencrypt"
|
||||||
- "--entrypoints.websecure.http.tls.domains[0].main=k3s.beta"
|
- "--entrypoints.websecure.http.tls.domains[0].main=beta.entos"
|
||||||
- "--entrypoints.websecure.http.tls.domains[0].sans=*.k3s.beta"
|
- "--entrypoints.websecure.http.tls.domains[0].sans=*.beta.entos"
|
||||||
- "--certificatesresolvers.letsencrypt.acme.tlschallenge=true"
|
- "--certificatesresolvers.letsencrypt.acme.tlschallenge=true"
|
||||||
- "--certificatesresolvers.letsencrypt.acme.dnschallenge=true"
|
- "--certificatesresolvers.letsencrypt.acme.dnschallenge=true"
|
||||||
- "--certificatesresolvers.letsencrypt.acme.dnschallenge.provider=ovh"
|
- "--certificatesresolvers.letsencrypt.acme.dnschallenge.provider=ovh"
|
@ -15,7 +15,7 @@ items:
|
|||||||
annotations:
|
annotations:
|
||||||
spec:
|
spec:
|
||||||
type: LoadBalancer
|
type: LoadBalancer
|
||||||
loadBalancerIP: 10.10.0.64
|
loadBalancerIP: 10.10.0.28
|
||||||
selector:
|
selector:
|
||||||
app.kubernetes.io/name: traefik-inter
|
app.kubernetes.io/name: traefik-inter
|
||||||
app.kubernetes.io/instance: traefik-inter
|
app.kubernetes.io/instance: traefik-inter
|
Loading…
Reference in New Issue
Block a user