[Question] How to replace text in a ConfigMap using replacements instead of vars?

[NickLarsenNZ]

I recall being able to replace var references in ConfigMaps through configs like so:

kustomization.yml

secretGenerator:
- name: argocd-oidc # will get a hashed suffix so that pods reload when changed
  literals:
  - auth0.clientSecret=secret

configMapGenerator:
- name: argocd-cm
  files:
  - oidc.config=oidc.config.yml

configurations:
- konfig.yml

vars:
- name: KUSTOMIZE_OIDC_SECRET_NAME
  objref:
    kind: Secret
    name: argocd-oidc
    apiVersion: v1

konfig.yml

# Specify which resources and keys might contain a variable to interpolate
varReference:
- kind: ConfigMap
  path: data

oidc.config.yml (as far as Kustomize is concerned, it is plain text)

name: Auth0
issuer: https://me.auth0.com/
clientID: ...
clientSecret: $$(KUSTOMIZE_OIDC_SECRET_NAME):auth0.clientSecret # Note the first dollar sign is part of the ArgoCD config to signify a Secret name. Not part of kustomize replacement
requestedScopes:
- openid
- profile
- email

This doesn't seem to work anymore, and seeing that vars is being deprecated, I'm wondering how I can replace text inside a ConfigMap?

For now I guess I'll see if I can find a way to specify the clientSecret through an env var, but I'm really at the mercy of the app here.

[k8s-ci-robot]

@NickLarsenNZ: This issue is currently awaiting triage.

SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[NickLarsenNZ]

For now, I have to use the disableNameSuffixHash: true generator option so that I have a static Secret name to use in the config - but then I have to manage reloading pods when that data changes.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.