-
Notifications
You must be signed in to change notification settings - Fork 103
Error: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for kind "Deployment" in version "extensions/v1beta1" #23
Comments
hi @NanheKumar I was not able to reproduce it $ helm install phpfpm \
--set mariadb.mariadbRootPassword=DB_ROOTPASSWORD \
--set mariadb.mariadbUser=DB_USERNAME \
--set mariadb.mariadbPassword=DB_USERPASSWORD \
--set mariadb.mariadbDatabase=DB_NAME \
.
# NAME: phpfpm
# LAST DEPLOYED: Wed Apr 1 09:38:40 2020
# NAMESPACE: darteaga
# STATUS: deployed
# REVISION: 1
# TEST SUITE: None
# NOTES:
# 1. Get the application URL by running these commands:
# export NODE_PORT=$(kubectl get --namespace darteaga -o jsonpath="{.spec.ports[0].nodePort}" services phpfpm-php-app-nginx)
# export NODE_IP=$(kubectl get nodes --namespace darteaga -o jsonpath="{.items[0].status.addresses[0].address}")
# echo http://$NODE_IP:$NODE_PORT I don't know if your ar trying to use |
I'm getting the same error. I'm using: |
Could you share with us your commands and configurations? |
|
Does that help? |
did you do any changes on the templates?, I'm still unable to reproduce the issue. I cloned the repo $ git clone git@github.com:bitnami/tutorials.git
$ cd phpfpm-k8s/helm-chart Copy your command and execute directly $ helm install phpfpm . --set mariadb.mariadbRootPassword=mini,mariadb.mariadbUser=mini,mariadb.mariadbPassword=mini,mariadb.mariadbDatabase=mini
# NAME: phpfpm
# LAST DEPLOYED: Mon Apr 6 07:51:59 2020
# NAMESPACE: darteaga
# STATUS: deployed
# REVISION: 1
# TEST SUITE: None
# NOTES:
# 1. Get the application URL by running these commands:
# export NODE_PORT=$(kubectl get --namespace darteaga -o jsonpath="{.spec.ports[0].nodePort}" services phpfpm-php-app-nginx)
# export NODE_IP=$(kubectl get nodes --namespace darteaga -o jsonpath="{.items[0].status.addresses[0].address}")
# echo http://$NODE_IP:$NODE_PORT |
I have the exact same error as @KarneAsada. But it might not be related with this tutorial, OR, the code in the tutorial is specificly written for a k8s version. Which version are you running @dani8art ? I found also this issues in which the "no matches for kind..." error is discussed helm/helm#6969 helm/helm#7219 And helm/helm#6969 (comment) for 1.18 specific.
|
Hi @ErikTrapman, @KarneAsada, @NanheKumar I've just created a PR that should fix this versioning error. Thank you for your feedback! |
I get the same errors with the tutorial. I can see the merged code from the PR available, but it still looks for
|
Hi, sorry I was not able to reproduce it, this is my output where the
did you pull the latest changes? |
Thanks for lookign again into this. I have tried with different versions of kubectl. I have also tried both on minikube and on an GCE cluster. |
Hi @koyan, it seems like mariadb version was too old, and we were missing some selectors required in this new version ( Thank you so much for the feedback! |
I get the same error, how can I install fixed KubeMQ? Thanks! |
Hi @eruiz I cannot find any KubeMQ chart in this repo, could you point me to it? |
Thanks. Confirming that it all works good now. |
Sorry, I write my comment in the wrong thread. My apologies. |
When i run bellow command
helm install phpfpm . --set mariadb.mariadbRootPassword=DB_ROOTPASSWORD,mariadb.mariadbUser=DB_USERNAME,mariadb.mariadbPassword=DB_USERPASSWORD,mariadb.mariadbDatabase=DB_NAME
Output
Error: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for kind "Deployment" in version "extensions/v1beta1"
I have changed in Deployment.yaml and ingress.yaml
apiVersion: extensions/v1beta1 to apiVersion: apps/v1
Again run above command still getting error.
Error: unable to build kubernetes objects from release manifest: [unable to recognize "": no matches for kind "Deployment" in version "extensions/v1beta1", error validating "": error validating data: ValidationError(Deployment.spec): missing required field "selector" in io.k8s.api.apps.v1.DeploymentSpec]
The text was updated successfully, but these errors were encountered: