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

Found that if all pods end up on the same node (just happened to me) nothing works well at least on our cluster due to hairpin issues. Any chance the yaml could have anti-affinity set for the pods so they don't end up on the same node by accident?

Summary

jx create addon istio doesn't work
since v 1.5 istio moved to operator so no folder install/kubernetes/helm/istio

Steps to reproduce the behavior

jx create addon istio

Output

Istio package already downloaded: /Users/msirs/.jx/cache/istio-1.6.0-osx.tar.gz
error: Could not find folder install/kubernetes/helm/istio inside istio clone at /Users/msirs/.jx/cache/istio

Hi. We have recently upgraded the sealed-secrets-controller to v0.8.1 from v0.7 and are experiencing that all sealed secrets are getting unsealed frequently without any modifications to the sealed secret entity.

Is this an expected behavior?

Worth noting is that we are runnnig in a

We'd like to make sure flagger is there if there's some contention. Also please add this to the loadtester chart

Implement a gPRC version of the API (on a different port) for podinfo and generate the client in podcli.

Reliability monitoring - e2e testing of GitHub workflow

Context

Since moving the Communtity Cluster from GKE to DigitalOcean the reliability has dropped dramatically due to issues with the Cilium networking driver 1.4.0. A separate action will be required for this, but in the meantime it highlights a lack of e2e monito

General remarks
There appears to be no way of adding labels or annotations to the Secret object created by KamusSecret

Is your feature request related to a problem? Please describe.
My Secret objects sometimes need annotations and/or labels - for example when using Helm version of Jenkins for Gitops, the Jenkins secret needs labels and annotations:
labels:
"jenkins.io/credenti

Can you add autocomplete to a command in bash? Pressing the tab key displays subcommands

Expected behavior

When running the terraform step, all plan contents should be visible or there should be a scroll bar.

Actual behavior

A scrollbar never appears, and content clips off the bottom of the screen. If the page zoom is changed, content reflows and a scroll bar appears.

Information

• Ship version: 0.43.1
• Command line run: ship init ./ship.yaml
• Chrome v

At present when we are for example checking the rollout status of multiple installed components, it will stop and only return the first error if some component's rollout failed.

To provide a user with a better overview of what happened, we should complete the bulk run before bailing so that we can return a full overview of what did and did not succeed.

For bonus points: we would like to mini

valuesFromFile:
  chartFileRef:
    myScript: path/to/file.js
  externalSourceRef:
    defaultScript: https://raw.githubusercontent.com/cdenneen/example/master/script.js

result in equivalent of:

helm install --set-file key=path/to/file.js

myScript: |
  const { events, Job } = require("brigadier")
  function run(e, project) {
    console.log("this i

Long tags with all digits seem to be changed to scientific notation at some point.

As a: developer

I want: the dashboard to display ring names I've configured in bedrock.yaml

So that: I can see the right ring name for services in the dashboard

Describe the solution you'd like:
Following the work on microsoft/bedrock#1313, any branch can be associated with any ring name. Currently, the introspection script assumes that the branc

As discussed in slack.

In comparison to skaffold (another deployment tool), kapp only reports if the condition was met or not. I'd like to see more information about the stabilization process e.g:

Waiting for deployments to stabilize...
 - production:deployment/demo: creating container service
    - production:pod/demo-5cf5f768d4-x9xfr: creating container service
 - production:deploy

If there are pending migrations for the database, setting the immediateDeploy flag to try should approve all pending migrations