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
Related kubernetes/minikube#14257
This isn't currently supported, the flag was put in for future proofing to make it easier if we do implement it.
If the user tries to use the flag we should output a message to the user saying the flag is not yet supported and the flag value should be ignored.
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
To configure the API key for a private instance of Stackoverflow requires an API passed in the request parameters. It should be passed to StackOverflow unencoded.
The implementation of qs.stringify have encoding set to true by default. Which changes special characters present in the API.
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
What happened/what you expected to happen?
The message that is output by the hook named on-fail should have the `{{ work
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
refer:
I think we could remove it directly and safely.
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
this command should be something like :
vela env set vela-system --label trivy-scan=true
Then we can tell users that this is a environment for development which can scan vulnerabilities.
Under the hood, we are labeling the k8s namespace.
Originally posted by @wonderflow in kubevela/catalog#380 (comment)
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