Skip to content

App-operator watching label set false#77

Open
ssyno wants to merge 8 commits intomainfrom
app-oparator-watching-label
Open

App-operator watching label set false#77
ssyno wants to merge 8 commits intomainfrom
app-oparator-watching-label

Conversation

@ssyno
Copy link
Collaborator

@ssyno ssyno commented Mar 20, 2024

This PR

Towards: Issue 30290

  • Sets the label app-operator.giantswarm.io/watching to "false" on configmap created by the operator to avoid the unstopable reconciliation of the resource.

Checklist

  • Update changelog in CHANGELOG.md.

@ssyno ssyno requested a review from a team March 20, 2024 14:38
@ssyno ssyno changed the title App oparator watching label App-operator watching label set false Mar 20, 2024
Copy link
Contributor

@anvddriesch anvddriesch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For my interest, teleport operator refreshes the token but we don't want it to be refreshed inside the agents?

Name: configMapName,
Namespace: clusterNamespace,
Labels: map[string]string{
"app-operator.giantswarm.io/watching": "false",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it okay to add the label upon creation already?
I'm asking because initially it is needed for the configmap to be used to configure the app. Or does this just mean it won't be watched after the initial configuration?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants