Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
O
openappstack
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 124
    • Issues 124
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • openappstack
  • openappstack
  • Issues
  • #617

Closed
Open
Opened Jun 19, 2020 by Varac@varacOwner

Force a helm upgrade for app config changes

Given:

  • a deployed OAS cluster

  • a change to i.e. the prometheus-config

  • an upgrade of your cluster using python3 -m openappstack oas.varac.net install --ansible-param='--tags=prometheus' The secret prometheus-settings in namespace oas contains the new config:

    kubectl view-secret -n oas prometheus-settings values.yaml

But the configmap prometheus-server didn't update, see the latest timestamp:

kubectl -n oas get cm prometheus-server -o jsonpath='{range .metadata.managedFields[*]}{.operation}{"\t"}{.time}{"\n"}{end}'                     

In order to update this configmap we need to force a helm upgrade for prometheus. Because there are no git changes which the helm-operator can act upon, there's no other way than to restart helm-operator pod:

kubectl -n oas delete pods -l 'app in (helm-operator)                                                                                            

In the helm-operator FAQ there's a section about Notifying the Helm Operator about Git changes, but in this case there's no git change.

I wonder how we can deal with this the best way. Should we trigger a helm-operator pod deletion every time we update the app secrect ?

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
0.4.1
Milestone
0.4.1
Assign milestone
Time tracking
None
Due date
None
Reference: openappstack/openappstack#617