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

At this point this is just by looking at the code and not validated by me. (although reported by a user)
Current main -- https://github.com/tektoncd/pipeline/blob/e2f528b0b247efb3b52b10800aad4ffd9046a266/pkg/pod/entrypoint_lookup_impl.go#L64

We're creating the k8schain with the service account, but also should add in the image pull secrets referenced in the pod template.

Description

We're running usability tests and would love for you to record walking through our tutorials. The idea for this ticket is that you do a screen capture walking through one of more of the following examples:

• Hello World! (15 minutes)
• [Iris Dataset](https://kedro.readthedocs.io/en/stable/02_get_started

Describe the bug
data docs columns shrink to 1 character width with long query

To Reproduce
Steps to reproduce the behavior:

1. make a batch from a long query string
2. run validation
3. render result to data docs
4. See screenshot
   <img width="1525" alt="Data_documentation_compiled_by_Great_Expectations" src="https://user-images.githubusercontent.com/928247/103230647-30eca500-4

Tell us about the new connector you’d like to have

• Which source and which destination?
  Source: mambu (https://api.mambu.com/)
  Destination: S3, RDS, Redshift
• Do you need a specific version of the underlying data source e.g: you specifically need support for an older version of the API or DB?
  Want to support for since 1.0.

Describe the context around this new connector

• Why do yo

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.

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

What steps did you take

• Click on a task on the KFP run page.
• On the Input/Output tab, click the minio:// link for main-logs to view raw logs.

What happened:

The logs file is served from the minio Express webserver without any character encoding header. This causes any non-ascii UTF-8 characters to be rendered as garbled text.

What did you expect to happen:

I think

We distinguish different types of terminals by judging process.stdout. On the default terminal, we use console to output logs, while on the TTY terminal, we use the ora. We have added a time prefix to Ttylogger, but this feature has not been implemented on the DefaultLogger.
Here is the DefaultLogger:
https://github.com/alibaba/pipcook/blob/main/packages/cli/src/utils/index.ts#L212

While testing another PR, I found that mu pipeline logs command displays information from the pipelines, but also shows this error:

$ mu pipeline logs
[... normal, expected output ...]
func1 ▶ ERROR  ResourceNotFoundException: The specified log group does not exist.
	status code: 400, request id: f7260741-7f69-4772-b4cc-7c6a9c22d264

This error does not occur with the `-f