Local PV (device) provisioner leaves a stale BDC in the following case:

• On PVC request, creates a BDC
• If the system doesn't have a matching BD, then PVC request keeps retrying, and so does the NDM operator that keeps retrying
• Now if the user deletes the PVC, then Local PV (device) provisioner doesn't get the trigger to process delete, as there was no PVC.

This causes the stale BDC

On contexts with many APIs and APIs calling other APIs in chains, having too many spans in the zipkin/jaeger dashboards may lead to a too complex usage of such dashboards and of not necessary big data volumes.

For Tyk's admin team, the steps representing the time spent in each Tyk middleware are much valuable.

But the upstream APIs teams just want to know the global time spent in Tyk interna

What's it about?
Upgrade Ingress API to networking.k8s.io/v1.

What's the reason why we need it?
Ingress is the core component that is used by the KubeSphere Routes feature. KubeSphere is still using the old api "extensions/v1beta1" both Frontend and Backend. However "extensions/v1beta1" Ingress is deprecated in v1.14+, unavailable in v1.22+. So we need to upgrade it to the latest v

I checked inspect.sh -- suggest_fixes
I think the addition of this boundary case will be helpful to the beginner of K8s

ref to #2364

Add a test sending (e.g. config map) patches through the same API using:

• JSON patch
• Strategic merge patch

make sure the API client is able to set the content type properly according to the request body, and the patches are applied successfully.

ref: https://github.com/ku

centos 8.2 已经发布了，想了解下对 centos 8.x 的支持计划大概是怎样的，谢谢。

This feature enables the ipsec backend for Flannel in the k3sup install command

Expected Behaviour

An additional flag to k3sup install should enable ipsec for Flannel as

Hi,

It seems like naming a remote is subject to certain limitations as groupadd is executed (potentially 32chars?).

Example

apiVersion: gitkube.sh/v1alpha1
kind: Remote
metadata:
  name: app-remote
  namespace: my-really-really-really-long-ns

k logs po/gitkub

Use case

Polyaxon tracking can be used to automatically log all information generated by Ludwig.

We should probably think about adding support for Polyaxon's tracking module in Ludwig contrib.

Location

• Browser
• CLI
• API
• Documentation

Motivation

Connecting to AWS RDS is complicated without a step-by-step guide unique to Porter.

Requirements

• Document how to set up the RDS instance if it doesn't exist.
• Document how to connect to the RDS instance from the same VPC.
• Document how to configure VPC peering if an RDS instance already exist

Hi,
This is a useful tool for any DevOps/SRE teams managing K8S clusters and apps.
One question though, will this be able to detect changes to Secrets stored in an external store like the GoDday one or the HashiCorp Vault.
thanks,
KK

Expected Behaviour

When using K8s 1.22 and newer, use the new namespace for ingress, for older use the deprecated API (apiVersion: extensions/v1beta1)

Several apps gener

The ingress template https://github.com/openfaas/faas-netes/blob/master/chart/openfaas/templates/ingress.yaml uses
deprecated extensions/v1beta1 version. Due to the https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/, the API version should be migrated to networking.k8s.io/v1beta1