Hi,
first thanks for this awesome software. But I have some trouble and I don't know how to proceed. First I try to find out what else I could provide for this report to be a good bug report.
First, I use the latest version (v1.14.0) from openSUSE build Service. I know, I should compile it by my self to avoid any other causes for this behavior. But for now I still use this package from there
As suggested by @afbjorklund kubernetes/minikube#14410 (comment)
We only check for docker, not dockerd & cri-dockerd, this will let the user know earlier on that they don't have all the requirements to run the docker container runtime.
Output of helm version:
version.BuildInfo{Version:"v3.8.1", GitCommit:"5cb9af4b1b271d11d7a97a71df3ac337dd94ad37", GitTreeState:"clean", GoVersion:"go1.17.8"}
If HELM_DATA_HOME contains spaces, like `/Users/My Name/Library/hel
The SwaggerUI component should display the description text of the different endpoints with an easy-to-read text color.
When the description contains and HTML element the text has the default col
Actual the windows executables (jaeger-agent.exe, jaeger-collector.exe, ...) don't have a version set. It is hard to identify the current used version and check if the actual used version is outdated.
Our parser outputs all aggregations functions using the general sqlparser.FuncExpr. This is a little clunky and requires us to do additional checks before we are sure that the aggregation we have is valid and what it is aggregating.
I suggest we instead introduce one struct type per aggregation, and have them all implement some interface. This would help clean up the code.
Example:
1. Describe IN DETAIL the feature/behavior/change you would like to see.
Implement WarmPool.RenderTerraform()
2. Feel free to provide a design supporting your feature request.
/kind feature
/area terraform
/lifecycle frozen
PodPriority should be deprecated from workflow spec since Kubernetes uses PodPriorityClass to indicate the importance and priority of a pod relative to others.
https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/
On https://thanos.io/tip/thanos/changelog.md/ -> Table of Contents
This link v0.25.2 - 2022.03.24 should actually go towards https://thanos.io/tip/thanos/changelog.md/#v0252httpsgithubcomthanos-iothanostreerelease-025---20220324
Perhaps this page / table of contents could be easier/nicer as well - For example that the table of contents
Add a network option in creating workload
like rancher‘s Networking tab
** During workload creation, user can customize own hosts and DNS search doma
Via a Slack conversation with @chrisohaver.
What you would like to be added: A warning about potentially malformed domains in Corefiles: e.g., k8s.foo.bar.com::53 (with two colons).
Why this is needed: CoreDNS will parse the domain as
Description
Reference
What would you like to be added/modified:
when we run keadm beta join command to start an edge node, we run systemd related commands in our source codes to start edgeocre systemd service, such as
https://github.com/kubeedge/kubeedge/blob/bef4c51ee551d315e3eb5e75db4878dd023b867f/keadm/cmd/keadm/app/cmd/edge/joinb
NetworkChaos works with device: eth0, not work with device: eth0@if12
I am not sure if it would be a bug or an enhancement.
We could add a validation webhook, or trim the things after @.
What version of Kubernetes are you using?
N/A
What version of Chaos Mesh are you using?
Spent the morning debugging what I thought was a goroutine leak, but turned out to be just a huge number of goroutines being created in a short period of time. However, it seems a lot of the unit tests do leak goroutines. Most of these might just be issues with tests not cleaning up properly, but it makes testing/debugging real leaks quite difficult. Or in my case, the leaks were a red herring - t
Describe the bug
certain pods are missing "standard" labels which are useful for certain scenarios:
app.kubernetes.io/name
app.kubernetes.io/instance
To Reproduce
Steps to reproduce the behaviour:
default labels are missing on:
all csi-.* pods
engine-image
instance-manager
longhorn-csi-plugin
Expected behavior
app.kubernetes.io
Is your feature request related to a problem? Please describe.
When I want to delete more than one apps, I have to do it one by one.
vela delete composed-app -y
vela delete frp-proxy -y
vela delete vela-app-with-sidecar -y
vela delete ecs-demo -y
It's annoying when I have many apps.
Describe the solution you'd like
I hope we can delete them together at once:
`
Add a description, image, and links to the cncf topic page so that developers can more easily learn about it.
To associate your repository with the cncf topic, visit your repo's landing page and select "manage topics."
Presumably this would occur when changing the default from one class to another. E.g.
At the case in point, when there are 2 defaults, we currently do not assign default values to new PVCs.
We should change this semantic - while there a