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

Checklist:

• I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
• I've included steps to reproduce the bug.
• I've pasted the output of argocd version.

Describe the bug

With 1.8.4, we have disabled the output of installation specific version information to unauthenticated consumers of the version endpoint. However, this looks funny when using `

Summary

When creating docker images for Java applications in the current setup in Jenkins-X the application and all dependencies are all placed in one jar file, meaning it will be in one layer in the docker image.

This means that when new versions of the application are created the unchanged dependencies can't be reused.

It would be a great enhancement if the application code where p

Problem

Installation is not straightforward enough for some users.

Suggestion

Use goreleaser (with a homebrew option for mac users, etc). The resulting installation section of your readme could then look something like [this](https://github.com/scottrigby/example-dep-no-vendor/#example-installati

In lieu of #283, implement Stackdriver Canary Analysis for use in GKE.

Would it be possible to add service.annotations to the chart? That would enable things like setting up CloudCDN in GKE and test it with Podman before going to production.

Hi guys,

it seems the documentation on sealed secrets is missing a simple flag:

The docs state Sealed Secret Doc:

kubeseal --format=yaml --cert=pub-sealed-secrets.pem \
< basic-auth.yaml > basic-auth-sealed.yaml

I believe the --controller-namespace argument is required (mentioned in bitnami docs & decryption did not work

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

Authentication via Azure/aad-pod-identity for keyvault access could be a good feature to avoid use of clientId/ clientSecret in chart values. Don't you think ?

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

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

What would you like to be added:

Change color of loading indicator

Why is this needed:

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

Currently releases are done by manually running goreleaser and docker build + docker push, the process is documented here.

The purpose of this issue is to request CI functionality be added to automate releases and also test the integrity and basic functionality of release artifacts (binaries, container images, e.t.c.).