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:
None. This is a GH actions pipelines improvement.

Describe the bug
GitHub Actions are part of our Build and Release pipelines, and we must ensure that we use up to date versions of the Actions and that we always use Actions from verified sources (Actions provided by GitHub or from verified provider of the GH actions Marketplace).

To Reproduce
N/A

**Expected

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 a mount 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:

export KAPP_E2E_NAMESPACE=test-ns
./hack/test-e2e.sh

What happened:
A few tests failed because they have hardcoded namespace kapp-test and hence require using a ns with the same name for running the e2e tests.

What did you expect:
Tests should have ran successfully.

Anything else you would like to add:
If we currently use

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:

Why is this needed: