Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add CONFIG_NAMESPACE and CONFIG_LOCKS_CONFIGMAP_NAME #1144

Merged
merged 1 commit into from
Sep 20, 2024

Conversation

mumoshu
Copy link
Contributor

@mumoshu mumoshu commented Sep 17, 2024

Add two environment variables to specify the namespace and the confimap to use lock-related features.

The namespace has been gocat but we no longer have the default. You need to explicitly specify the namespace, using the downward API, for example.

Similarly, the configmap name has been deploylocks, but we have no default value anymore. Specify it, like CONFIG_LOCKS_CONFIGMAP_NAME=deploylocks, for example to retain the default behavior.

Add two environment variables to specify the namespace and the confimap to use lock-related features.

The namespace has been `gocat` but we no longer have the default. You need to explicitly specify the namespace, using the downward API, for example.

Similarly, the configmap name has been `deploylocks`, but we have no default value anymore. Specify it, like CONFIG_LOCKS_CONFIGMAP_NAME=deploylocks, for example to retain the default behavior.
@pirlodog1125 pirlodog1125 merged commit 9fe2a22 into kufu-ai:master Sep 20, 2024
5 checks passed
@mumoshu mumoshu deleted the deploy-respect-loccks branch September 23, 2024 01:27
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.

2 participants