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

Update docs about how CRDs are managed #1278

Merged
merged 4 commits into from
Mar 16, 2022
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions docs/install.rst
Original file line number Diff line number Diff line change
Expand Up @@ -45,6 +45,16 @@ This will install the Kanister controller in the ``kanister`` namespace
--namespace kanister


Kanister Custom Resource Definitions (CRD)
viveksinghggits marked this conversation as resolved.
Show resolved Hide resolved
==========================================

`Custom Resource Definitions <https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/>`_
that Kanister needs are, by default, managed by Kanister controller. If Kanister
controller doesn't have the authorization to create or update CRDs, you can disable
that using ``controller.updateCRDs`` helm flag. If set to ``false``, helm will
manage the CRDs instead of Kanister controller.
viveksinghggits marked this conversation as resolved.
Show resolved Hide resolved


Building and Deploying from Source
==================================

Expand Down