Summary

In v2.4.0 version, ArgoCD brought us a much waited (and awesome) feature that enables you to shell into containers.
Now developers can have access to their pods freely.

Motivation

Grant access to people dig into their pods in production environments led us to a few concerns about security and accountability.
Perhaps we need to have visibility about the commands inputed into

Which component:
code-generator v0.23.4

Describe the bug
Log reproducing the bug bumping the version to 0.23.4

F0408 17:05:35.537606   54104 main.go:58] Error: Failed executing generator: some packages had errors:
errors in package "github.com/bitnami-labs/sealed-secrets/pkg/client/informers/externalversions/sealed-secrets":
unable to format file "/home/X/go/src/github.com/bit

We are using font-awesome V4 and should migrate to font-awesome V5 which comes with its own vue.js module: https://github.com/FortAwesome/vue-fontawesome

Migration includes removing old font-awesome V4 module and changing all existing icons to new vue.js tag.

This is blocked until #114 is merged which comes with first initial integration.

Golang supports only 2 major releases: https://endoflife.date/go
Go 1.19 is expected to be out in August 2022.
We should start the upgrade process to go 1.18, before go 1.17 becomes unsupported (expected in August 2022).

Before upgrading , we need to upgrade the version of golang in the catalog repository:
example (there are other files as well): https://github.com/jenkins-x/jx3-pipeline-ca

Describe the bug

We have activated the event and post-rollout webhook and canary analysis is skipped so far. However, we never get triggered by the post-rollout webhook. With the event webhook we get this message "Promotion completed! Canary analysis was skipped for my-test-app". But no post-rollout webhook call.

To Reproduce

Our canaries YAML:

apiVersion: flagger.a

In #2649, all our dependencies except this module in the Azure related end-to-end tests were updated, as it contains a breaking change.

tfinstall has been removed and needs to be replaced with https://github.com/hashicorp/hc-install. We call it exactly one time in [azure_test.go](https://github.com/

Summary

I've tried a rollout without AnalysisTemplate and it works as expected (Linkerd + Nginx)

When I add an AnalysisTemplate it just gets stuck.

apiVersion: argoproj.io/v1alpha1
kind: AnalysisTemplate
metadata:
  name: success-rate
spec:
  args:
  - name: application-name
  metrics:
  - name: success-rate
    successCondition: result.successRate >= 0.95
    provid

Porch currently trades in packages represented in memory as tree hierarchy rooted in the topmost directory containing Kptfile:

/folder/
   Kptfile
   foo.yaml

is represented in the filesystem as

/
  Kptfile
  foo.yaml

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 ?

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

What steps did you take:

As a codebase which uses the public kapp go API, we call the public RecordedApp.UsedGVs() which in turn calls the private RecordedApp.meta() which in turn uses the k8s API to fetch the config map:

https://github.com/vmware-tanzu/carvel-kapp/blob/3486b0b61553e4cd1ebfc2fed3f95d81c1f65d10/pkg/kapp/app/recorded_app.go#L281-L287

So the code neatly checks if the

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

What would you like to be added:

This error is shown in the stage log. Need to found out and update error format for all error like this

 (%!w(*fmt.wrapError=&{failed to apply:  (signal: killed) 0xc0090b8dc0}))

Why is this needed:

When running kubectl schemahero install --yaml the Statefulset for the manager includes an "availableReplicas" field. This should not be present b/c it's not installable with it.