(→Participants: Add myself) |
(Added dkirwan / David Kirwan) |
||
| (8 intermediate revisions by 5 users not shown) | |||
| Line 9: | Line 9: | ||
* [[User:lrossett|Leonardo Rossetti]] | * [[User:lrossett|Leonardo Rossetti]] | ||
* [[User:ngompa|Neal Gompa]] | * [[User:ngompa|Neal Gompa]] | ||
* [[User:kad|Jorge Gallegos]] | |||
* [[User:defolos|Dan Čermák]] | |||
* [[User:patux|Patrick Vavrina]] | |||
* [[User:dkirwan|David Kirwan]] | |||
== Joining the SIG == | == Joining the SIG == | ||
| Line 16: | Line 20: | ||
== Comms == | == Comms == | ||
The main communication channels are doing in our | The main communication channels are doing in our IRC channel and fedora mailing list. | ||
=== Issue Tracker === | |||
https://pagure.io/kube-sig/kube-sig | |||
=== Meetings === | === Meetings === | ||
| Line 24: | Line 32: | ||
=== IRC Channel === | === IRC Channel === | ||
There is an existing | There is an existing irc channel for developers and users of Kubernetes in Fedora: {{fpchat|#fedora-kube}} | ||
=== Mailing List === | === Mailing List === | ||
| Line 30: | Line 38: | ||
You can also subscribe to our mailing list: [https://lists.fedoraproject.org/archives/list/kube@lists.fedoraproject.org/ kube@lists.fedoraproject.org] | You can also subscribe to our mailing list: [https://lists.fedoraproject.org/archives/list/kube@lists.fedoraproject.org/ kube@lists.fedoraproject.org] | ||
== | == Scope == | ||
=== Development Experience and Learning === | === Development Experience and Learning === | ||
| Line 54: | Line 62: | ||
A place for sysadmins and ops engineers to discuss the challenges, practices and tooling of monitoring, deploying and running operators, api servers and other related kubernetes components in production. | A place for sysadmins and ops engineers to discuss the challenges, practices and tooling of monitoring, deploying and running operators, api servers and other related kubernetes components in production. | ||
== Proposals == | |||
[[Proposal: Koji Operator|Koji Operator (DRAFT)]] | |||
[[Proposal: Fedora Messaging Publisher Operator|Fedora Messaging Publisher Operator (DRAFT)]] | |||
== References == | == References == | ||
Latest revision as of 11:44, 24 April 2023
Fedora Kubernetes Development Special Interest Group
Mission
The KubeDev SIG (Special Interest Group) is a group of Fedora contributors that discuss and work on Kubernetes related technologies.
Participants
Joining the SIG
Joining the KubeDev SIG is as simple as being part of Fedora and having a love for kubernetes and related technologies. Once you are a contributor to Fedora, you can join the SIG by adding your name above and communicating with the rest of the team in our IRC channel: #fedora-kube[?].
Comms
The main communication channels are doing in our IRC channel and fedora mailing list.
Issue Tracker
https://pagure.io/kube-sig/kube-sig
Meetings
TBD
IRC Channel
There is an existing irc channel for developers and users of Kubernetes in Fedora: #fedora-kube[?]
Mailing List
You can also subscribe to our mailing list: kube@lists.fedoraproject.org
Scope
Development Experience and Learning
A place to exchange and discuss Kubernetes development design and patterns.
Extending kubernetes is not that straightforward so this SIG would be a good place to learn more about it.
Kubernetes can be extended in the following areas:
- Kubectl Plugins
- Custom API Servers
- Custom Controllers / Operators
Operator Development
The Operator SDK is the shining new framework when developing custom kubernetes controllers nas has become a popular tool for packaging and deploying applications in kubernetes.
Some Fedora services and components could leverage the usage of an operator but other services could be deployed via operators as well and even the mbbox operator could be split into smaller operators.
Kubernetes DevOps
A place for sysadmins and ops engineers to discuss the challenges, practices and tooling of monitoring, deploying and running operators, api servers and other related kubernetes components in production.
Proposals
Fedora Messaging Publisher Operator (DRAFT)