-
Notifications
You must be signed in to change notification settings - Fork 614
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'main' into jpkrohling/lfx-mar-2024-otel
Signed-off-by: Ali Ok <[email protected]>
- Loading branch information
Showing
1 changed file
with
243 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -76,6 +76,22 @@ | |
- Bill Mulligan(@xmulligan, [email protected]) | ||
- Upstream Issue: https://github.com/cilium/community/issues/78 https://github.com/cilium/community/issues/27 | ||
|
||
### Istio | ||
|
||
#### Improve Test Coverage for Istio Ambient Mesh | ||
|
||
- Description: Ambient mesh is now one of the biggest features in Istio, but it is in its early stage. We are in the process of improving the test coverage for Ambient Mesh in order to move it to Beta. Ztunnel works as shared data plane within a node, it subscribes to `Workload` and `Authorization` resources, both need to be well tested. | ||
- Expected Outcome: | ||
- Enhanced UnitTest coverage for `Workload` and `Authorization` Delta xDS/Stow interface. | ||
- Enhanced integration tests for ztunnel Authorization Policy | ||
- Recommended Skills: Go, Istio Test Framework | ||
- Mentor(s): | ||
- Zhonghu Xu (@hzxuzhonghu, [email protected]) | ||
- Faseela K (@kfaseela, [email protected]) | ||
- Upstream Issue: | ||
- https://github.com/orgs/istio/projects/9 | ||
- https://github.com/istio/ztunnel/issues/251 | ||
|
||
### Jaeger | ||
|
||
#### Jaeger-V2 Storage Backends | ||
|
@@ -108,6 +124,39 @@ | |
- Jonah Kowall (@jkowall, [email protected]) | ||
- Upstream Issue: https://github.com/jaegertracing/jaeger/issues/5084 | ||
|
||
### KCL | ||
|
||
#### KCL Package Version Management | ||
|
||
- Description: The KCL package management tool primarily handles the management of third-party KCL packages for the KCL project, which includes tasks such as uploading and downloading these packages. When adding third-party packages to the KCL project, it is important to adhere to version management strategies. This involves carefully selecting and downloading the appropriate version of a package, especially when different versions of the same package are available. | ||
- Expected Outcome: Add version management to the KCL package management tool. | ||
- Recommended Skills: golang | ||
- Mentor(s): | ||
- Pengfei Xu (@Peefy, [email protected]) | ||
- Zhe Zong (@zong-zhe, [email protected]) | ||
- Upstream Issue (URL): https://github.com/kcl-lang/kpm/issues/246 | ||
|
||
#### KCL IDE Quick Fix | ||
|
||
- Description: When the KCL IDE encounters some errors in the KCL code, it can pop up `Quick Fix` prompts to help users quickly fix the errors. | ||
- Expected Outcome: Added Quick Fix for some error prompts in KCL IDE. | ||
- Recommended Skills: rust | ||
- Mentor(s): | ||
- Pengfei Xu (@Peefy, [email protected]) | ||
- Zheng Zhang (@He1pa, [email protected]) | ||
- Upstream Issue (URL): https://github.com/kcl-lang/kcl/issues/997 | ||
|
||
#### KCL IDE Update KCL Dependencies | ||
|
||
- Description: When a KCL package is loaded using KCL IDE, the IDE automatically updates the dependencies of the current KCL package through kpm. | ||
- Expected Outcome: Add automatic updates for third-party libraries to the IDE. | ||
- Recommended Skills: rust, go | ||
- Mentor(s): | ||
- Pengfei Xu (@Peefy, [email protected]) | ||
- Zheng Zhang (@He1pa, [email protected]) | ||
- Zhe Zong (@zong-zhe, [email protected]) | ||
- Upstream Issue (URL): https://github.com/kcl-lang/kcl/issues/998 | ||
|
||
### Knative Eventing | ||
|
||
#### Cross Namespace Event Links | ||
|
@@ -122,6 +171,158 @@ | |
- Pierangelo Di Pilato (@pierdipi, [email protected]) | ||
- Upstream Issue: https://github.com/knative/eventing/issues/7530 | ||
|
||
### Konveyor | ||
|
||
#### Move2Kube: Exploratory approaches to artifact manipulation. | ||
|
||
- Description: Move2Kube is a command-line tool for automating creation of Infrastructure as code (IaC) artifacts. It has built-in support for creating IaC artifacts for replatforming to Kubernetes/OpenShift. As part of replatforming, we want to allow artifact manipulation at various levels to handle complex cases of replatforming flows. Example - while re-platforming from Netflix OSS spring boot feign client + eureka setup to Kubernetes (kubedns, kube-dns, services, ingress etc.) could need some artifact changes at different levels (code, architecture etc.). | ||
- Expected Outcome: | ||
- Identify various forms of artifact manipulation and explore approaches to support such manipulations. | ||
- Recommended Skills: | ||
- Golang | ||
- program analysis | ||
- Mentor(s): | ||
- Akash Nayak (@akash.nayak1, [email protected]) | ||
- Harikrishnan Balagopal (@HarikrishnanBalagopal, [email protected]) | ||
- Mehant Kammakomati (@kmehant, [email protected]) | ||
- Upstream Issue: https://github.com/konveyor/move2kube/issues/1130 | ||
|
||
#### Move2Kube: Simplify plugin architecture of m2k | ||
|
||
- Description: Move2Kube is a command-line tool for automating creation of Infrastructure as code (IaC) artifacts. The tool has a powerful plugin based transformer architecture where developers can write their own custom transformer plugins to fulfil their re-platforming needs. However, concepts like path mappings etc could be simplified for better adoption. Example - writing a Move2Kube custom transformer needs developers to understand various concepts such as path mappings etc, can we reduce this learning overhead by simplifying the Move2Kube architecture? | ||
- Expected Outcome: | ||
- Come up with a simplified alternative design for plugin architecture for M2K | ||
- Migrate existing components to support the new design with backward compatibility (good to have). | ||
- Recommended Skills: | ||
- Golang | ||
- K8s | ||
- Mentor(s): | ||
- Akash Nayak (@akash.nayak1, [email protected]) | ||
- Harikrishnan Balagopal (@HarikrishnanBalagopal, [email protected]) | ||
- Mehant Kammakomati (@kmehant, [email protected]) | ||
- Upstream Issue: https://github.com/konveyor/move2kube/issues/1131 | ||
|
||
#### Move2Kube: Advanced Resources support and enhance other Move2Kube components | ||
|
||
- Description: Move2Kube is a command-line tool for automating creation of Infrastructure as code (IaC) artifacts. It has built-in support for creating IaC artifacts for replatforming to Kubernetes/OpenShift. Currently we have support for resources such as ArgoCD, Tekton, etc. There is still a gap to be covered in the support Move2Kube provides. Example - enhance support for external transformers (GRPC, file/folder permissions, etc.). | ||
- Expected Outcome: | ||
- More comprehensive support for Move2Kube advanced resources and other components. | ||
- Recommended Skills: | ||
- Golang | ||
- K8s | ||
- ArgoCD | ||
- Tekton | ||
- Mentor(s): | ||
- Akash Nayak (@akash.nayak1, [email protected]) | ||
- Harikrishnan Balagopal (@HarikrishnanBalagopal, [email protected]) | ||
- Mehant Kammakomati (@kmehant, [email protected]) | ||
- Upstream Issue: https://github.com/konveyor/move2kube/issues/1132 | ||
|
||
### Kubearmor | ||
|
||
#### Kubearmor Kata Container Support | ||
|
||
- Description: Kata Containers is an open source community working to build a secure container runtime with lightweight virtual machines that feel and perform like containers, but provide stronger workload isolation using hardware virtualization technology as a second layer of defense. | ||
- Expected Outcome: KubeArmor natively protecting Kata containers with required Integration. | ||
- Recommended Skills: Go, Kubernetes, Linux | ||
- Mentor(s): | ||
- Barun Acharya (@daemon1024, [email protected]) | ||
- Prashant Mishra (@primalpimmy, [email protected]) | ||
- Rudraksh Pareek (@DelusionalOptimist, [email protected] ) | ||
- Upstream Issue: https://github.com/kubearmor/KubeArmor/issues/1340 | ||
|
||
#### Leverage OCI Hooks for Container Events | ||
|
||
- Description: Use OCI hooks and get events in context to container start/stop: Currently KubeArmor mounts docker/containerd/crio UNIX domain socket file in KubeArmor to watch for container events. The aim is to use OCI hooks for getting such container events. | ||
- Expected Outcome: Eliminate exposing docker/containerd/crio UNIX domain sockets inside a container. | ||
- Recommended Skills: Go, Kubernetes, Linux | ||
- Mentor(s): | ||
- Barun Acharya (@daemon1024, [email protected]) | ||
- Akshay Gaikwad (@akshay196, [email protected]) | ||
- Rudraksh Pareek (@DelusionalOptimist, [email protected] ) | ||
- Upstream Issue: https://github.com/kubearmor/KubeArmor/issues/1390 | ||
|
||
#### Dashboards for application behavior and KubeArmor state | ||
|
||
- Description: For showing an application's behaviour, we'd like to have a Kibana/Grafana dashboard. We have existing integrations for | ||
visualizing alerts with Elastic/Loki and we can use them for creating these. | ||
We want to leverage the above for creating a plugin which will allow users to see an application's behavior based on visibility logs sent by KubeArmor. | ||
- Expected Outcome: A kubernetes dashboard setup that also has the app behaviours described. | ||
- Recommended Skills: Grafana, Javascript, Go, Kubernetes, Linux | ||
- Mentor(s): | ||
- Barun Acharya (@daemon1024, [email protected]) | ||
- Prashant Mishra (@primalpimmy, [email protected]) | ||
- Rudraksh Pareek (@DelusionalOptimist, [email protected] ) | ||
- Anurag Kumar (@kranurag7, [email protected]) | ||
- Upstream Issue: https://github.com/kubearmor/KubeArmor/issues/1390 | ||
|
||
### KubeVela | ||
|
||
#### Support versioning for definitions | ||
|
||
- Description: In KubeVela, X-Definitions provide the foundation for users to construct their applications. Currently we will automatically upgrade the definitions' version for our users, however, we still need the capability of explicit versioning in definitions. With this feature, our users can now manage the version easily for application upgrades and migrations. | ||
- Expected Outcome: Support expilict versioning in definitions to help application upgrades and migrations. | ||
- Recommended Skills: Go, Kubernetes | ||
- Mentor(s): | ||
- Fog Dong (@FogDong, [email protected]) | ||
- Zhongpei Qiao(@chivalryq, [email protected]) | ||
- Upstream Issue: https://github.com/kubevela/kubevela/issues/6435 | ||
|
||
### Kyverno | ||
|
||
#### Kyverno for Envoy Authorization | ||
|
||
- Description: Build an Envoy plugin to support authorisation based on Kyverno policies. | ||
- Expected Outcome: Enable users to perform autorisation with similar concepts as kyverno and kyverno-JSON using policies. | ||
- Recommended Skills: Golang, Kubernetes, Envoy | ||
- Mentor(s): | ||
- Charles-Edouard Brétéché (@eddycharly, [email protected]) | ||
- Anushka Mittal (@anushkamittal2001, [email protected]) | ||
- Upstream Issue: https://github.com/kyverno/kyverno/issues/9488 | ||
|
||
#### Kyverno VPA Recommender | ||
|
||
- Description: A common pain-point heard from users is improper resource allocations, and if Kyverno policies can help with that. This is an exploratory project to see if Kyverno can work with Kubernetes Vertical Pod Autoscalers (VPA). | ||
- Expected Outcome: Kyverno policies that work with VPA recommender. | ||
- Recommended Skills: Golang, Kubernetes | ||
- Mentor(s): | ||
- Jim Bugwadia (@jimbugwadia, [email protected]) | ||
- Khaled Emara (@KhaledEmaraDev, [email protected]) | ||
- Upstream Issue: https://github.com/kyverno/kyverno/issues/9429 | ||
|
||
|
||
#### Convert Kubernetes Best Practices Policies to CEL | ||
|
||
- Description: Kubernetes Best Practices policies are written using Kyverno patterns and JMESPath, which means they cannot be executed as ValidatingAdmissionPolicy resources in the API server. This project aims to convert Kubernetes Best Practices policies, and other validating policies, to CEL wherever possible. | ||
- Expected Outcome: Convert Kyverno policies for Kubernetes best practices to CEL. | ||
- Recommended Skills: Kubernetes, Kyverno policies, CEL | ||
- Mentor(s): | ||
- Anusha Hegde (@anusha94, [email protected]) | ||
- Mariam Fahmy (@MariamFahmy98, [email protected]) | ||
- Upstream Issue: https://github.com/kyverno/policies/issues/891 | ||
|
||
#### Verify Multiple Image Attestations | ||
|
||
- Description: Currently Kyverno cannot verify data across multiple attestations e.g. an image vulnerability scan report and a OpenVEX document. This project will enhance the image verification rules to support flexible checks across multiple attestations. | ||
- Expected Outcome: Support condition validation across multiple image verification attestations or context entry. | ||
- Recommended Skills: Golang, Kubernetes, VEX, Cosign, Notary | ||
- Mentor(s): | ||
- Vishal Choudhary (@vishal-chdhry, [email protected]) | ||
- Shuting Zhao (@realshuting, [email protected]) | ||
- Upstream Issue: https://github.com/kyverno/kyverno/issues/9456 | ||
|
||
### K8sGPT | ||
|
||
#### Enhance K8sGPT's analyzers Unit Test Coverage | ||
|
||
- Description: K8sGPT is a tool for scanning Kubernetes clusters, diagnosing and triaging issues with the help of GenAI. It has SRE experience codified into its analyzers. These analyzers are critical for K8sGPT to perform its in-depth analysis. There are a few analysers that have either limited or absent unit tests. The goal is to introduce more unit tests which will reflect mocked problematic/misconfigured K8s resources and assure K8sGPT analysers can catch and identify those test scenarios. | ||
- Expected Outcome: Introduce and enhance Test Coverage of K8sGPT's analyzers | ||
- Recommended Skills: Go, Kubernetes | ||
- Mentor(s): | ||
- Alex Jones (@AlexsJones, [email protected]) | ||
- Aris Boutselis (@arbreezy, [email protected]) | ||
- Issue: https://github.com/k8sgpt-ai/k8sgpt/issues/889 | ||
|
||
### OpenTelemetry | ||
|
||
#### One Logging Bridge per Language | ||
|
@@ -169,3 +370,45 @@ | |
- [Manan Gupta](https://github.com/GuptaManan100) ([email protected]) | ||
- [Harshit Gangal](https://github.com/harshit-gangal) ([email protected]) | ||
- Issue: <https://github.com/vitessio/vitess/issues/14931> | ||
|
||
### WasmEdge | ||
|
||
#### Integrate MLX as a new WASI-NN backend | ||
|
||
- Description: LLM is a hot topic, there are more and more frameworks to make the execution of LLM faster. WasmEdge already integrated the [llama.cpp](https://github.com/ggerganov/llama.cpp) as one of the backend. And we want to bring more. [MLX](https://github.com/ml-explore/mlx) is an array framework on Apple silicon created by Apple machine learning research. With MLX, we believe it can have a huge improvement on macOS. | ||
- Expected Outcome: A new plugin provides a MLX [WASI-NN](https://github.com/second-state/wasmedge-wasi-nn) backend, a test suite for validating the plugin, documents and examples for explaining how to use the plugin. | ||
- Recommended Skills: C++, Wasm | ||
- Mentor(s): | ||
- Hung-Ying Tai (@hydai, [email protected]) | ||
- dm4 (@dm4, [email protected]) | ||
- Upstream Issue: https://github.com/WasmEdge/WasmEdge/issues/3168 | ||
|
||
#### Integrate Intel Extension for Transformers as a new WASI-NN backend | ||
|
||
- Description: LLM is a hot topic, there are more and more frameworks to make the execution of LLM faster. WasmEdge already integrated the [llama.cpp](https://github.com/ggerganov/llama.cpp) as one of the backend. Running LLM with CPU only is huge for those users who don't have GPU. We would like to integrate [Intel Extension for Transformers](https://github.com/intel/intel-extension-for-transformers) as a new WASI-NN backend to provide a faster CPU inference performance. | ||
- Expected Outcome: A new plugin provides a Intel Extension for Transformers [WASI-NN](https://github.com/second-state/wasmedge-wasi-nn) backend, a test suite for validating the plugin, documents and examples for explaining how to use the plugin. | ||
- Recommended Skills: C++, Wasm | ||
- Mentor(s): | ||
- Hung-Ying Tai (@hydai, [email protected]) | ||
- dm4 (@dm4, [email protected]) | ||
- Upstream Issue: https://github.com/WasmEdge/WasmEdge/issues/3169 | ||
|
||
#### Integrate whisper.cpp as a new WASI-NN backend | ||
|
||
- Description: WasmEdge supports PyTorch, TensorFlow Lite, llama.cpp, and more NN backend. Dealing with the Voice to Text is a big thing that we want to achieve. To make it possible, we would like to integrate [whisper.cpp](https://github.com/ggerganov/whisper.cpp), a port of OpenAI's Whisper model in C/C++ as a new [WASI-NN](https://github.com/second-state/wasmedge-wasi-nn) backend. | ||
- Expected Outcome: A new plugin provides a whisper.cpp [WASI-NN](https://github.com/second-state/wasmedge-wasi-nn) backend, a test suite for validating the plugin, documents and examples for explaining how to use the plugin. | ||
- Recommended Skills: C++, Wasm | ||
- Mentor(s): | ||
- Hung-Ying Tai (@hydai, [email protected]) | ||
- dm4 (@dm4, [email protected]) | ||
- Upstream Issue: https://github.com/WasmEdge/WasmEdge/issues/3170 | ||
|
||
#### Integrate burn.rs as a new WASI-NN backend | ||
|
||
- Description: WasmEdge supports PyTorch, TensorFlow Lite, llama.cpp, and more NN backend. [Burn.rs](https://github.com/tracel-ai/burn) is a new deep learning framework built using Rust. The portability, flexibility, and compute efficiency are important to Wasm. That's why we would love to have `burn.rs` as a new [WASI-NN](https://github.com/second-state/wasmedge-wasi-nn) backend. | ||
- Expected Outcome: A new plugin provides a burn.rs [WASI-NN](https://github.com/second-state/wasmedge-wasi-nn) backend, a test suite for validating the plugin, documents and examples for explaining how to use the plugin. | ||
- Recommended Skills: Rust, Wasm | ||
- Mentor(s): | ||
- Hung-Ying Tai (@hydai, [email protected]) | ||
- dm4 (@dm4, [email protected]) | ||
- Upstream Issue: https://github.com/WasmEdge/WasmEdge/issues/3172 |