Skip to content

Latest commit

 

History

History
79 lines (59 loc) · 3.81 KB

README.md

File metadata and controls

79 lines (59 loc) · 3.81 KB
Raw

dof_app_deploy

the name

dof: DevOpsFuture - this was a working title that stuck to this repository

why

goal is to enable a push based deployment (contrary to pull in gitops speech) this repository would be the environment repository for that matter

how

if in any "auto-deployment" enabled repositories a push happened the dev deployment workflow to our dev system gets executed

adding new secrets

Note: Consult with DevOps for any uncertainties.

Appending to an Existing Secret

  1. Update in 1Password: Modify the secret within development vaults (sc-dev-*) in 1Password.
  2. Notify DevOps: Inform DevOps for updates across other stages.

Creating a New Secret

  1. Create in 1Password: Add a new item in the development vaults (sc-dev-*).
  2. Prepare Manifest: 
    apiVersion: "onepassword.com/v1"
kind: OnePasswordItem
metadata:
  name: <unique-secret-name>
  namespace: {{ NAMESPACE }}
  labels:
    app: "your-app"
spec:
  itemPath: "vaults/{{ ONEPASSWORD_OPERATOR_VAULT }}/items/<item-name>"
  3. Add to Ansible: Incorporate the manifest into the relevant Ansible task, usually main.yml.
  4. Inform DevOps: Notify DevOps for deployment to other stages.

dev namespace (de)activation

only applies to the dev stage to save resources!

activation: deployments in a certain namespace are scaled up to 1
deactivation: deployments in a certain namespace are scaled down to 0

namespace lifecycle:

  1. during a rollout the namespace activator is triggered to activate the namespace for 2 days
  2. after 2 days the namespace gets automatically deactivated
  3. you might re-activate it again, by visiting https://activate.[dbc,nbc,brb].dbildungscloud.dev/namespace for 2 more days
  • new pushes to a branch won't re-new the 2 days on purpose
  • visiting the activator before the time has run up, you may hit activate to get 2 more days
  • you may also get more than 2 days, but don't make that your default action, think about the trees 🌳

extend activation time by adding a label to your pr:

⚠️ Important: The auto-extend-activation-time label should only be used when absolutely necessary, such as when you need to activate the namespace for e2e tests. Avoid using it as a precautionary measure to prevent unnecessary rollouts and resource consumption.

This method is effective for each unique PR. If you have multiple PRs from the same branch across various repositories, you only need to apply this setting once.

  1. Navigate to the PR you wish to automatically extend its namespace's activation time.
  2. Apply the auto-extend-activation-time label to the PR. This action will also initiate a new rollout.
  3. Following this, the activation time for the namespace will be automatically extended with every new push to the branch associated with this PR.

extend activation time by modifying the database:

  1. Gain access to the MongoDB located within the sc-common namespace.
  2. Navigate to the keda database and access the namespaces collection. Once there, it will be clear which modifications are necessary.

how does a branch name get converted into a namespace

To convert a branch name to a Kubernetes namespace by stripping paths, converting to lowercase, and replacing underscores and dots with hyphens. It ensures the namespace is compliant with Kubernetes naming conventions.

Some examples:

refs/heads/FEATURE_NAME.1 => feature-name-1
depandabot/npm/jose-5.8.3 => jose-5-8-3
refs/tags/v2.0.1-beta => v2-0-1-beta
feature/ABC_XYZ.2021 => abc-xyz-2021
HUHU-666 => huhu-666