Move all Dockerfile samples to non-root user

Expected Behaviour

As an OpenFaaS end-user, I want to run all samples on my OpenFaaS cluster, even with the new non-root feature enabled.

Current Behaviour

Description

Adding Indonesian translation of Readme.md and contributing.md

Con

Feature Description

Kubersphere integrate the velero based on the k8s CRD extensions

How does it work
It's like monitoring component

Installing microk8s with sudo snap install microk8s --classic appears to go fine, but microk8s status always reports as microk8s not running. microk8s kubectl get all --all-namespaces shows everything as not ready and pending.

Ubuntu 20.04.1 Desktop, network-interfaces are ens33, lo, virbr0 and virbr0-nic, so nothing particularly exciting there. The flannel - interface you'd get with an e

Hi,

It seems like naming a remote is subject to certain limitations as groupadd is executed (potentially 32chars?).

Example

apiVersion: gitkube.sh/v1alpha1
kind: Remote
metadata:
  name: app-remote
  namespace: my-really-really-really-long-ns

k logs po/gitkub

Add a test sending (e.g. config map) patches through the same API using:

• JSON patch
• Strategic merge patch

make sure the API client is able to set the content type properly according to the request body, and the patches are applied successfully.

ref: https://github.com/ku

目前备份存储只支持oss,s3,azure三种云端存储方案，希望增加本地存储方案（Ceph,nfs,nas）

Task

Convert CI to GitHub Actions

Context

Travis is removing its free tier for OSS projects, so this should be built with GitHub Actions instead, which is not going to add additional cost.

I would expect this to be one of the easier projects to convert given that Docker isn't used in the build.

See also:

https://github.com/mvdan/github-actions-golang
https://github.com/ac

Use case

Polyaxon tracking can be used to automatically log all information generated by Ludwig.

We should probably think about adding support for Polyaxon's tracking module in Ludwig contrib.

It would be nice to include k8s liveness and readiness probes support.

fx access HTTP endpoint of docker engine to do image build and container run, but currently fx make docker endpoint to support HTTP with "socat" with docker run https://github.com/metrue/fx/blob/master/provisioner/darwin/darwin.go#L18, it'd would be great to migrate it to Go.

The buildkit (client) and buildkitd (builder daemon) can both be used with faasd or k3s hosts for building images without installing Docker onto the machine.

There is a tar that can be downloaded like we do with inletsctl, however, we need to make sure we extract both binaries. I'm fairly sure that this will "just work"

See more:

https://github.com/moby/buildkit/releases

NOTE: GitHub issues are reserved for bug reports only.
For anything else, please join the conversation
in Kong Nation https://discuss.konghq.com/c/kubernetes.

Summary

As specified here, images on bintray should follow have an architecture appended to them:
https://github.com/Kong/kong/blob/master/CHANGELOG.md

Currently only amd64 is available.

Kong proxy does but the

Cloudprober supports building additional metrics (other than the default ones) from external probe output. We could possible do the same for HTTP probe.