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

kubernetes: fix configmap volumes #2462

Conversation

dweomer
Copy link

@dweomer dweomer commented May 17, 2024

Use the ConfigMap name as the volume/volumeMount name so that files discovered while parsing buildkitd.toml, such as references to tls ca/cert/key, will be mounted in the builder Deployment.

Use the ConfigMap name as the volume/volumeMount name so that files
discovered while parsing buildkitd.toml, such as references to tls
ca/cert/key, will be mounted in the builder Deployment.

Signed-off-by: Jacob Blain Christen <dweomer5@gmail.com>
@dweomer
Copy link
Author

dweomer commented May 17, 2024

I've tested this (with registry mirrors in my buildkitd.toml) on my 0.13.x branch, tagged v0.13.1+dweomer.1, image dweomer/buildx-bin:v0.13.1-dweomer.1

Copy link
Member

@crazy-max crazy-max left a comment

Choose a reason for hiding this comment

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

Seems to be a duplicate of #2454 which introduces similar changes?

driver/kubernetes/manifest/manifest.go Show resolved Hide resolved
driver/kubernetes/manifest/manifest.go Show resolved Hide resolved
@crazy-max
Copy link
Member

Fixed in #2454

@crazy-max crazy-max closed this May 27, 2024
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