Add information about MastOperator

kubernetes / website

Kubernetes website and documentation repo:

https://kubernetes.io

Creative Commons Attribution 4.0 International

4.37k stars 14.14k forks source link

Add information about MastOperator #37354

Open kivio opened 1 year ago

kivio commented 1 year ago

Hi, we have build simplified method of building operators using Ansible - without image building (mostly). I propose to add link to documentation of our tool into https://kubernetes.io/docs/concepts/extend-kubernetes/operator/#writing-operator section.

Our tool documentation for operators: https://docs.ansi.services/mast/user_guide/operator/ Main documentation: https://docs.ansi.services/mast/

sftim commented 1 year ago

/language en

/kind feature

Why should we make this change @kivio? I recommend always mentioning the “why” for a feature request issue.

kivio commented 1 year ago

Sure, it's a valid question.

Why do we build Mast and why it can be valuable for others?

We are building huge enterprise environments that connect Kubernetes and not Kubernetes-based systems. As we, I mean group of people from few companies. We decided to choose Kubernetes as the center of our operational management. To implement it, we need to write new operators for managing such platforms. The best choice for performing actions in such circumstances is to select Ansible as code runner. However, ansible-operator as part of operator-framework is not flexible enough for our code changes. This makes us to decide to build simplified dynamic and declarative operator framework that will remove strong connection between code and handler definition. Its main goal of Mast. We do it as open source, as we love open source.

We believe that others can have similar needs, I got feedback with few cases for that tool. It makes us feel we should share information about possibility to do this to wider audience, this page is the best place for sharing such information.

RA489 commented 1 year ago

/triage accepted

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue or PR as fresh with /remove-lifecycle stale
Mark this issue or PR as rotten with /lifecycle rotten
Close this issue or PR with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

sftim commented 1 year ago

Anyone is welcome to work on this issue.

vaibhav2107 commented 1 year ago

/remove-lifecycle stale

k8s-triage-robot commented 3 weeks ago

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

Confirm that this issue is still relevant with /triage accepted (org members only)
Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted