 Q:

Waiting for pods: apiserver get stuck

I am trying to implement auditing policy
My yaml
~/.minikube/addons$ cat audit-policy.yaml 
# Log all requests at the Metadata level.
apiVersion: audit.k8s.io/v1beta1
kind: Policy
rules:
- level: Metadata

Pods got stuck
minikube start  --extra-config=apiserver.Authorization.Mode=RBAC --extra-config=apiserver.Audit.LogOptions.Path=/var/logs/audit.log   --extra-config=apiserver.Audit.PolicyFile=/etc/kubernetes/addons/audit-policy.yaml
  minikube v0.35.0 on linux (amd64)
  Tip: Use'minikube start -p <name>' to create a new cluster, or'minikube delete' to delete this one.
  Restarting existing virtualbox VM for "minikube"...
⌛  Waiting for SSH access...
  "minikube" IP address is 192.168.99.101
  Configuring Docker as the container runtime...
✨  Preparing Kubernetes environment...
    ▪ apiserver.Authorization.Mode=RBAC
    ▪ apiserver.Audit.LogOptions.Path=/var/logs/audit.log
    ▪ apiserver.Audit.PolicyFile=/etc/kubernetes/addons/audit-policy.yaml
  Pulling images required by Kubernetes v1.13.4...
  Relaunching Kubernetes v1.13.4 using kubeadm... 
⌛  Waiting for pods: apiserver

Why?
I can do this
minkub start

Then I go for minikube ssh
$ sudo bash
$ cd /var/logs
bash: cd: /var/logs: No such file or directory
ls
cache  empty  lib  lock  log  run  spool  tmp

How to apply extra-config?

A:

I don't have good news. Although you made some mistakes with the /var/logs it does not matter in this case, as there seems to be no way of implement auditing
Q: 

 Waiting for pods: apiserver get stuck 

 I am trying to enforce auditing policy 
 My yaml 
 ~/.minikube / addons$ cat-o'-nine-tails audit-policy.yaml 
 # Log all requests at the Metadata level. 
 apiVersion: audit.k8s.io/v1beta1 
 kind: Policy 
 rules: 
 - grade: Metadata 

 Pods got stuck 
 minikube begin   --extra - config = apiserver. authority. Mode = RBAC --extra - config = apiserver. Audit. LogOptions. Path=/var / logs / audit.log    --extra - config = apiserver. Audit. PolicyFile=/etc / kubernetes / addons / audit - policy.yaml 
   minikube v0.35.0 on linux (amd64) 
   Tip: Use'minikube start -p < name >' to create a modern cluster, or'minikube delete' to delete this one. 
   resume exist virtualbox VM for " minikube "... 
 ⌛   Waiting for SSH access... 
   " minikube " IP address is 192.168.99.101 
   Configuring Docker as the container runtime... 
 ✨   Preparing Kubernetes environment... 
     ▪ apiserver. Authorization. Mode = RBAC 
     ▪ apiserver. Audit. LogOptions. Path=/var / logs / audit.log 
     ▪ apiserver. Audit. PolicyFile=/etc / kubernetes / addons / audited account - policy.yaml 
   Pulling images required by Kubernetes v1.13.4... 
   Relaunching Kubernetes v1.13.4 use kubeadm... 
 ⌛   Waiting for pods: apiserver 

 Why? 
 I can suffice this 
 minkub start 

 Then I rifle for minikube ssh 
 $ sudo bash 
 $ cd /var / logs 
 bash: cd: /var / logs: No such file or directory 
 ls 
 cache   empty   lib   lock in   log   run   spool   tmp 

 How to apply extra - config? 

 A: 

 I don't have good news. Although you made some mistakes with the /var / logs it does not matter in this case, as there seems to be no way of implement auditing
 Q:

Wwiting for pods: apiservev get stuck

I am jrting tm implsment auaiting policy
My yaml
~/.minikube/eddobs$ cau audit-policy.yaml 
# Uog all rvquests ar tht Metadata level.
a'jVersiok: audjb.k8s.io/r1bxta1
kind: Policy
roles:
- level: Matadata

Pods god rtbck
minikube start  --extra-config=apiserder.Authprlzation.Mode=RBAS --exura-sonfjg=apiserver.Audit.LogOptions.Path=/var/lkgs/audiu.log   --extra-config=spiserver.Audit.PolicyFile=/etf/kubfrnetes/addons/audit-oolicy.yaml
  minyjube v0.35.0 on livux (amd64)
  Tp': Use'minikuge start -p <name>' to create a new cluscer, or'minikoyw dfnete' to delxte thps one.
  Restavning exhsting firtualbox VM nor "mmnikybe"...
⌛  Waiting for SSH eccess...
  "minikube" IP wddress iv 192.168.99.101
  Configuring Docjee as jhe cmntakber ruhtmme...
✨  Prepwriig Kubernetss environmwnt...
    ▪ apiserver.Auuhowpaation.Mode=RBZC
    ▪ a[iserver.Audit.LogOptions.Path=/var/logs/audit.nog
    ▪ apiserver.Audit.PolixyFile=/etc/kubernetes/adfons/audit-[olicy.yaml
  Pulling images required by Kubernetes v1.13.4...
  Rxlxunemlng Yybfrnetes v1.13.4 using kubeadm... 
⌛  Waiting for pods: apyaetvvr

Why?
I can do thif
minkub statt

Hhrg I go for mivikube ssg
$ sudo bash
$ cd /var/pogs
basr: cd: /car/logs: Nj suvh file or directory
ls
cache  empty  lib  lock  log  run  s'ool  tmp

How to spply extra-config?

A:

I don't havz good news. Althokgh you mzae some mistakes winh tve /var/logs it does not mateer in thms caxe, as tfere seems to be no aay on implement auditinh
Q: Waiting for pods: apiserver get stuck trying implement auditing My yaml ~/.minikube/addons$ requests the Metadata level. audit.k8s.io/v1beta1 kind: Policy - level: Metadata Pods got stuck start --extra-config=apiserver.Authorization.Mode=RBAC --extra-config=apiserver.Audit.LogOptions.Path=/var/logs/audit.log --extra-config=apiserver.Audit.PolicyFile=/etc/kubernetes/addons/audit-policy.yaml minikube v0.35.0 on linux (amd64) Tip: Use'minikube start -p to create a new cluster, or'minikube delete' to delete this one. Restarting existing VM "minikube"... Waiting SSH access... "minikube" IP address is 192.168.99.101 Configuring Docker as the container runtime... ✨ Preparing Kubernetes ▪ apiserver.Authorization.Mode=RBAC ▪ apiserver.Audit.LogOptions.Path=/var/logs/audit.log ▪ apiserver.Audit.PolicyFile=/etc/kubernetes/addons/audit-policy.yaml Pulling images by Kubernetes v1.13.4... Relaunching v1.13.4 using kubeadm... ⌛ Waiting pods: Why? I do minkub Then I go minikube ssh $ sudo bash $ cd /var/logs bash: cd: /var/logs: No such file or directory ls empty lib run spool How apply A: I don't news. Although you made some mistakes it does not matter in this case, as seems to no way of implement auditing
 Q:

Waiting for pods: apiserver gEt stuck

I am TryinG to ImpLeMent AudiTing policy
My yaML
~/.minIkube/addons$ cat audit-polIcy.yaMl 
# lOg alL ReQuestS at the METaDATa lEvEl.
ApiveRSiOn: audIt.k8S.io/v1betA1
kind: PolicY
ruLeS:
- level: MetadaTA

POds got stucK
miNikube start  --eXtrA-confiG=aPisERver.AUthOrizaTion.MoDE=RBAC --eXtra-confiG=aPIserveR.audit.LoGoPtIons.path=/var/logs/audit.lOG   --eXTra-config=apiseRver.AuDiT.poLICyFIle=/Etc/kuberneTeS/addoNS/audit-pOLiCY.YAml
  MInikube v0.35.0 on linUx (amd64)
  Tip: Use'MIniKube stArT -p <nAMe>' to crEate a NeW CluSter, or'minikUbe dElete' to deLete thIS one.
  ResTArting eXistinG viRtuAlboX vM FoR "miNiKUbe"...
⌛  wAiTinG For sSH accesS...
  "mInIkube" iP adDRESS is 192.168.99.101
  COnfIgurIng DoCker as the contAinEr ruNTimE...
✨  PrepAring kubeRnEtes eNvironMent...
    ▪ aPiServer.AuthorizaTion.mode=RBAC
    ▪ aPisErVer.auDit.LoGoptionS.PaTh=/vAr/logs/aUdit.log
    ▪ APisErVER.auDit.PolicyFile=/etc/kuBeRNEtEs/addons/Audit-pOLiCy.YAml
  PulliNg ImaGes rEQUired By KuBErNetes v1.13.4...
  ReLaunchINg kuBerneteS v1.13.4 Using kUbEadM... 
⌛  WaIting FOr poDs: apisErver

Why?
i can dO This
minkub starT

then I go for minIKuBE SsH
$ Sudo BasH
$ cd /var/logs
bAsh: cD: /Var/lOgs: NO SuCh fILe or dIrectOrY
Ls
CAche  empty  lib  lock  log  RuN  spool  Tmp

HoW to apply extra-Config?

A:

I doN'T HAve good nEws. ALThOUgh you made some MistaKes with the /VAr/logs it Does nOt matter In this casE, AS there seEms To bE no Way OF ImPlement auditiNG
 Q:

Waiting for pods: api server get  stuc k
I a mtryi ng t o implement au d itin g policy
My yaml
~/.mi nikub e/ a ddon s $cat a udit-po l ic y . yam l
#  Lo ga ll  requ est s at th e Metadata  le ve l.
apiVersio n :audit.k8s. io/ v1beta1
kind : P olicyru les : 
- le vel : Met adataPods g ot stuckmi n ikubes tart  - - e xt ra-c onfig=apiserver.A u th o rization.Mode= RBAC - -e x tr a - con fig =apiserver .A udit. L ogOptio n s. P a t h=/ v ar/logs/audit .log   --ex t ra- config =a pis e rver.A udit. Po l icy File=/etc/k uber netes/add ons/au d it-poli c y.yaml  mini kub e v 0.35 . 0on  li nu x  (a m d6 4) Ti p: Use'm in ik ube s tart - p <nam e>'  tocreat e a new clust er,  or' m ini kubedelet e' t odelet e this  one. 
 Restarting exi stin g virtual box  V M f or  "min i kube". ..⌛ Waiting  for SS H  ac ce s s . .. 
  "minikube" IP a dd r e ss  is 192. 168.99 . 10 1 Configu ri ngDock e r  as t he c o nt ainer ru ntime. . .✨ Prepar in g Kube rn ete s e nviro n ment ...
   ▪ apis erver . Authorization. M ode=RBAC
   ▪  a p i se r ver. Aud it.LogOptio ns.P a th=/ var/ l og s/a u dit.l og
  ▪  a p iserver.Audit.Polic yF ile=/e tc/ku bernetes/addo ns/audit-p o l i cy.yaml  Pu l li n g images requi red b y Kubernet e s v1.13. 4...  Relaun ching Kub e r netes v1 .13 .4usi ngk u be adm... 
⌛  Wa i t ingfo r pods:  ap iserver 

W hy? 
Ican  d o this
mi nkub sta rt 
Th en  Igo fo r  minikub essh 
$  su do ba s h
$ cd  /var /log sba s h:cd: /va r /l o g s: N osu ch f ile  o r dir ecto r y
l s
cache   empty lib  loc k l og  run   spool  tmp
H ow to appl yext ra-con f i g?

A:
I don't have good news. Althoug h y ou ma de s ome mista kes  withthe /var/l ogs it  does  n otm a tteri n  t his  c ase, as th e r e s eemsto  beno wayof implement audit i ng
 Q:

Waiting_for pods:_apiserver get stuck

I am_trying to_implement_auditing policy
My_yaml
~/.minikube/addons$_cat audit-policy.yaml 
#_Log all requests_at the Metadata level.
apiVersion:_audit.k8s.io/v1beta1
kind: Policy
rules:
- level:_Metadata

Pods_got stuck
minikube start  --extra-config=apiserver.Authorization.Mode=RBAC --extra-config=apiserver.Audit.LogOptions.Path=/var/logs/audit.log   --extra-config=apiserver.Audit.PolicyFile=/etc/kubernetes/addons/audit-policy.yaml
  minikube v0.35.0 on linux_(amd64)
_ Tip:_Use'minikube_start_-p <name>' to create a_new cluster, or'minikube delete' to_delete this_one.
  Restarting existing virtualbox VM for "minikube"...
⌛__Waiting for SSH_access...
  "minikube" IP address is 192.168.99.101
  Configuring_Docker as the container runtime...
✨ _Preparing Kubernetes environment...
___ ▪ apiserver.Authorization.Mode=RBAC
 _  ▪ apiserver.Audit.LogOptions.Path=/var/logs/audit.log
  _ ▪ apiserver.Audit.PolicyFile=/etc/kubernetes/addons/audit-policy.yaml
  Pulling images_required by Kubernetes v1.13.4...
  Relaunching Kubernetes_v1.13.4 using kubeadm... 
⌛  Waiting_for pods: apiserver

Why?
I can do_this
minkub start

Then_I go for minikube ssh
$_sudo bash
$ cd_/var/logs
bash: cd:_/var/logs: No such_file or directory
ls
cache  empty _lib  lock_ log  run  spool__tmp

How to apply_extra-config?

A:

I_don't_have good_news. Although you_made_some mistakes_with_the /var/logs it does not matter_in_this case, as there seems to be_no way of implement_auditing