...

Text file src/edge-infra.dev/config/pallets/sds/firewallctl/README.md

Documentation: edge-infra.dev/config/pallets/sds/firewallctl

     1# Environment Variables
     2
     3## Environment Setup
     4
     5Create an `.env` file with the following variables:
     6
     7```dotenv
     8# gke, sds, or generic. use "generic" for any K8s cluster that isn't GKE or 
     9# SDS.
    10export CLUSTER_PROVIDER=
    11# uuid is necessary for generating a cluster_hash, existing resources should
    12# have this in their annotations already but one can be created by using
    13# uuidgen
    14export CLUSTER_UUID=
    15# google cloud project id
    16export GCP_PROJECT_ID=
    17# defaults to us and east1-b, otherwise needs to be valid GCP value
    18export GCP_REGION=
    19export GCP_ZONE=
    20# set to same value as gcp project ID when developing within a single
    21# project.
    22export FOREMAN_GCP_PROJECT_ID=
    23# enables split scheduling
    24export INFRA=true
    25# name of the kubeconfig context to use to schedule infra objects; 
    26# default behavior is to apply all objects to the same K8s context
    27export INFRA_CONTEXT=
    28# target namespace for all applied infrastructure resources, including 
    29# dependencies; the namespace is created if it does not already exist.
    30export INFRA_NAMESPACE=
    31```
    32
    33# Applying the Pallet
    34
    35The following is an example on applying the firewallctl deployment
    36
    37```shell
    38source .env
    39lift pack config/pallets/sds/firewallctl
    40lift apply config/pallets/sds/firewallctl
    41```

View as plain text