Summary

The Argo CD core mode should allow the user to set a permanent path to a K8s client configuration file, instead of either using ~/.kube/config per default or having to specify --kubeconfig for each command.

Motivation

Some K8s distributions by default install a Kubernetes client CLI (kubectl) which uses a custom path for its configuration. For example, K3s uses `/etc/ran

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.

Bump distroless/static to fix issues with tzdata package that are flagged by image vulnerability scanners.

I'm trying to configure Jenkins X in my company and found some broken links.

Example of links:

• "trying out a quickstart first" on https://jenkins-x.io/v3/develop/create-project/
• "charts/jenkins-x/tekton/values.yaml.gotmpl" on https://jenkins-x.io/v3/develop/apps/
• "edit any pipeline in any git repository" on https://jenkins-x.io/v3/develop/pipelines/#add-new-taskspipelines-by-hand
• "a

Describe the bug

There is a bug in podinfo chart which will not deploy service if you enabled canary, even though you enabled service via helm values.

https://github.com/fluxcd/flagger/blob/main/charts/podinfo/templates/service.yaml#L1

To Reproduce

If you set values like this, it will not deploy service.

service:
  enabled: true # service will not be deployed if ca

The documentation doesn't mention which scopes are needed for the Github PAT. Is it possible to add this information?

Summary

When using a Rollout with traffic splitting (SMI to be precise) the weight reported in the rollouts dashboard and kubectl argo rollouts get rollout <name> sometimes don't match the value in the Rollout .status.canary.weights.canary.weight or the actual TrafficSplit resource. For example, if we are at weight x and then proceed to a step setWeight: y where y would require mor

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 ?

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

Describe the problem/challenge you have
currently Deployment waiting code looks at several conditions include FailedDelete [0]. there is another condition that would be useful to look at it FailedCreate. we should add that check in there so that we can show nice informational message to the users as part of the progress log. i do not think we need to consider progress as done though, in this

Describe the bug: (a clear and concise description of what the bug is)

To Reproduce
Steps to reproduce the behavior:

1. Create a new public knative service (do not set Authenticate with Single Sign On flag)
2. Save and Deploy
3. Observe that keycloak redirect_urls has been extended by public url of that service

Expected behavior: (a clear and concise description of what you expec

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:

There is a bug while detecting the deployer in this screenshot, but the deployer name's should be limited to avoid the wide "Deployed By" column.

In the case of a long username, it can be trimmed and displayed as "foooooo...".

![Screen Shot 2022-01-13 at 14 47 02](https://use