Closed ppaslan closed 2 years ago
Hi @ppaslan, thanks for reporting!
CRDs are installed using the standard helm (v3) mechanism, by placing them into the chart's crds
directory, see helm docs.
Can I ask you to run the helm version
command and paste the output?
You can eventually install them manually by running:
kubectl apply --server-side -f https://raw.githubusercontent.com/xco-sk/eck-custom-resources/eck-custom-resources-operator-0.3.2/config/crd/bases/es.eck.github.com_elasticsearchroles.yaml
kubectl apply --server-side -f https://raw.githubusercontent.com/xco-sk/eck-custom-resources/eck-custom-resources-operator-0.3.2/config/crd/bases/es.eck.github.com_elasticsearchusers.yaml
kubectl apply --server-side -f https://raw.githubusercontent.com/xco-sk/eck-custom-resources/eck-custom-resources-operator-0.3.2/config/crd/bases/es.eck.github.com_indexlifecyclepolicies.yaml
kubectl apply --server-side -f https://raw.githubusercontent.com/xco-sk/eck-custom-resources/eck-custom-resources-operator-0.3.2/config/crd/bases/es.eck.github.com_indextemplates.yaml
kubectl apply --server-side -f https://raw.githubusercontent.com/xco-sk/eck-custom-resources/eck-custom-resources-operator-0.3.2/config/crd/bases/es.eck.github.com_indices.yaml
kubectl apply --server-side -f https://raw.githubusercontent.com/xco-sk/eck-custom-resources/eck-custom-resources-operator-0.3.2/config/crd/bases/es.eck.github.com_ingestpipelines.yaml
kubectl apply --server-side -f https://raw.githubusercontent.com/xco-sk/eck-custom-resources/eck-custom-resources-operator-0.3.2/config/crd/bases/es.eck.github.com_snapshotlifecyclepolicies.yaml
kubectl apply --server-side -f https://raw.githubusercontent.com/xco-sk/eck-custom-resources/eck-custom-resources-operator-0.3.2/config/crd/bases/es.eck.github.com_snapshotrepositories.yaml
kubectl apply --server-side -f https://raw.githubusercontent.com/xco-sk/eck-custom-resources/eck-custom-resources-operator-0.3.2/config/crd/bases/kibana.eck.github.com_dashboards.yaml
kubectl apply --server-side -f https://raw.githubusercontent.com/xco-sk/eck-custom-resources/eck-custom-resources-operator-0.3.2/config/crd/bases/kibana.eck.github.com_indexpatterns.yaml
kubectl apply --server-side -f https://raw.githubusercontent.com/xco-sk/eck-custom-resources/eck-custom-resources-operator-0.3.2/config/crd/bases/kibana.eck.github.com_lens.yaml
kubectl apply --server-side -f https://raw.githubusercontent.com/xco-sk/eck-custom-resources/eck-custom-resources-operator-0.3.2/config/crd/bases/kibana.eck.github.com_savedsearches.yaml
kubectl apply --server-side -f https://raw.githubusercontent.com/xco-sk/eck-custom-resources/eck-custom-resources-operator-0.3.2/config/crd/bases/kibana.eck.github.com_spaces.yaml
kubectl apply --server-side -f https://raw.githubusercontent.com/xco-sk/eck-custom-resources/eck-custom-resources-operator-0.3.2/config/crd/bases/kibana.eck.github.com_visualizations.yaml
Thanks for the quick Replay, assumed crds was included in the helm chart, i'll just copy them over.
Thanks!
On Fri, Jul 1, 2022, 15:21 Marek Hornak @.***> wrote:
Hi @ppaslan https://github.com/ppaslan, thanks for reporting! CRDs are installed using the standard helm (v3) mechanism, by placing them into the chart's crds directory, see helm docs https://helm.sh/docs/chart_best_practices/custom_resource_definitions/#method-1-let-helm-do-it-for-you . Can I ask you to run the helm version command and paste the output?
You can eventually install them manually by running:
kubectl apply --server-side -f https://raw.githubusercontent.com/xco-sk/eck-custom-resources/eck-custom-resources-operator-0.3.2/config/crd/bases/es.eck.github.com_elasticsearchroles.yaml kubectl apply --server-side -f https://raw.githubusercontent.com/xco-sk/eck-custom-resources/eck-custom-resources-operator-0.3.2/config/crd/bases/es.eck.github.com_elasticsearchusers.yaml kubectl apply --server-side -f https://raw.githubusercontent.com/xco-sk/eck-custom-resources/eck-custom-resources-operator-0.3.2/config/crd/bases/es.eck.github.com_indexlifecyclepolicies.yaml kubectl apply --server-side -f https://raw.githubusercontent.com/xco-sk/eck-custom-resources/eck-custom-resources-operator-0.3.2/config/crd/bases/es.eck.github.com_indextemplates.yaml kubectl apply --server-side -f https://raw.githubusercontent.com/xco-sk/eck-custom-resources/eck-custom-resources-operator-0.3.2/config/crd/bases/es.eck.github.com_indices.yaml kubectl apply --server-side -f https://raw.githubusercontent.com/xco-sk/eck-custom-resources/eck-custom-resources-operator-0.3.2/config/crd/bases/es.eck.github.com_ingestpipelines.yaml kubectl apply --server-side -f https://raw.githubusercontent.com/xco-sk/eck-custom-resources/eck-custom-resources-operator-0.3.2/config/crd/bases/es.eck.github.com_snapshotlifecyclepolicies.yaml kubectl apply --server-side -f https://raw.githubusercontent.com/xco-sk/eck-custom-resources/eck-custom-resources-operator-0.3.2/config/crd/bases/es.eck.github.com_snapshotrepositories.yaml kubectl apply --server-side -f https://raw.githubusercontent.com/xco-sk/eck-custom-resources/eck-custom-resources-operator-0.3.2/config/crd/bases/kibana.eck.github.com_dashboards.yaml kubectl apply --server-side -f https://raw.githubusercontent.com/xco-sk/eck-custom-resources/eck-custom-resources-operator-0.3.2/config/crd/bases/kibana.eck.github.com_indexpatterns.yaml kubectl apply --server-side -f https://raw.githubusercontent.com/xco-sk/eck-custom-resources/eck-custom-resources-operator-0.3.2/config/crd/bases/kibana.eck.github.com_lens.yaml kubectl apply --server-side -f https://raw.githubusercontent.com/xco-sk/eck-custom-resources/eck-custom-resources-operator-0.3.2/config/crd/bases/kibana.eck.github.com_savedsearches.yaml kubectl apply --server-side -f https://raw.githubusercontent.com/xco-sk/eck-custom-resources/eck-custom-resources-operator-0.3.2/config/crd/bases/kibana.eck.github.com_spaces.yaml kubectl apply --server-side -f https://raw.githubusercontent.com/xco-sk/eck-custom-resources/eck-custom-resources-operator-0.3.2/config/crd/bases/kibana.eck.github.com_visualizations.yaml
— Reply to this email directly, view it on GitHub https://github.com/xco-sk/eck-custom-resources/issues/35#issuecomment-1172342971, or unsubscribe https://github.com/notifications/unsubscribe-auth/AV4YXMXA3DPMW3RVD5RUCF3VR3WDXANCNFSM52MTLYAQ . You are receiving this because you were mentioned.Message ID: @.***>
@ppaslan the CRD yamls are part of the released chart, they are not present in the chart folder here in the git repo because they are generated by kubebuilder. So the release pipeline generates the CRDs and copies them into the chart, that is then released as a build artifact. It depends on the version of helm if they are automatically deployed or not.
Installing the helm chart does not actually install any CRD's for the operator to manage. What are the recommended way to install this operator through helm?
Here are some startup logs. PS: Thank you for writing this operator.