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.

Steps to reproduce

10:27:56 in ~/Downloads/kubeseal-test
➜ kubectl create secret generic mysecret --dry-run --from-literal=foo=bar -o yaml >mysecret.yaml

10:28:13 in ~/Downloads/kubeseal-test
➜ cat mysecret.yaml                                                                             
apiVersion: v1
data:
  foo: YmFy
kind: Secret
metadata:
  creationTimestamp: null
  name: m

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

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 "edit this page" links in the right-hand sidebar go to 404 github pages.

I assume this is a hangover of the move to auto-generating these pages from the binary's help output

Steps to reproduce

1. Navigate to any page in the 'Flux CLI' section
2. Click on 'Edit this page' in the right hand side bar

For example, under 'Flux CLI' > 'Flux' 'Edi

Summary

I have the zsh completion sourced in ~/.zshrc using:

source <(kubectl-argo-rollouts completion zsh)
# or
source <(kubectl argo rollouts completion zsh)

With only this, no completion works:

• kubectl does not list argo
• kubectl-argo-rollouts does not complete
• kubectl argo rollouts does not complete

But the completion script does not enable

We are adding support custom resource ordering in kpt live with the introduction of the depends-on annotation (GoogleContainerTools/kpt#2565). The resource references includes the namespace and name of resources, which means we should make sure they are updated when using the set-namespace and ensure-name-substring functions are used. We should update the functions to

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

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

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

What would you like to be added:

https://github.com/pipe-cd/pipe/blob/2fda7c82def6c81aff29ab08d1283851f5f49f06/pkg/app/piped/cloudprovider/ecs/task.go#L45-L54

Why is this needed:

kubectl schemahero get migrations command can output a long list of migrations, with potentially repeating names.

To find the right migration with a tool like grep, we need to look at the what schema files were changed to determine what the name of the migration would be.

It would be nice to list migrations sorted by timestamps or filter by migration state (open/approved/applied)