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

[v2] initial CRD generation #153

Open
lucasreed opened this issue Dec 11, 2020 · 1 comment
Open

[v2] initial CRD generation #153

lucasreed opened this issue Dec 11, 2020 · 1 comment
Assignees
Labels
enhancement Adding additional functionality or improvements pinned Prevents stalebot from removing
Milestone

Comments

@lucasreed
Copy link
Contributor

Using kubebuilder, create initial CRD manifests based on the design in DESIGN.md

@lucasreed lucasreed added enhancement Adding additional functionality or improvements pinned Prevents stalebot from removing labels Dec 11, 2020
@lucasreed lucasreed added this to the v2 milestone Dec 11, 2020
@lucasreed lucasreed self-assigned this Dec 11, 2020
@lucasreed lucasreed changed the title [v2 feature] initial CRD generation [v2] initial CRD generation Dec 11, 2020
@isaaguilar
Copy link
Contributor

isaaguilar commented Mar 26, 2021

I'm really interested in this idea. I created an astro-ruleset-operator for my job which takes a new resources (called the "ruleset" CRD) and translates that to the astro-data ConfigMap. I feel that this new v2 proposal would be a much better approach because the controller should just act on the custom resource directly and doesn't need to worry about the ConfigMap.

I'm looking forward to updates if this gains any traction. I'm willing to help if there are any tasks for v2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Adding additional functionality or improvements pinned Prevents stalebot from removing
Projects
None yet
Development

No branches or pull requests

2 participants