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

helm install fails when deploying VAPs in Kubernetes v1.28.0 #78

Open
aramase opened this issue Sep 5, 2024 · 7 comments · May be fixed by #89
Open

helm install fails when deploying VAPs in Kubernetes v1.28.0 #78

aramase opened this issue Sep 5, 2024 · 7 comments · May be fixed by #89
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug.
Milestone

Comments

@aramase
Copy link
Member

aramase commented Sep 5, 2024

➜ kgno -owide
NAME                 STATUS   ROLES           AGE   VERSION   INTERNAL-IP   EXTERNAL-IP   OS-IMAGE                         KERNEL-VERSION    CONTAINER-RUNTIME
kind-control-plane   Ready    control-plane   36s   v1.28.0   172.18.0.2    <none>        Debian GNU/Linux 11 (bullseye)   6.6.32-linuxkit   containerd://1.7.1

secrets-store-sync-controller/manifest_staging/charts/secrets-store-sync-controller on  pr-72 [$] at ☸️ kind-kind
➜ helm install sssc .
Error: INSTALLATION FAILED: unable to build kubernetes objects from release manifest: [resource mapping not found for name: "secrets-store-sync-controller-create-update-policy" namespace: "" from "": no matches for kind "ValidatingAdmissionPolicy" in version "admissionregistration.k8s.io/v1beta1"
ensure CRDs are installed first, resource mapping not found for name: "secrets-store-sync-controller-create-update-token-deny-policy" namespace: "" from "": no matches for kind "ValidatingAdmissionPolicy" in version "admissionregistration.k8s.io/v1beta1"
ensure CRDs are installed first, resource mapping not found for name: "secrets-store-sync-controller-delete-policy" namespace: "" from "": no matches for kind "ValidatingAdmissionPolicy" in version "admissionregistration.k8s.io/v1beta1"
ensure CRDs are installed first, resource mapping not found for name: "secrets-store-sync-controller-update-check-oldobject-policy" namespace: "" from "": no matches for kind "ValidatingAdmissionPolicy" in version "admissionregistration.k8s.io/v1beta1"
ensure CRDs are installed first, resource mapping not found for name: "secrets-store-sync-controller-update-label-policy" namespace: "" from "": no matches for kind "ValidatingAdmissionPolicy" in version "admissionregistration.k8s.io/v1beta1"
ensure CRDs are installed first, resource mapping not found for name: "secrets-store-sync-controller-validate-annotation-policy" namespace: "" from "": no matches for kind "ValidatingAdmissionPolicy" in version "admissionregistration.k8s.io/v1beta1"
ensure CRDs are installed first, resource mapping not found for name: "secrets-store-sync-controller-validate-label-policy" namespace: "" from "": no matches for kind "ValidatingAdmissionPolicy" in version "admissionregistration.k8s.io/v1beta1"
ensure CRDs are installed first, resource mapping not found for name: "secrets-store-sync-controller-validate-token-policy" namespace: "" from "": no matches for kind "ValidatingAdmissionPolicy" in version "admissionregistration.k8s.io/v1beta1"
ensure CRDs are installed first, resource mapping not found for name: "secrets-store-sync-controller-create-update-policy-binding" namespace: "" from "": no matches for kind "ValidatingAdmissionPolicyBinding" in version "admissionregistration.k8s.io/v1beta1"
ensure CRDs are installed first, resource mapping not found for name: "secrets-store-sync-controller-create-update-token-deny-policy-binding" namespace: "" from "": no matches for kind "ValidatingAdmissionPolicyBinding" in version "admissionregistration.k8s.io/v1beta1"
ensure CRDs are installed first, resource mapping not found for name: "secrets-store-sync-controller-delete-policy-binding" namespace: "" from "": no matches for kind "ValidatingAdmissionPolicyBinding" in version "admissionregistration.k8s.io/v1beta1"
ensure CRDs are installed first, resource mapping not found for name: "secrets-store-sync-controller-update-owners-check-oldobject-policy-binding" namespace: "" from "": no matches for kind "ValidatingAdmissionPolicyBinding" in version "admissionregistration.k8s.io/v1beta1"
ensure CRDs are installed first, resource mapping not found for name: "secrets-store-sync-controller-update-label-policy-binding" namespace: "" from "": no matches for kind "ValidatingAdmissionPolicyBinding" in version "admissionregistration.k8s.io/v1beta1"
ensure CRDs are installed first, resource mapping not found for name: "secrets-store-sync-controller-validate-annotation-policy-binding" namespace: "" from "": no matches for kind "ValidatingAdmissionPolicyBinding" in version "admissionregistration.k8s.io/v1beta1"
ensure CRDs are installed first, resource mapping not found for name: "secrets-store-sync-controller-validate-label-policy-binding" namespace: "" from "": no matches for kind "ValidatingAdmissionPolicyBinding" in version "admissionregistration.k8s.io/v1beta1"
ensure CRDs are installed first, resource mapping not found for name: "secrets-store-sync-controller-validate-token-policy-binding" namespace: "" from "": no matches for kind "ValidatingAdmissionPolicyBinding" in version "admissionregistration.k8s.io/v1beta1"
ensure CRDs are installed first]

The CI isn't catching this failure because the test matrix is always deploying a cluster with v1.30.2

KIND_NODE_IMAGE_VERSION ?= v1.30.2

Opened kubernetes/test-infra#33432 to set the correct version in the test matrix. I suspect the tests will start failing after that's merged, so this needs to be fixed.

/kind bug
/assign @nilekhc

@k8s-ci-robot k8s-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Sep 5, 2024
@aramase aramase added this to the v0.0.2 milestone Sep 5, 2024
@AlexanderStocks
Copy link
Contributor

AlexanderStocks commented Sep 20, 2024

Did you enable the required feature gates when testing this with v1.28.0? I believe the kind-config.yaml featureGates and runtimeConfig values would need to be changed to work for 1.28.0

@nilekhc
Copy link
Contributor

nilekhc commented Oct 7, 2024

/unassign

@omerap12
Copy link
Member

omerap12 commented Oct 8, 2024

/assign

@omerap12
Copy link
Member

omerap12 commented Oct 8, 2024

Did you enable the required feature gates when testing this with v1.28.0? I believe the kind-config.yaml featureGates and runtimeConfig values would need to be changed to work for 1.28.0

I will look into it thanks!

@AlexanderStocks AlexanderStocks linked a pull request Oct 23, 2024 that will close this issue
3 tasks
@AlexanderStocks
Copy link
Contributor

/assign

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 25, 2025
@aramase
Copy link
Member Author

aramase commented Feb 25, 2025

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants