search

ceph / ceph-helm

Curated applications for Kubernetes
Apache License 2.0
108 stars 36 forks source link

Not compatible with latest kubernetes #82

Open BlackTurtle123 opened 4 years ago

BlackTurtle123 commented 4 years ago

If this is a BUG REPORT, please: -The deployment isn't compatible with kubernetes 1.16

What happened:

secret/ceph-keystone-user-rgw unchanged configmap/ceph-bin-clients unchanged configmap/ceph-bin unchanged configmap/ceph-etc configured configmap/ceph-templates unchanged storageclass.storage.k8s.io/general unchanged service/ceph-mon unchanged service/ceph-rgw unchanged job.batch/ceph-storage-admin-key-cleaner-z0qki created job.batch/ceph-mds-keyring-generator unchanged job.batch/ceph-osd-keyring-generator unchanged job.batch/ceph-rgw-keyring-generator unchanged job.batch/ceph-mon-keyring-generator unchanged job.batch/ceph-mgr-keyring-generator unchanged job.batch/ceph-namespace-client-key-cleaner-xkx0p created job.batch/ceph-namespace-client-key-generator unchanged job.batch/ceph-storage-keys-generator unchanged unable to recognize "STDIN": no matches for kind "DaemonSet" in version "extensions/v1beta1" unable to recognize "STDIN": no matches for kind "Deployment" in version "apps/v1beta1" unable to recognize "STDIN": no matches for kind "Deployment" in version "apps/v1beta1" unable to recognize "STDIN": no matches for kind "Deployment" in version "apps/v1beta1" unable to recognize "STDIN": no matches for kind "Deployment" in version "extensions/v1beta1" unable to recognize "STDIN": no matches for kind "Deployment" in version "apps/v1beta1"

What you expected to happen: A cluster would need to be deployed

How to reproduce it (as minimally and precisely as possible): Install latest kubernetes, k3s,.. download the charts and run them

xforze commented 4 years ago

I can confirm this, did you already found a solution to deploy a ceph cluster ?

noprom commented 4 years ago

Same issue here on k8s 1.16.7.

avarf commented 4 years ago

Hi, I just started to look into ceph and I haven't installed it yet but this error is because the K8s api is not fully backward compatible after 1.16 and they need to edit their yaml files.

Just FYI, I think the latest K8s (1.18) is also not fully backward compatible.

wskibum commented 2 years ago

these seem to be the problems in the templates ~/ceph-helm$ grep -r v1beta1 * | grep ceph ceph/ceph/templates/daemonset-osd-devices.yaml:apiVersion: extensions/v1beta1 ceph/ceph/templates/daemonset-mon.yaml:apiVersion: extensions/v1beta1 ceph/ceph/templates/deployment-mds.yaml:apiVersion: apps/v1beta1 ceph/ceph/templates/deployment-moncheck.yaml:apiVersion: apps/v1beta1 ceph/ceph/templates/deployment-mgr.yaml:apiVersion: apps/v1beta1 ceph/ceph/templates/deployment-rbd-provisioner.yaml:apiVersion: extensions/v1beta1 ceph/ceph/templates/deployment-rgw.yaml:apiVersion: apps/v1beta1 ceph/ceph/templates/daemonset-osd.yaml:apiVersion: extensions/v1beta1

I've replaced both the extension and deployment to apps/vi the deployment seems fine, the Daemonsets choke with

Error: release ceph failed: daemonsets.apps is forbidden: User "system:serviceaccount:kube-system:default" cannot create resource "daemonsets" in API group "apps" in the namespace "ceph"