-
Notifications
You must be signed in to change notification settings - Fork 107
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
Kubectl manifest can't find api resource eventhough it exist #274
Comments
I took a small deep dive in the code of the manifest but I am not very familiar with go so I have a limited understanding of it. I have to mention that the ClusterSecretStore kind is a kind with not namespace attached to it. It is accessible from everywhere. I am not sure how kubernetes handles this but could this be the problem of the error? |
I just faced this issue too. It creates the resource but then says it can't find it. This didn't used to happen. |
Seems to be the same problem as #270 |
Can confirm this is a legit issue. |
Can you try the fork
That issue should be fixed there |
Thanks |
@alekc thanks. I was ready to cry, but your fork spared my dignity :-D |
@alekc Any chance of getting this fork merged, since it obviously works? |
Merged where sorry? This repo is abandoned, I am maintaining a fork (with
big fixes and new features) on
https://github.com/alekc/terraform-provider-kubectl
…On Mon, 2 Sept 2024, 14:02 Henrik Svensson, ***@***.***> wrote:
@alekc <https://github.com/alekc> Any chance of getting this fork merged,
since it obviously works?
—
Reply to this email directly, view it on GitHub
<#274 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACJ5VZ33YAR5KLQZMYUFPTZUROXPAVCNFSM6AAAAABNQJP2KOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRUG4YTCNZQGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Ah, my bad! I'm loving the changes you've made but when I first searched the providers on TF registry I only saw this old one. Today I saw yours in on there as well. I just wanted people to have a chance at finding the working version from the start and not like me where I first had issues with the old until I found this issue. |
I am trying to create components of the external-secrets.io/v1beta1 api. The resource get's created with success but after this, it returns an error which says
Error: gcp-backend failed to fetch resource from kubernetes: the server could not find the requested resource
This error happens with everything from this resource. I am assuming it has something to do with the v1beta1 but I don't know why that would be an issue. This api resource does not yet has a released v1 api. I am running Terraform version 1.5.6
This is my required providers settings
This is my terraform code
The Api resources in my cluster include the following
Again, the resource gets created and everything works fine but my terraform code returns an error and does not save the resource in the state, resulting that it tries to recreate it with every run.
The text was updated successfully, but these errors were encountered: