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

[Bug]: flux-system/aws-observability-accelerator failed to create kubernetes rest client for update of resource: resource [source.toolkit.fluxcd.io/v1beta2/GitRepository] isn't valid for cluster, check the APIVersion and Kind fields are valid #229

Open
1 task done
jalawala opened this issue Sep 6, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@jalawala
Copy link

jalawala commented Sep 6, 2023

Welcome to the AWS Observability Accelerator

  • Yes, I've searched similar issues on GitHub and didn't find any.

AWS Observability Accelerator Release version

v2.9.0

What is your environment, configuration and the example used?

running the examples/existing-cluster-with-base-and-infra for EKS 1.27 cluster

What did you do and What did you see instead?

Below error occurs during terraform apply on EKS 1.27 cluster

│ Error: flux-system/aws-observability-accelerator failed to create kubernetes rest client for update of resource: resource [source.toolkit.fluxcd.io/v1beta2/GitRepository] isn't valid for cluster, check the APIVersion and Kind fields are valid

│ with module.eks_monitoring.kubectl_manifest.flux_gitrepository[0],
│ on ../../modules/eks-monitoring/dashboards.tf line 1, in resource "kubectl_manifest" "flux_gitrepository":
│ 1: resource "kubectl_manifest" "flux_gitrepository" {



│ Error: flux-system/grafana-dashboards-infrastructure failed to create kubernetes rest client for update of resource: resource [kustomize.toolkit.fluxcd.io/v1beta2/Kustomization] isn't valid for cluster, check the APIVersion and Kind fields are valid

│ with module.eks_monitoring.kubectl_manifest.flux_kustomization[0],
│ on ../../modules/eks-monitoring/dashboards.tf line 20, in resource "kubectl_manifest" "flux_kustomization":
│ 20: resource "kubectl_manifest" "flux_kustomization" {



│ Error: flux-system/grafana-dashboards-apiserver failed to create kubernetes rest client for update of resource: resource [kustomize.toolkit.fluxcd.io/v1beta2/Kustomization] isn't valid for cluster, check the APIVersion and Kind fields are valid

│ with module.eks_monitoring.kubectl_manifest.api_server_dashboards[0],
│ on ../../modules/eks-monitoring/dashboards.tf line 51, in resource "kubectl_manifest" "api_server_dashboards":
│ 51: resource "kubectl_manifest" "api_server_dashboards" {



│ Error: flux-system/grafana-dashboards-adothealth failed to create kubernetes rest client for update of resource: resource [kustomize.toolkit.fluxcd.io/v1beta2/Kustomization] isn't valid for cluster, check the APIVersion and Kind fields are valid

│ with module.eks_monitoring.kubectl_manifest.adothealth_monitoring_dashboards[0],
│ on ../../modules/eks-monitoring/dashboards.tf line 76, in resource "kubectl_manifest" "adothealth_monitoring_dashboards":
│ 76: resource "kubectl_manifest" "adothealth_monitoring_dashboards" {



│ Error: flux-system/grafana-dashboards-kubeproxy failed to create kubernetes rest client for update of resource: resource [kustomize.toolkit.fluxcd.io/v1beta2/Kustomization] isn't valid for cluster, check the APIVersion and Kind fields are valid

│ with module.eks_monitoring.kubectl_manifest.kubeproxy_monitoring_dashboard[0],
│ on ../../modules/eks-monitoring/dashboards.tf line 98, in resource "kubectl_manifest" "kubeproxy_monitoring_dashboard":
│ 98: resource "kubectl_manifest" "kubeproxy_monitoring_dashboard" {

Additional Information

No response

@jalawala jalawala added the bug Something isn't working label Sep 6, 2023
@ss1796
Copy link

ss1796 commented Feb 28, 2024

I'm getting the same error on V12.2.1 on EKS 1.28

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants