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

PriorityClassList fails to create due to: failed to determine if namespaced #1045

Closed
CoreyLoose opened this issue Mar 25, 2020 · 3 comments
Closed
Assignees
Labels
kind/bug Some behavior is incorrect or out of spec resolution/fixed This issue was fixed

Comments

@CoreyLoose
Copy link

Problem description

When creating a PriorityClassList the following error happens:

resource scheduler-priorities-rqaatzhi was not successfully created by the Kubernetes API server : failed to determine if the following GVK is namespaced: scheduling.k8s.io/v1, Kind=PriorityClassList

Errors & Logs

This is simplest version of the code I've got that causes the error. Running just the PriorityClass piece by itself works, so the problem is definitely with the PriorityClassList

new k8s.scheduling.v1.PriorityClassList("scheduler-priorities", {
    items: [
        new k8s.scheduling.v1.PriorityClass("selector-spread-priority", {value: 10})
    ]
});

Affected product version(s)

I'm using pulumi 1.6

@CoreyLoose
Copy link
Author

CoreyLoose commented Mar 25, 2020

Talked with @lblackstone a little bit about this in slack

@deepio
Copy link

deepio commented May 31, 2022

Same for CronJobList

pulumi: v3.33.2

@deepio
Copy link

deepio commented Jun 1, 2022

I got something that works for me. Instead of using any *List (e.g., CronJobList, NamespaceList, PriorityClassList) try just putting them in an array.

const cronJob = [
  new k8s.batch.v1beta1.CronJob(...),
  new k8s.batch.v1beta1.CronJob(...),
];

@lblackstone lblackstone added the kind/bug Some behavior is incorrect or out of spec label Jul 13, 2023
@lblackstone lblackstone removed their assignment Jul 13, 2023
@lblackstone lblackstone self-assigned this Jul 13, 2023
@lblackstone lblackstone added the resolution/fixed This issue was fixed label Jul 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Some behavior is incorrect or out of spec resolution/fixed This issue was fixed
Projects
None yet
Development

No branches or pull requests

3 participants