Symfony skeletor project
Go to file Use this template
pcaseiro 3f098b691a Merge pull request 'feat(jenkins): adding new default jenkins configuration' (#1) from feat/jenkins into dev
Reviewed-on: #1
2023-06-22 11:46:05 +02:00
bin feat(docker): adding first Dockerfile and kustomization 2023-06-14 12:15:12 +02:00
config feat(docker): adding first Dockerfile and kustomization 2023-06-14 12:15:12 +02:00
misc feat(jenkins): adding new default jenkins configuration 2023-06-21 09:43:13 +02:00
public feat(docker): adding first Dockerfile and kustomization 2023-06-14 12:15:12 +02:00
src feat(docker): adding first Dockerfile and kustomization 2023-06-14 12:15:12 +02:00
.dockerignore feat(docker): adding first Dockerfile and kustomization 2023-06-14 12:15:12 +02:00
.env feat(docker): adding first Dockerfile and kustomization 2023-06-14 12:15:12 +02:00
.gitignore feat(docker): adding first Dockerfile and kustomization 2023-06-14 12:15:12 +02:00
Jenkinsfile feat(jenkins): adding new default jenkins configuration 2023-06-21 09:43:13 +02:00
Makefile feat(jenkins): adding new default jenkins configuration 2023-06-21 09:43:13 +02:00
README.md feat(docker): adding first Dockerfile and kustomization 2023-06-14 12:15:12 +02:00
composer.json feat(docker): adding first Dockerfile and kustomization 2023-06-14 12:15:12 +02:00
composer.lock feat(docker): adding first Dockerfile and kustomization 2023-06-14 12:15:12 +02:00
init-app feat(jenkins): adding new default jenkins configuration 2023-06-21 09:43:13 +02:00
main.mk feat(jenkins): adding new default jenkins configuration 2023-06-21 09:43:13 +02:00
skaffold.yaml feat(jenkins): adding new default jenkins configuration 2023-06-21 09:43:13 +02:00
symfony.lock feat(docker): adding first Dockerfile and kustomization 2023-06-14 12:15:12 +02:00

README.md

Symfony Skeletor

Create a dev cluster with "kind"

  1. Start your Kubernetes cluster

    export ENGINE="kind"
    

    Setup your "harbor" user:

    export HARBOR_USER_NAME="<pnom>"
    

    Create the cluster

    ${ENGINE} create cluster --config misc/k8s/${ENGINE}/${ENGINE}-cluster.yaml
    
  2. Check your cluster status

    kubectl get nodes
    

    All the nodes are "Ready"

    NAME                STATUS   ROLES           AGE    VERSION
    dev-control-plane   Ready    control-plane   5d5h   v1.27.2
    dev-worker          Ready    <none>          5d5h   v1.27.2
    dev-worker2         Ready    <none>          5d5h   v1.27.2
    dev-worker3         Ready    <none>          5d5h   v1.27.2
    
  3. Déployer les opérateurs dans votre cluster

    kubectl apply -k misc/k8s/${ENGINE}/cluster --server-side  
    
  4. Récupèrer la plage IP de votre "cluster" Si vous utilisez kind :

    docker network inspect kind | jq '.[0].IPAM.Config[0].Subnet' -r
    

    En toute logique vous devriez obtenir un résultat du type 172.XX.0.0/16. Gardez cette information pour plus tard.

your-project/
├── assets/
├── bin/
│   └── console
├── config/
│   ├── bundles.php
│   ├── packages/
│   ├── routes.yaml
│   └── services.yaml
├── public/
│   └── index.php
├── src/
│   ├── ...
│   └── Kernel.php
├── templates/
├── tests/
├── translations/
├── var/
└── vendor/