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

Issue with k8s.io/docs/concepts/workloads/pods/podpreset/ #23285

Closed
arul24ar opened this issue Aug 21, 2020 · 4 comments · Fixed by #26027
Closed

Issue with k8s.io/docs/concepts/workloads/pods/podpreset/ #23285

arul24ar opened this issue Aug 21, 2020 · 4 comments · Fixed by #26027
Labels
kind/support Categorizes issue or PR as a support question. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@arul24ar
Copy link

This is a Bug Report

**Problem: Even after enabling the minikube with podpreset API I am getting the below error when I try to apply the podpreset.

Steps Followed:

  1. minikube start --extra-config=apiserver.runtime-config=settings.k8s.io/v1alpha1=true
  2. kubectl apply -f podpreset.yml
    Here is my propreset values:
    apiVersion: settings.k8s.io/v1alpha1
    kind: PodPreset
    metadata:
    name: share-cred
    spec:
    selector:
    matchLabels:
    app: myapp
    env:
    • name: MY_SECRET
      value: '123456'
      volumeMount:
    • mountPath: /share
      name: share-volume
      volumes:
    • name: share-volume
      emptyDir: {}

ERROR: no matches for kind "PodPreset" in version "settings.k8s.io/v1alpha1"

Proposed Solution:

Page to Update:
https://kubernetes.io/docs/tasks/inject-data-application/podpreset/

@sftim
Copy link
Contributor

sftim commented Aug 22, 2020

Thanks for submitting this issue @arul24ar

It looks like you didn't enable the PodPreset admission controller. See https://kubernetes.io/docs/concepts/workloads/pods/podpreset/#enable-pod-preset

If you enable that, does it work OK?

/triage support

@k8s-ci-robot k8s-ci-robot added the kind/support Categorizes issue or PR as a support question. label Aug 22, 2020
@arul24ar
Copy link
Author

Thank you for your response @tim Bannister
Yes even after enabling I am getting the same error. 
Please find the below steps I followed :

1)minikube start --extra-config=apiserver.runtime-config=settings.k8s.io/v1alpha1=true
2) kubectl apply -f podpreset.yml

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/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 Nov 22, 2020
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/support Categorizes issue or PR as a support question. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants