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

Is your feature request related to a problem? Please describe.
As a user I often update apps by simply changing their image tag... edit the yaml is a tedious task.

Describe the solution you'd like
I would love to see a quick set im

Description

After removing a pvc I can still find a directory shared-pvc-69adec76-665e-46bc-b957-2b2f58338429-target in /var/openebs. Shouldn't this stuff be cleaned up automagically? Storage class:

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  annotations:
    cas.openebs.io/config: |
      - name: StoragePoolClaim
        value: "cstor-disk-pool1"
      - name: Re

I recently installed the microk8s snap on a vanilla LXD container. At the time I hadn't come across https://microk8s.io/docs/lxd and it took a little while before I noticed that some components hadn't started up properly and I found my way to that doc.

Having found the documentation, it's excellent, thank you - following the instructions there left me with a very happy microk8s instance. From a

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）

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.

I reinstalled a k3s cluster built with --no-extras and added `--k3s-extra-args="--flannel-backend=host-gw". The cluster failed to start.

I logged in and saw that the output of ps showed the following:

14760 ?        Ssl    0:40 /usr/local/bin/k3s server --cluster-init --tls-san 10.68.0.63 --flannel-backend=host-gw--n

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.

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.