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

I find a solution in the forum
https://kubesphere.com.cn/forum/d/3384-kubespheredevopsdotnet-core
But it is too trouble to use , and waste much time to set up it .
So any plan for including it to the nodes of devops flow.

Starting point: a default, single-node microk8s installation (snap install microk8s --classic --channel=1.19) with several deployments installed through GitLab integration, including database pods with persistent volumes (storage addon).

Running microk8s disable ha-cluster deletes all deployments, all services, all pods, and all persistent volumes without any warning. Everything is gone

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

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

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

Task

Convert CI to GitHub Actions

Context

Travis is removing its free tier for OSS projects, so this should be built with GitHub Actions instead, which is not going to add additional cost.

I would expect this to be one of the easier projects to convert given that Docker isn't used in the build.

See also:

https://github.com/mvdan/github-actions-golang
https://github.com/ac

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.

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

Update Istio app to use istioctl and 1.8

Expected Behaviour

Istio 1.18 is now available and is installed via a CLI (similar to how Linkerd works)

Current Behaviour

<!

fx access HTTP endpoint of docker engine to do image build and container run, but currently fx make docker endpoint to support HTTP with "socat" with docker run https://github.com/metrue/fx/blob/master/provisioner/darwin/darwin.go#L18, it'd would be great to migrate it to Go.

NOTE: GitHub issues are reserved for bug reports only.
For anything else, please join the conversation
in Kong Nation https://discuss.konghq.com/c/kubernetes.