Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S stack-genablers
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • vfos
  • stack-genablers
  • Issues
  • #1

Closed
Open
Created Jan 31, 2019 by Ricardo Grim Cabrita@grimMaintainer

K8s secrets for protecting database credentials

Some deployments, such as keyrock and keyrock-mysql include sensitive data in the form of environment variables.

This is not terribly critical as such credentials are the defaults for Keyrock and are already documented in the official docs. Additionally communication with the databases is restricted to the vfos namespace and the databases aren't likely to be used to store private information.

Replace ENVAR containing sensitive credentials with k8s secrets and include a sample file in the repository.

Assignee
Assign to
Time tracking