gitops

The current fav icon makes me think the app has been faved, when it has not. The fav icon should be an outlined star, not a filled star.

Not fav:

<img width="138" alt="image" src="https://user-images.githubusercontent.com/1142830/162030909-b256be55-d242

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.

Not sure what the error is, but lint passes in the CI and locally even if exported structs dont have comments.
Most probably, it's an issue with the golangci yaml config we use.

Also we use revive instead of golint (which is deprecated), may be some setting in revive needs to be enabled?

If we check the goreport card, we can see the issues: https://goreportcard.com/report/github.com/jenkins

Describe the bug

The documentation and some tests uses gw.ns(.svc.cluster.local) for gateways.

I think this is the correct format for istio gateways: <gateway namespace>/<gateway name>

Like here:

https://github.com/fluxcd/flagger/blob/273b05fb24d467c10939389218e6a8ec26d4c70e/test/istio/test-delegation.sh#L41

re. https://istio.io/latest/docs/reference/config/networking/virtua

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/

Similar to deployment, Rollout should throw error and shouldn't create the object if the selector is not specified.

Current behavior:
Rollout object gets created with Error status

Expected behavior:
Rollout object shouldn't be allowed to create and throw a validation error

Following file doesn't have selector defined

apiVersion: argoproj.io/v1alpha1
kind: Rollout
metadata:
  n

We have a small number of e2e tests for kpt live (outside of the bash-based approach). They currently run in serial and requires that a new cluster is created for several of the tests. This causes them to be very slow.

We should improve this by:

• Reduce the number of times we need to create a new kind cluster, as this takes ~1 minute. Tests should clean up after themselves and we can handle

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 ?

Is your feature request related to a problem? Please describe. A clear and concise description of what the problem

The kiali-operator may require higher memory limits for clusters with bigger amount of nodes. Thus resource limits shall be configurable via values.

Describe the solution you'd like A clear and concise description of what you want to happen.
Enrich schema for Kiali-operator

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

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

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.

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: