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

kustomize build error: evalsymlink failure #3358

Open
ringods opened this issue Dec 8, 2024 · 2 comments
Open

kustomize build error: evalsymlink failure #3358

ringods opened this issue Dec 8, 2024 · 2 comments
Labels
area/docs Improvements or additions to documentation kind/documentation Improvements or additions to documentation

Comments

@ringods
Copy link
Member

ringods commented Dec 8, 2024

What happened?

When deploying the example below, I get the following error:

pulumi up
Previewing update (desk8s)

View in Browser (Ctrl+O): https://app.pulumi.com/ringods/snapshot-controller/desk8s/previews/786d8d64-bf97-45f9-8a76-70d18a33ac61

     Type                                  Name                        Plan       Info
 +   pulumi:pulumi:Stack                   snapshot-controller-desk8s  create     1 error
 +   └─ kubernetes:kustomize/v2:Directory  snapshot-controller-crds    create     

Diagnostics:
  pulumi:pulumi:Stack (snapshot-controller-desk8s):
    error: kubernetes:kustomize/v2:Directory resource 'snapshot-controller-crds' has a problem: kustomize build error: evalsymlink failure on '/private/var/folders/mp/9wctftz9039d4jdch0y48r780000gn/T/kustomize-3015178404/tree/v8.1.0/client/config/crd' : lstat /private/var/folders/mp/9wctftz9039d4jdch0y48r780000gn/T/kustomize-3015178404/tree: no such file or directory

When checking after this error, everything up to /private/var/folders/mp/9wctftz9039d4jdch0y48r780000gn/T exists, but the subfolder kustomize-3015178404 and lower doesn't exist.

Example

Following the example Kustomize Directory from a Git Repo, I replaced the example location with the one I wanted:

const crds = new k8s.kustomize.v2.Directory("snapshot-controller-crds", {
    directory: "https://github.com/kubernetes-csi/external-snapshotter/tree/v8.1.0/client/config/crd",
});

Output of pulumi about

pulumi about
CLI          
Version      3.142.0
Go Version   go1.23.3
Go Compiler  gc

Plugins
KIND      NAME        VERSION
resource  kubernetes  4.18.4
language  nodejs      unknown

Host     
OS       darwin
Version  15.1.1
Arch     x86_64

This project is written in nodejs: executable='/Users/ringods/.volta/bin/node' version='v18.15.0'

Current Stack: ringods/snapshot-controller/desk8s

Found no resources associated with desk8s

Found no pending operations associated with desk8s

Backend        
Name           pulumi.com
URL            https://app.pulumi.com/ringods
User           ringods
Organizations  ringods, pulumiverse
Token type     personal

Dependencies:
NAME                VERSION
@pulumi/kubernetes  4.18.4
@pulumi/pulumi      3.142.0
@types/node         18.19.67
typescript          5.7.2

Pulumi locates its logs in /var/folders/mp/9wctftz9039d4jdch0y48r780000gn/T/ by default

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

@ringods ringods added kind/bug Some behavior is incorrect or out of spec needs-triage Needs attention from the triage team labels Dec 8, 2024
@rquitales
Copy link
Member

We use the upstream Kustomize library to help with downloading remote artifacts. From Kustomize's documentation, the GitHub URL should follow the following documented structure. As such, your Pulumi program should be updated to be:

const crds = new k8s.kustomize.v2.Directory("snapshot-controller-crds", {
  directory: "https://github.com/kubernetes-csi/external-snapshotter//client/config/crd?ref=v8.1.0",
});

I noticed that the URL used in our documentation is not a working/correct example, so I'll leave this issue open for us to update our docs.

@rquitales rquitales added area/docs Improvements or additions to documentation kind/documentation Improvements or additions to documentation and removed kind/bug Some behavior is incorrect or out of spec needs-triage Needs attention from the triage team labels Dec 9, 2024
@ringods
Copy link
Member Author

ringods commented Dec 15, 2024

Verified that with the correct URL structure, the deployment works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/docs Improvements or additions to documentation kind/documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants