controller-runtime
nixpkgs
| controller-runtime | nixpkgs | |
|---|---|---|
| 53 | 975 | |
| 2,305 | 15,753 | |
| 1.0% | 2.2% | |
| 9.4 | 10.0 | |
| 6 days ago | about 19 hours ago | |
| Go | Nix | |
| Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
controller-runtime
-
AWS open source newsletter, #176
operatorpkg is a set of packages used to develop Kubernetes operators at AWS. It contains opinions on top of existing projects like https://github.com/kubernetes/apimachinery and https://github.com/kubernetes-sigs/controller-runtime. In many cases, we plan to mature packages in operatorpkg before commiting them upstream.
- New Release: controller-runtime v0.16.3
-
In CRDs how to set defaults for resources type?
however, at least in envtest this returns
- New Release: controller-runtime v0.15.0
- New Release: controller-runtime v0.15.0-beta.0
- New Release: controller-runtime v0.15.0-alpha.1
-
My CNCF LFX Mentorship Spring 2023 Project at Kubescape
(rejected) kubernetes-sigs/controller-runtime #2266 🐛 Support get config inside snap with SNAP_REAL_HOME
- New Release: controller-runtime v0.15.0-alpha.0
-
How to get a GroupVersionResource from a GroupVersionKind?
Check out https://github.com/kubernetes-sigs/controller-runtime/blob/main/pkg/client/example_test.go. It really is that easy :-).
-
Debugging concurrency: Adding millisecond sleeps randomly?
I am using Kubernetes controller-runtime envtest.
nixpkgs
-
Nix: The Breaking Point
I don't think so. The article is probably intended for the Nix community, so the author doesn't need to convince HN that something is going on. If as an outsider you are interested then you need to look into it yourself, the community has no obligation to make their internal conflicts legible to the outside world.
As an outsider myself, it certainly looks like something is going on as more than 20 Nixpkg maintainers left in a week: https://github.com/NixOS/nixpkgs/issues?q=label%3A%228.has%3...
- Maintainers Leaving
-
Air Force picks Anduril, General Atomics to develop unmanned fighter jets
https://github.com/NixOS/nixpkgs/commits?author=neon-sunset
-
Eelco Dolstra's leadership is corrosive to the Nix project
I see two signers in the top 6 displayed on https://github.com/NixOS/nixpkgs/graphs/contributors
-
3rd Edition of Programming: Principles and Practice Using C++ by Stroustrup
For a single file script, nix can make the package management quite easy: https://github.com/NixOS/nixpkgs/blob/master/doc/languages-f...
For example,
```
- NixOS/nixpkgs: There isn't a clear canonical way to refer to a specific package
-
NixOS Is Not Reproducible
Yes, Nix doesn't actually ensure that the builds are deterministic. In fact it works just fine if they aren't. There are packages in nixpkgs that aren't reproducible: https://github.com/NixOS/nixpkgs/issues?q=is%3Aopen+is%3Aiss...
-
The xz attack shell script
I'm not familiar with Bazel, but Nix in it's current form wouldn't have solved this attack. First of all, the standard mkDerivation function calls the same configure; make; make install process that made this attack possible. Nixpkgs regularly pulls in external resources (fetchUrl and friends) that are equally vulnerable to a poisoned release tarball. Checkout the comment on the current xz entry in nixpkgs https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/comp...
-
Debian Git Monorepo
NixOS uses a monorepo and I think everyone's love it.
I love being able to easily grep through all the packages source code and there's regularly PRs that harmonizes conventions across many packages.
Nixpkgs doesn't include the packaged software source code, so it's a lot more practical than what Debian is doing.
https://github.com/NixOS/nixpkgs
-
From xz to ibus: more questionable tarballs
In this specific case, nix uses fetchFromGitHub to download the source archive, which are generated by GitHub for the specified revision[1]. Arch seems to just download the tarball from the releases page[2].
[1]: https://github.com/NixOS/nixpkgs/blob/3c2fdd0a4e6396fc310a6e...
[2]: https://gitlab.archlinux.org/archlinux/packaging/packages/ib...
What are some alternatives?
client-go - Go client for Kubernetes.
asdf - Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more
controller-tools - Tools to use with the controller-runtime libraries
Home Manager using Nix - Manage a user environment using Nix [maintainer=@rycee]
operator-sdk - SDK for building Kubernetes applications. Provides high level APIs, useful abstractions, and project scaffolding.
git-lfs - Git extension for versioning large files
yaml - A better way to marshal and unmarshal YAML in Golang
easyeffects - Limiter, compressor, convolver, equalizer and auto volume and many other plugins for PipeWire applications
golang-design-pattern - 设计模式 Golang实现－《研磨设计模式》读书笔记
spack - A flexible package manager that supports multiple versions, configurations, platforms, and compilers.
sample-controller-kubebuilder - This is Sample Controller(Foo Controller) developed by Kubebuilder
waydroid - Waydroid uses a container-based approach to boot a full Android system on a regular GNU/Linux system like Ubuntu.