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

Give option to create a default profile at install time #82

Closed
gauthamsunjay opened this issue May 30, 2018 · 2 comments
Closed

Give option to create a default profile at install time #82

gauthamsunjay opened this issue May 30, 2018 · 2 comments

Comments

@gauthamsunjay
Copy link
Contributor

This option will simplify writing action sets for the users. The controller can default to the location and credentials provided in this profile if the users do not override them in their action sets.

@gauthamsunjay
Copy link
Contributor Author

The main drawback with this approach is that for every change in the schema of the profile CRD we will have to send a PR upstream which will take a long time to get approved. The alternative is to add a profile helm chart under kanister.

tdmanv pushed a commit that referenced this issue Jun 5, 2018
#82

--Use case--

Currently, when a user creates an actionset specifying a profile is mandatory. We just error out otherwise. This commit provides the users an option to create a default profile in the controller namespace. The default profile will be used when no profile is specified in the action set.
depohmel pushed a commit to kanisterio/charts that referenced this issue Jun 22, 2018
Provides the option to install a profile CR along with the operator
the profile CR is installed via a subchart

Kanister operator requires access to CRDs and Events.
Add this to the cluster-role.

Fixes kanisterio/kanister#82
fixes kanisterio/kanister#90
@gauthamsunjay
Copy link
Contributor Author

Upstream PR has been sent.

k8s-ci-robot pushed a commit to helm/charts that referenced this issue Jul 15, 2018
…#6280)

* [stable/kanister-operator] RBAC changes and default profile creation

Provides the option to install a profile CR along with the operator
the profile CR is installed via a subchart

Kanister operator requires access to CRDs and Events.
Add this to the cluster-role.

Fixes kanisterio/kanister#82
fixes kanisterio/kanister#90

* fixing repo url and version requirement

* Fix typo

* remove remote chart with local

* operator version to 0.10.0

* new lines EOF

* Update Chart.yaml
Jnig pushed a commit to Jnig/charts that referenced this issue Nov 13, 2018
…helm#6280)

* [stable/kanister-operator] RBAC changes and default profile creation

Provides the option to install a profile CR along with the operator
the profile CR is installed via a subchart

Kanister operator requires access to CRDs and Events.
Add this to the cluster-role.

Fixes kanisterio/kanister#82
fixes kanisterio/kanister#90

* fixing repo url and version requirement

* Fix typo

* remove remote chart with local

* operator version to 0.10.0

* new lines EOF

* Update Chart.yaml

Signed-off-by: Jakob Niggel <info@jakobniggel.de>
gsemet pushed a commit to gsemet/charts that referenced this issue Nov 13, 2018
…helm#6280)

* [stable/kanister-operator] RBAC changes and default profile creation

Provides the option to install a profile CR along with the operator
the profile CR is installed via a subchart

Kanister operator requires access to CRDs and Events.
Add this to the cluster-role.

Fixes kanisterio/kanister#82
fixes kanisterio/kanister#90

* fixing repo url and version requirement

* Fix typo

* remove remote chart with local

* operator version to 0.10.0

* new lines EOF

* Update Chart.yaml
depohmel pushed a commit that referenced this issue Aug 9, 2019
#82

--Use case--

Currently, when a user creates an actionset specifying a profile is mandatory. We just error out otherwise. This commit provides the users an option to create a default profile in the controller namespace. The default profile will be used when no profile is specified in the action set.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant