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.

Sign up for GitHub

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

Jump to bottom

Add docs to describe how to build addon operators #11

Closed
4 tasks
dholbach opened this issue Jun 14, 2019 · 12 comments · Fixed by #58
Closed
4 tasks

Add docs to describe how to build addon operators #11

dholbach opened this issue Jun 14, 2019 · 12 comments · Fixed by #58
Labels
kind/documentation Categorizes issue or PR as related to documentation.

Comments

@dholbach
Copy link
Member

This should ideally cover

  • quick intro: what's an addon operator
  • explaining structure, bare minimum of work
  • links to already existing bits
  • caveats(?)
@dholbach
Copy link
Member Author

dholbach commented Jun 14, 2019 •
edited
Loading

/kind documentation

@k8s-ci-robot k8s-ci-robot added the kind/documentation Categorizes issue or PR as related to documentation. label Jun 14, 2019
@stealthybox
Copy link
Contributor

stealthybox commented Jun 14, 2019 •
edited
Loading

Contributor tooling + docs

  • docs + Makefile using kind to make development easier -- merged to kubebuilder-declarative-pattern
  • docs + U/X for go.mod support

@dholbach dholbach mentioned this issue Jul 1, 2019
Closed
@dholbach
Copy link
Member Author

Maybe do after #24?

@dholbach dholbach mentioned this issue Sep 18, 2019
Closed
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 10, 2019
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 10, 2019
@dholbach
Copy link
Member Author

/remove-lifecycle rotten

@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Dec 11, 2019
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 10, 2020
@rajansandeep
Copy link
Contributor

/remove-lifecycle stale
/lifecycle active

@k8s-ci-robot k8s-ci-robot added lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Mar 10, 2020
@vnzongzna
Copy link

@dholbach Can I take this issue if no one is working on it currently?

@dholbach
Copy link
Member Author

@vaibhavk Thanks for reaching out.

I believe this will be worked on as part of #39 or #47 - @stealthybox @justinsb @johnsonj please correct me if I'm wrong.

In any case, any help is appreciated!

@rajansandeep rajansandeep mentioned this issue Jun 2, 2020
Merged
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. and removed lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. labels Jul 1, 2020
@dholbach
Copy link
Member Author

dholbach commented Jul 1, 2020

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/documentation Categorizes issue or PR as related to documentation.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Adding documentation for CoreDNS operator and building an addon-operator rajansandeep/cluster-addons
6 participants
@dholbach @stealthybox @k8s-ci-robot @vnzongzna @rajansandeep @fejta-bot