What happened:
This [PR](kubernetes/kubernetes@30b0f8b

@cakrit I just got the following response:

Thanks for getting in touch about this. Unfortunately, I'm afraid that the issue is due to the fact that app incoming webhooks cannot be overridden to send to specific channels.

For this use case where you need to be able to send messages to different channels, it would be better not to use an app incoming webhook because those are restricted

There is a document describing how to migrate an existing etcd cluster from HTTP communication to encrypted HTTPS.
The document uses v2-based CLI, some of those commands have different args or output format in their v3 equivalent, and some of them (like etcdctl cluster-health) doesn't seem to exist in v3. The documen

Do you want to request a feature or report a bug?

Bug

Did you try using a 1.7.x configuration for the version 2.0?

• Yes
• No

What did you do?

As mentioned in #5604, there is a missleading error message. We should fix that.

What did you expect to see?

Not a missleading error message

What did you see instead?

Midlleware ERROR: TLS Certifi

(This is used to request new product features, please visit https://discuss.istio.io for questions on using Istio)

Describe the feature request
Intermediate CAs must be manually generated. The manual process is not easy requiring many manual error-prone steps. It took me about 2 hours to get through the instructions the first time and the results were not correct. I had it down to abo

We have a python script that checks if there is license boilerplate in every file in the repo.
that was initially copied from kuberntes project.

https://github.com/kubernetes/minikube/blob/master/hack/boilerplate/boilerplate.py

we need to get rid of it, because it would be nicer to have everything in go.
also reduce the dependency installation during each build / PR. currently we have to

Move all Dockerfile samples to non-root user

Expected Behaviour

As an OpenFaaS end-user, I want to run all samples on my OpenFaaS cluster, even with the new non-root feature enabled.

Current Behaviour

Overview of the feature request

We should add the spring no-http plugin to make sure we (and our users) do not use http repositories by accident in maven or gradle builds. If it works well we can extend the use to e.g. production code.

I will take care of it. It worked pretty well for gradle but there were some problems with the maven checkstyle integration.

**Motivation f

in conversation with Matt (Farina) 😄 looks like the helm build is failing when coveralls is down or respond http 500

The proposed idea is not to fail the build when this is down, just bypass the upload results.

I will open a PR to propose the change and we can discuss the approach

/cc @mattfarina

Rancher server version - v2.2.4

Document the changes done relating to changing file path related fields to content based fields in node template drivers.

We need to ensure that our documentation clearly states any/all pre-requisites for a node (VM).

For example:

• Hostnames cannot be duplicated, some providers (e.g. Linode) may create machines with just "localhost" as the hostname. If this is the case you must pass the --node-name or $K3S_NODE_NAME env var with the curl script and specify a unique node name.
• Just like with k8s (https://k

This issue is to support the following netdevice ioctls.
SIOCGIFMAP
SIOCGIFTXQLEN
SIOCGIFDSTADDR
SIOCGIFBRDADDR

Issue Description

Type: bug report or feature request

Describe what happened (

Feature Description

If I accidentally speak HTTP to the vtgate server's MySQL port, I will receive an error as follows:

E0913 16:24:17.447452   14972 server.go:299] Cannot read client handshake response from client 5 (127.0.0.1:39986): Code: INTERNAL
invalid sequence, expected 1 got 32

Note that this is an error, not a warning/info.

Use Case(s)

Some naive

Current output:

Checking cache...
 - gcr.io/priya-wadhwa/redis: Found. Pushing
The push refers to repository [gcr.io/priya-wadhwa/redis]

Expected Output;

Checking cache...
 - gcr.io/priya-wadhwa/redis: Found Locally. Pushing
The push refers to repository [gcr.io/priya-wadhwa/redis]

or, if exists remotely,

Checking cache...
 - gcr.io/priya-wadhwa/redis: Fou

Currently we didn't port all test cases from v1alpha1 to v1beta1. Part of the reasons is because we haven't implement functions that v1alpha1 has:

• SyncCache
• [GetSecret](https://github.com/kubeflow/kubeflow/blob/2f15d8dbe85f0081652c1e5

From #2046.

Auth has the most friction, and it will help a lot to report if Jib picked up some credentials and where if so. It will help cases like #2050 too.

FEATURE REQUEST:
Hi,

I see that there is nothing in the kargo repo related to docker login stuff and more precisely nothing about the ability to make kubernetes pull images from private registries such as ECR.

I have a solution for this that currently works for ECR and CoreOS and that could be extended to different registries solutions (azure one, custom private registry on premi

The output of `oc new-build

Description

Add Azure notebook to our SETUP doc.
I tested google colab and Azure notebook to run reco-repo without requiring creating any DSVM or compute by myself, and it works really well with simple tweaks to the notebooks (e.g. for some libs, should install manually).

I think it would be good to add at least Azure notebook to our SETUP doc, where users can easily test out our repo w/o

Is this a bug report or feature request?

• Feature Request

**What s

Current README instructs to remove the liveness/readiness probes from deployments, if the user has installed Istio with STRICT mTLS.

OSS Istio 1.1 now supports probes in mTLS, so we may want to:

1. test that this is the case
2. modi

HELP nginx_ingress_controller_bytes_sent The the number of bytes sent to a client
TYPE nginx_ingress_controller_bytes_sent histogram

Labels:

• controller_class
• controller_namespace
• controller_pod
• host
• ingress
• method
• namespace
• path
• service
• status

HELP nginx_ingress_controller_config_hash Running configuration hash actually running
TYPE ngi

This issue captures the slack conversations w.r.t inability of NDM to discover certain disks.

❓ Hello all,
I continue my journey to understand openebs storage.
Reading the documentation regarding the cStor I added 8 * 32G disks to each nodes in my cluster. Actually there's 3 nodes in my cluster so I assume that I will seen 8 * 3 = 24 blockdevices in my clusters. But there's only 8: