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

If you are trying to resolve an environment-specific issue or have a one-off question about the edge case that does not require a feature then please consider asking a question in argocd slack channel.

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.

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

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

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.

You can create an ImagePolicy with a semver range, and filter by regex, but not give a replacement pattern (.spec.filter.extract field) or use an alphabetical (asc or desc) ordering.

Suggested UI:

$ ./bin/flux create image policy --help
The create image policy command generates an ImagePolicy resource.
An ImagePolicy object calculates a "latest image" given an image
repository 

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:
Bytes generated by goccy/go-yaml.File.Read() always doesn't have a newline at the end of file.

--- a/ecr-test/deployment.yaml
+++ b/ecr-test/deployment.yaml
@@ -19,6 +19,6 @@ spec:
     spec:
       containers:
       - name: nakabonne-test
-        image: account

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.).