Description

Reverse proxies can be a useful option to separate authentication logic from application logic. SUSE and openSUSE use "loginproxies" as an authentication layer in front of several services.

Description

There are already k9s and kustomize packages that exist for openSUSE today. These could be used as the source for these binaries in our rancher projects. By using them we would benefit from CVE fixes included in our distribution of the packages not in cluded upstream. However they are not providing arm package builds which are required.

Have some knowledge on Dockers , but now taking the next step in understanding and expanding my skill set in containers and kubernetes.

Project Description

Podman is an open-source, Linux-based tool that builds Docker-compatible container images

kGraft is SUSE Labs answer to the rising need for being able to patch the running kernel without rebooting the system. I think this kind of tool is very cool, so by this hackweek chance, I want to investigate it how it works and how it was implemented. And also by this chance, I hope I can improve my ability of kernel hacking. If you are also interested in kernel live patching, please join this project together.

since i am learning golang, i will make some contributions for the upstream project we used already @suse

SUSE CaaS Platform is a Cloud-Native Computing Foundation (CNCF) certified Kubernetes distribution.

Using the camsource and vlc packages as an example. If camsource is configured to use a given dev/video[n] device with a choice of resolution in the width and height fields of a camsource conf file then if camsource is the first application to access the device captured images are as-expected. However, if an application like vlc is used for the same device (and exited) before starting camsource (e.g. to check the view from the camera before starting camsource) and if the camera supports higher resolutions than used in the camsource configuration what occurs is that camsource will not setup the camera to use the configured resolution and has a broken view of the camera output based on the vlc chosen resolution chopped to the camsource configuration. For example, with camsource configuration set to use 640x480 on a camera that supports 720x480 and vlc is used and exited before camsource is started then the captured camsource images contain two non-continuous partial image blocks with a horizontal border dividing them. I assume either vlc fails to fully reset the device configuration when exiting or camsource fails to initialize the device "from scratch" when starting. The two applications use different video device APIs but the setup and cleanup for the camera in each case is a very limited part of the application's functionality.

Project Description

I'm totally new in k8s, when I hear Rancher's product in all-hands I couldn't image what's that is. I'd like to take some time to learn some basic knowledge about k8s and Rancher's products.

The user space interface of evdev is pretty generic. All hardware abstraction is done in the kernel driver, device properties are mapped to a set of generic properties. The properties can be queried thru a generic interface only very few parameters are set from user space. In user space the evdev API is used by Xorg's evdev driver and libinput.